EST 333750 Allow Job Details UDF to be amended
 |
CHANGE REQUEST ESTIMATE |
| Client | HEW | Project | DEV | Site | BSE |
| Client Reference | Aptean Reference | 333750 | Estimate Version | 0.3 | |
| Prepared By | Rob McGee | Estimate Date | 02/03/2016 | ||
| Invoice Reference | Priority | 3 | |||
| Customer | System Version | 3.X | |||
| Client Request |
| On the device require the ability to enter or change the trailer ID against a job and the ability to change the job details UDF from the driver signature screen. On the admin system require the ability to enter or change the trailer ID against a job and the ability to change the job details UDF. |
| Aptean Solution |
ePOD Admin Changes: A new 'Amend Job Details UDF' flag will be added to the job group maintenance page. This will control whether or not job details UDF can be amended on both the device's driver signature screen and the admin system job details page. 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:
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. When saving any changes to the job details UDF this will again be done in the same was as on the device, including validating all entries based on the UDF configuration before saving any changes.
The ePOD device currently copies the trailer ID from the load to the job when the job is completed. This is done regardless of any trailer ID set against the job (i.e. this currently overwrites any trailer ID stored against the job). This will be changed so the trailer ID is copied from the load to the job when the job is started - this is so the trailer ID for the job is available when the user opens the collection/delivery screen. Also, the trailer ID will only be copied from the load to the job if the job does not already have a trailer ID (i.e. the trailer ID against the job is blank). This is to prevent any trailer ID entered for the job in the admin system being overwritten by the trailer ID from the load. The job details UDF creation will be changed to pass the job to the UDF creation in order to allow UDF fields to be associated with a value on the job (i.e. the trailer ID). The UDF creation will be changed so that when building the UDF fields if a field is associated with a field from the database the value for the UDF field will automatically be set to the value of the associated field. This will affect all UDF including the load metrics UDF and the job details UDF. This change will mean when UDF fields are shown on the device:
The signature screen will then be changed to allow a new job details UDF tab to be shown when capturing a driver signature. This tab will only be shown if the new 'Amend Job Details UDF' (see admin changes above) is set and if job details UDF exist for the job/jobs being signed for. When shown, this tab will appear in the same place as the customer signature terms and conditions tab (i.e. below the signature for portrait or to the right for landscape). If the signature is being captured for a single job, the tab will just show the job details UDF for that job. If the signature is being captured for multiple jobs, the tab will show the display job reference followed by the job details UDF for each job. In all cases the job details UDF tab will be a scrollable tab so that if the data shown does not fit into the space available the user will be able to scroll to see the remaining data.
When the changes are released, OBS will update the existing job details UDF to add a trailer ID field. This will be the same as the trailer ID field included on the load metrics with the exception that this text field will be associated with the trailer of the job. |
Note: Any UDF fields that are data-bound (e.g. the trailer ID, which is already on the Details tab) 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.
 Warning: | Unknown costs for client/year (HEW/2016) |
| Cost Details | |||
| Activity | Hours | Rate per hour (£) | Cost (£ Exc. VAT) |
| Requirements | 0.00 | 0.00 | £0.00 |
| Change Request Evaluation | 2.25 | 0.00 | £0.00 |
| Functional Specification | 1.25 | 0.00 | £0.00 |
| Technical Specification | 1.25 | 0.00 | £0.00 |
| Development | 4.75 | 0.00 | £0.00 |
| Testing and Release | 1.00 | 0.00 | £0.00 |
| Implementation | 0.25 | 0.00 | £0.00 |
| Project Management | 0.25 | 0.00 | £0.00 |
| TOTAL | 11.00 | £0.00 | |
| Estimate excludes training, release to live and go live support. |
|
Copyright © Aptean 2016. |
