FS 333750 Allow Job Details UDF to be amended
OBS Logistics Ltd
Allow Job Details UDF to be amended
CALIDUS EPOD
8th April 2016 - 0.1
Reference: FS 333750
Contents
Functional Overview
Client Requirement
On the CALIDUS ePOD Admin system require the ability to enter or change the trailer ID against a job and the ability to change the job details UDF.
Solution Overview
If the job has been completed, the Edit button is only be present if edit functions are allowed, defined by the existing Site flag 'Allow Update Functions'.
The Job Details pop-up will have the following changes made:
Clicking the Edit button for a completed job will issue a warning to the user before allowing them to edit the job.
The trailer ID of the job will be added as a new field on the Details tab. The user will be able to change this field even if the job has been completed, by clicking the Edit button.
A new job detail UDF tab will be added to allow the display and editing of job details UDF for the job.
Whenever the user selects the job details UDF tab the system will build and show the job details UDF questions in the same way as the device does.
The user will be allowed to edit the values of the UDF fields.
Any UDF fields that are data-bound (e.g. has a full stop in the ID of the field) will not be editable in the UDF tab - this should be edited in the Details tab. The data-bound UDF fields should still be displayed, however.
When saving any changes to the job details UDF, this will save the entered job details onto the device. No validation checks will be made on this screen.
Scope
Set-up
Pre-requisites
Menu Structure
Data
Functional Description
Admin - Job Details
If the job has been completed, the Edit button is only be present if edit functions are allowed, defined by the existing Site flag 'Allow Update Functions'. This is as now.
Clicking the Edit button for a completed job will issue a warning confirmation alert to the user before allowing them to edit the job.
The warning should say: "This job is at status <status> and should not be changed. Are you sure you want to edit this job?". The alert should offer 2 options: OK and Cancel.
If Cancel is clicked, the user should be returned to the edit popup, and the popup should still be disabled.
If OK is clicked, the user should be returned to the edit popup, and the popup should be enabled for editing.
Job Details tab, showing the added tab and field
The trailer ID of the job will be added as a new field on the Details tab in the position shown above.
This field should be enabled for editing at all times, even after job completion or cancellation, when the Edit button is clicked and confirmed.
A new Job Details UDF tab will be added to allow the display and editing of job details UDF for the job. Note that this will not be displayed when creating a new job through the New button, nor if there is no value in the Job Detail UDF datafield EPOD_JOB.EPL_UDF_JOBDETS.
Whenever the edit popup is displayed, the Job Details UDF (from EPOD_JOB.EPL_UDF_JOBDETS) will be built using the preview code available in the existing UDF Configuration screen. This will be read-only.
If the 'Edit button is pressed and confirmed, the UDF should be enabled for entry. Only fields with an ID that does not contain a full stop will be enabled. The user will be allowed to edit the values of the UDF fields.
When saving changes to the job using the Save button, the popup will first validate before saving. This validation will be modified as follows:
- The Trailer ID will be limited to the maximum length of the trailer ID (20 characters).
No other additional validation will apply.
On successful validation, the popup screen will save all details back to the EPOD_JOB table. This will be amended to include:
- The UDF fields will be converted back into UDF. This value will be saved back into the EPOD_JOB field.
- The value of the trailer ID will also be saved into the trailer ID field.
Appendix A: TEST PLAN
Test Script / Scenario Reference | Allow Job Details UDF to be amended | Call Number(s): 333750 |
Test Script / Scenario Description | To test editing of Job Details UDF and Trailer ID | PASS / ISSUES / FAIL |
Menu Access | Tasks/Jobs | |
Pre-requisites | Job Details UDF need to be configured for the site or job group. Jobs must be completed, cancelled and pending. | Tested By: |
Test Objective | To confirm: UDF may be edited; the trailer ID may be edited. | Date: |
Step | Action | Result | Remarks | P/F |
1 | Admin - Job Details | |||
1.01 | Create a new job | No Job Details UDF tab is displayed. The Trailer ID is displayed. | ||
1.02 | Enter the details of a job including the trailer ID. Save. | All details are saved and can be seen on the data and the screen when editing again. | ||
1.03 | Click Select against a Pending job. | As there is no UDF for this job yet, the Job Details UDF tab should not be displayed. The Trailer ID should be displayed, but disabled for entry. | ||
1.04 | Click Edit | The Trailer ID should be enabled for editing. | ||
1.05 | Change the trailer ID and save. | All details are saved and can be seen on the data and the screen when editing again. | ||
1.06 | Click Select against a Complete job. | The Job Details UDF tab should be displayed with the entered values against that job. The Trailer ID should be displayed. The UDF and Trailer ID should be disabled for entry. | ||
1.07 | Click Edit | An Alert Confirmation dialogue should be displayed as described. | ||
1.08 | Click Cancel | The alert should be removed, but the job details and UDF should still be disabled for editing. | ||
1.09 | Click Edit then OK | The Trailer ID and Job Details UDF should be enabled for editing. | ||
1.10 | Change the UDF values and save. | All UDF details are saved and can be seen on the data and the screen when editing again. |
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 | 0 | £0.00 |
Change Request Evaluation | 0.00 | 0.00 | 0 | £0.00 |
Functional Specification | 0.25 | 0.25 | 0 | £0.00 |
Technical Specification | 0.00 | 0.00 | 0 | £0.00 |
Development | 1.25 | 1.25 | 0 | £0.00 |
Testing and Release | 0.25 | 0.25 | 0 | £0.00 |
Implementation | 0.25 | 0.25 | 0 | £0.00 |
Project Management | 0.25 | 0.25 | 0 | £0.00 |
TOTAL | 2.25 | 2.25 | £0.00 |
Estimate excludes training, release to live and go live support. |
B.1 References
Ref No | Document Title & ID | Version | Date |
1 |
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 Tipping | OBS Logistics Project Manager | _____________________________ |