FS 343616 POD DMS Export Images
Marshalls Stone
POD DMS Export Images
CALIDUS ePOD
16th August 2017 - 1.0
Reference: FS 343616 SCR-ADD-1
Contents
Functional Overview
Client Requirement
Additional request from customer: Following a meeting with Credit Services they would ideally like images associated with a POD being uploaded in to OnBase as well as the POD report itself, but ideally in a separate file such that they can choose whether to send them with the POD or not to any customer that is querying an invoice.
Solution Overview
The POD/POC report mechanism will be modified so that the images file can be exported in a separate file.
Additionally, this will also be modified so that the addition of images when exporting to a Document Management System can be configured at a system level, allowing OBSL to configure the system so that multiple files can be exported to the DMS:
- The POD file itself
- Any attached images
The customer can then choose to send the images to the customer through OnBase if they desire.
The files are expected to be named in the following patterns:
- The POD file - POD_(EPL_JOB_CODE).pdf
- The Images file - POD_(EPL_JOB_CODE)_Images.pdf
In these file names, EPL_JOB_CODE is replaced with the value from the job. This is expected to be populated from the data in the interface as the Sales Order.
It is expected that the files created will be transferred either by direct file copying into a folder or transferred via FTP to an account and folder set up by the customer. In the case where the files are simply copied, an FTP server may be set up on the instance of CALIDUS ePOD for the customer, so that the files may be retrieved automatically by an external system or manually.
Scope
Changes will be made to latest version (v4.X) of CALIDUS ePOD only.
Note: If the report format does not allow images to be specified, this section of the report will never be populated.
Note: If the report format allows images to be generated, a separate image PDF will always be generated for the report when exported through the POD interface to the DMS, if the export is configured for this. In the case where there are no photos present on the job, the file will only contain the header section.
Note: Emailing the report from the Admin Report or automatic emailing of the report to a customer not be affected by this change - these processes will obey the settings against the report itself as to whether the images will be included in the PDF file. This new setting against the report will affect exporting through the POD interface only.
Set-up
Pre-requisites
Menu Structure
Data
The existing Marshalls configurable reports will have the parameters modified so that the images will be split:
- Marshalls Premier Mortars
- Marshalls Landscape
An Export configuration will be generated for the export of the POD reports to the DMS:
Example format of POD message.
| Field | Value |
|---|---|
| EPL_XF_TYPE | FILE (Types of FILE, FTP and EMAIL are supported.) |
| EPL_XF_DESTINATION | Destination Folder for example: C:\OUTBOUND\POD\ |
| EPL_XF_ID | POD |
| EPL_WEB_USER | User for filesystem or FTP , if required. |
| EPL_WEB_PASSWORD | Password for filesystem or FTP, if required. |
| EPL_XF_DIRECTION | O |
| EPL_EXPORT_JOB_TYPES | D|S |
| EPL_EXPORT_FORMAT | PDF (formats of HTML, Image, PDF) |
| EPL_IMAGE_TYPE | |
| EPL_TIFF_COMPRESSION | |
| EPL_FILENAME | Filename with insertions, expected to be "POD_(EPL_JOB_CODE)" |
Export Configuration
Each site will be configured with this Export Configuration.
Site Maintenance
Functional Description
Note: The nature of this change is very technical, in that it deals with back-end processing of exports and generic production of reports. As such, it is not expected that this can be explicitly reviewed and accepted. However, the overall result of this change is as described in the Solution Overview above.
Configurable POD/POC Report
The parameter EPOD_CONFIG_REPORT.ECR_EMAIL_IMAGES_IND will change from values 0 (disabled) and 1 (enabled) to the following values:
- 0 - not created
- 1 - Created - same file
- 2 - created - split file in export
The POD section of the report will be changed to be surrounded in comments as follows:
<!-- POD START --> <!-- POD END -->
This will be achieved method PopulateReport, when the divContent.innerHtml is populated.
The Image section of the report will be changed to be surrounded in comments as follows:
<!-- IMAGES START --> <!-- IMAGES END -->
This will be achieved in method generateImageData.
AutoExport
EPOD_SYS_EXPORT.ExportPOD will be changed to the call to EPOD_SYS_EMAIL.GetReportHTML, to add a parameter by reference for the configurable report format (EPOD_CONFIG_REPORT).
EPOD_SYS_EMAIL.GetReportHTML will be changed to get the configurable report format (if this is a configurable report) and set to this parameter. A new EPOD_CONFIG_REPORT DAL object will be created, passing in the configurable report ID from the Job Group, if this is a configurable report, for POD and POC types - service reports are not affected at this time. The parameter will be set to this object created, or null.
EPOD_SYS_EMAIL.GeneratePDFFromHTML will be changed to receive a new parameter (p_strOrient) indicating (P)ortrait or (L)andscape. If present, add following to the call to WkHTMLtoPDF:
(p_strOrient == PDFDocument.Orientation.Portrait ? "portrait" : "landscape") + " "
The same change above will be added to EPOD_SYS_EMAIL.GenerateImageFromHTML
EPOD_SYS_EXPORT.EmailPOD will be changed to add an EPOD_CONFIG_REPORT parameter to call of GetReportHTML.
EPOD_SYS_EXPORT.ExportPOD will be modified to add an EPOD_CONFIG_REPORT parameter to call of GetReportHTML.
After the call of this, if the Report Format is Configurable (i.e. EPOD_CONFIG_REPORT as a valid DAL object and has a value) and Images are included in this generation (ECR_EMAIL_INC_IMAGES_IND > 0) and they are to be split (ECR_EMAIL_IMAGES_IND == 2):
- Save the ReportHTML into a new variable (ImageHTML)
- In ReportHTML, remove images by replacing with a pattern match through the comments added above.
- In ImageHTML, remove POD by replacing with pattern match through comments added above.
- Call EPOD_SYS_EMAIL.GeneratePDFFromHTML on ReportHTML as normal, adding the parameter for orientation, defaulting to "P" if not present. Store as object PDF.
- Call EPOD_SYS_EMAIL.GeneratePDFFromHTML a second time for imageHTML if present. Store as object ImagesPDF.
- For each PDF object generated, call SendFile to export the file through the parameters specified. Note that the images file must have "_images" appended to the filename, by appending this to the value of EPOD_XF_CONFIG.EPL_FILENAME before calling SendFile for the Images PDF. For example, in this configuration, a job with code "1234567890" with images will be generated as "POD_1234567890.pdf" for the POD and "POD_1234567890_images.pdf" for the images file.
Note: The comment pattern match will be as follows:
\<\!--\sPOD\sSTART.*POD\sEND\s--\> - for POD \<\!--\sIMAGES\sSTART.*IMAGES\sEND\s--\> - for IMAGES
Appendix A: TEST PLAN
| Test Script / Scenario Reference | POD DMS Export Images | Call Number(s): 343616 SCR-ADD-1 |
| Test Script / Scenario Description | Testing the export to POD can split images. | PASS / ISSUES / FAIL |
| Menu Access | Administration/Auto-Export | |
| Pre-requisites | A system configured as Marshalls. | Tested By: |
| Test Objective | To test: Auto-Export may export POD and image files separately. | Date: |
| Step | Action | Result | Remarks | P/F |
| 1 | Export Tests | |||
For these tests:
|
||||
| 1.01 | Check Export email from AutoExport. | All jobs should have a report emailed to the email address against the jobs and the site email address. Every email should have a single attachment. Photos will not be present in the job configured to not have images at all, and the job to not have email images. | ||
| 1.02 | Check Export to POD in FILE system | The Job with the report configured for Split images should have two files, one named POD_(EPL_JOB_CODE).pdf containing just the POD, and one named POD_(EPL_JOB_CODE)_Images.pdf containing just the images.
The Job with the report configured to not split images should have one file named POD_(EPL_JOB_CODE).pdf containing the POD and the images. The Job with the report configured to not display images should have one file named POD_(EPL_JOB_CODE).pdf containing just the POD. All files should be in the File folder. |
||
| 1.03 | Check Export to POD in FTP server | The Job with the report configured for Split images should have two files, one named POD_(EPL_JOB_CODE).pdf containing just the POD, and one named POD_(EPL_JOB_CODE)_Images.pdf containing just the images.
The Job with the report configured to not split images should have one file named POD_(EPL_JOB_CODE).pdf containing the POD and the images. The Job with the report configured to not display images should have one file named POD_(EPL_JOB_CODE).pdf containing just the POD. All files should be in the FTP folder. |
||
| 1.04 | Run the report from Admin and click the Send email button from the produced report | All jobs should have a report emailed to the email address entered. Every email should have a single attachment. Photos will not be present in the job configured to not have images at all, and the job to not have email images. |
Appendix B: Quote & Document References
| Cost Details | ||||
| Activity | Estimate No. of Days |
No. of Days | Rate per Day (£) | Cost (£ Exc. VAT) |
| Requirements | 0.00 | 0.00 | 750 | £0.00 |
| Change Request Evaluation | 0.00 | 0.00 | 750 | £0.00 |
| Functional Specification | 0.75 | 0.75 | 750 | £562.50 |
| Technical Specification | 0.00 | 0.00 | 750 | £0.00 |
| Development | 2.25 | 2.25 | 750 | £1,687.50 |
| Testing and Release | 0.50 | 0.50 | 750 | £375.00 |
| Implementation | 0.25 | 0.25 | 750 | £187.50 |
| Project Management | 0.25 | 0.25 | 750 | £187.50 |
| TOTAL | 4.00 | 4.00 | £3,000.00 | |
| Estimate excludes training, release to live and go live support. |
B.1 References
| Ref No | Document Title & ID | Version | Date |
| 1 | EST 343616 POD DMS Export Images | 0.1 | 15/08/2017 |
B.2 Glossary
| Term | Definition |
|---|---|
| EPOD | Electronic Proof of Delivery. The OBS EPOD system is CALIDUS ePOD. |
| CALIDUS eSERV | The OBS mobile system to complete Service functionality in the field. This is part of the CALIDUS ePOD system. |
| PDA | The mobile device on which the C-ePOD system will run in the field. This can be a Phone, EDA or industrial PDA, running Android. |
| DAL | Data Access Layer. A mechanism for accessing data by the system that is removed from the application, allowing for simplified access and providing protection to the data, as only approved DAL methods can be used to modify it. |
| GPS | Global Positioning System. A mechanism of retrieving accurate positioning information in the form of Latitude and Longitude (Lat-Long) co-ordinates from a device. |
| GPRS, 3G, HSDPA, Data Service | All terms referring to mobile device network connectivity, and the speed at which the device connects to the internet. |
B.3 Authorised By
Matt Turner | OBSL Account Manager | _____________________________ |
Simon Martin | Customer Representative | _____________________________ |
Debbie Linley | Customer Representative | _____________________________ |
