| Table of Contents | Pages |
|---|---|
|
Purpose
The Delivery module is the repository of created reports in MetaField. It stores both MetaField-generated reports and other project-related reports that are optionally uploaded into Delivery. There are a variety of actions that can be performed on reports in the Delivery module.
| Info |
|---|
It is important to understand that the Delivery module stores reports that have been generated in other areas of MetaField or in non-MetaField applications. They are static (point-in-time) reports. Changing the underlying DATA on a test or sample will not impact reports in Delivery at all. A new report will need to be created from the source module / application and finalized or uploaded into the Delivery module. |
Create a Consolidated Report
See Delivery - Consolidated Reports
Upload a Report
Publish a Report
AgilePort subscribers can publish reports from delivery to your AgilePort site. Simply select the report(s) you want to publish and click the Publish button. Your reports will be published to the appropriate project folder / sub folders on your AgilePort site.
Emailing Reports
If you have the appropriate permissions you will see an Emailbutton in delivery. When you choose to send a report via email, the system will send an email message that contains Depending on how your instance of MetaField is configured, you will be able to send emails that contain links to each of the selected reports along with who the reports were sent toor emails that contain report PDF attachments. In either case, the system will track when and to whom the report was sent. In the case of report links, you will also be able to track if your report recipient opened the link to view your report.
An example email message with an email link:
| Info | ||
|---|---|---|
| ||
Before each report the Report Name, Report Description (if set to display in Administration and unique system Report Number will display. |
To send reports via email follow these steps:
Preparing & Sending the Email
| Step | Description | Example | |||||
|---|---|---|---|---|---|---|---|
| 1 | Select the reports you want to email and choose the Emailbutton
|  | |||||
| 2 | A popup will appear. It will be prepopulated as coming from you. If you want to copy yourself on the email message, select the Send Email to Me flag. If your Admin user has defined default text, this will be entered in the Message field for you. You can modify the message as necessary.
| 
| |||||
| 3 | Add additional recipients by selecting the Add Recipient button. When you are adding a receipt you can choose which reports out of the ones selected should be sent to the individual. If you have a defined email distribution list in Project specifications your recipients will be populated for you. |  | |||||
| 4 | When you are done performing any modifications necessary on the popup, select Send to send the reports via email. All reports sent will automatically be marked as delivered. |
Viewing Past Email Recipients and Accessed Report Links
When a report is sent via email from deliveryMetaField, the system tracks the email recipients and . If your site is configured to distribute report links, you also can view when the report link sent to them was first accessed. The system also tracks reports that were sent form the field.
To view this information To view the log of email transactions for each report, select the envelop icon from the main reports grid.
| Info | ||
|---|---|---|
| ||
| If the report link is still valid, you will see a link to the report. When the report link is no longer valid, you will see Expired in the grid. |
Expired Report Links
Emails sent through delivery will contain links to reports that are valid for 14 days. This is by design and for security reasons. After this period, the link will expire and the report will no longer be valid. be accessible to the email recipient. For more a more permanent archive of reports, AgilePort should be utilized.
| Info | ||
|---|---|---|
| ||
When a user tried to access an expired report link hey will receive this notices:
|
Download A Report
Reports can be downloaded individually or in batch. Click the disk icon in the report record to download a copy of an individual report PDF file. Click the Batch Download button to download multiple reports at the same time, which will place them all in a single .zip file that will be downloaded.
Batch Print Reports
Reports can be printed in batch. Simply select the reports you want to print and click the Batch Print button. A consolidated PDF will be created with all of your underlying reports that can be sent to your printer.
Edit Report Metadata
When reports are created, users can supply an optional Description and Label. These values can be updated in Delivery by using the Edit Description and Edit Report Label buttons.
| Info | ||
|---|---|---|
| ||
|
Mark Reports As Delivered
Reports that have been delivered to your customers should be marked as Delivered in the Delivery module. Simply select the reports that have been delivered and click the Deliver button.
| Info | ||
|---|---|---|
| ||
If you choose to publish a report to AgilePort or send a report via email from Delivery, your report will automatically be marked as Delivered. |
Mark Reports As Revised
In addition to the statuses in the Delivery Status column, there is also the option to flag a report as a Revision. To indicate a report is a revision, select the checkbox in the R column next to the corresponding report.
Delivery Status Assignment
The following table outlines how various Delivery statuses are automatically assigned.
...
Deliver
...
Publish
(AgilePort Users Only)
...
Sign
(AgileStamp Users Only)
...
Delivered (unsigned)
...
Delivered
| Info |
|---|
When Sign is selected for an unsigned Delivered report, the original unsigned report will remain and a signature will be applied to a copy of the report. Both reports remain in Delivered status. |
| Tip |
|---|
Both signed and unsigned reports can have a status of Delivered. You can tell if a Delivered report has been signed by viewing the Signed By column.
|
Sign a Report
If Digital Signature is available to you (AgileStamp subscribers), you’ll see a Sign button.
| Step | Description |
|---|---|
| 1 |
|
| 2 |
|
| 3 |
|
| Info |
|---|
|
What Reports Can Be Signed in Delivery
Report Delivery Status | Previously Digitally Signed | Delivered | Can Sign? | Signing Process Notes |
|---|---|---|---|---|
| Complete | No | No | Yes | Report can be signed for the first time since it has not been signed. |
| Final | Yes | No | No | Signing is not allowed since re-signing a report in Delivery is not allowed. |
| Delivered | Yes | Yes | No | Signing is not allowed since re-signing a report in Delivery is not allowed. |
| Delivered | No | Yes | Yes | User will be asked if they want to copy the delivered report to sign a new copy. If they select "Yes" then the unsigned & delivered report will be copied and the new copy of the report will be signed. The user can't directly sign the delivered report that was not originally signed. |
For all scenarios above where the report can be signed, signing is only allowed if the Signature Type defined in the Administration module does NOT equal "None."
Deleting a Report from Delivery
To delete a report in Delivery, simply click the X on the far right side of the reports grid.
...
"Failed to Send Reports to" Popup
If a "failed to send reports to:" message is encountered after hitting send it is likely due to one of two reasons. For any other reason, please reach out to the MetaField support team.
- The recipient email address is not valid. Please ensure the recipient address is correct and valid.
- The email being send contains an attachment that exceeds the email attachment size limit for the recipient. This could occur with a large consolidated report (25Mb+) compromised of multiple reports with images. AgilePort could be used as a delivery method to circumvent this.