FS 313052 2nd Contact Number
Andrew Porter
2nd Contact Number
CALIDUS ePOD
28th October 2013 - 0.1
Reference: FS 313052 312105/4
Contents
Functional Overview
Client Requirement
A second telephone number is required against the customer and job address information.
Solution Overview
The Job Details screen allows the user to contact the customer (through text or phone), or navigate to the customer's address (available only after choosing to start the job).
A second telephone number is required against the customer and job address information, allowing the user to enter a land or mobile number. The Job Details form will on the device will be modified to display this new number, and to modify the SMS and Call buttons to take best advantage of this.
Note: The Andrew Porter back-end system supports up to 3 contact numbers - this will be mapped to the 2 numbers specified above, through the interface and through validation in the back-end contact information data entry form.
Scope
- These changes will be made in the latest version of the CALIDUS ePOD product only.
- The changes will be made to the Android CALIDUS ePOD client only.
Set-up
Pre-requisites
Menu Structure
Data
Functional Description
Import/Export
Note: Although there is no explicit change to the import or export, the following should be noted in the documentation and the customers informed:
- The field EPL_TELEPHONE can contain multiple contact numbers, delimited by a vertical bar character.
The generic XSD and mapping spread-sheets should be modified to indicate this. Any external developers mapping an interface to CALIDUS ePOD should be informed of this.
Admin
The existing EPL_TELEPHONE field used to store the contact number will be modified to allow multiple contact numbers to be specified. This should be through a delimiter per number specified, in this case vertical bar (|).
This will affect multiple screens:
- Customers Maintenance (customer_maint.aspx)
- Job Details (Job_Details.aspx)
Customers Maintenance
The data when found in the grid should not be modified.
When selecting a grid line or adding a new customer, the Edit/Entry pop-up should be modified.
The Telephone field should be moved to the right, under contact. A second telephone entry box should be added under this - no label is required for this field.
When Editing data on this screen, the content of the telephone field EPL_TELEPHONE should be examined. If the field contains a vertical bar, the data should be split and displayed in the multiple separate fields. If more than two are found, the remaining will be discarded.
When adding or editing data on this screen, the user should be able to enter 2 telephone numbers, one in each field.
When saving a new or edited record, the screen should consolidate the values in the two Telephone entry boxes into one string, delimited by a vertical bar character. Note that, if only one is entered in either box, no vertical bar character is required.
Job Details
The data when found in the grid should not be modified.
When selecting a grid line or adding a new job, the Edit/Entry pop-up should be modified.
A second Telephone entry box should be added under the existing Telephone entry box - no label is required for this field.
When Editing data on this screen for a Customer or Job Address, the content of the telephone field EPL_TELEPHONE should be examined, from the Job Address or Customer as normal. If the field contains a vertical bar, the data should be split and displayed in the multiple separate fields. If more than two are found, the remaining will be discarded.
When adding Job Address data on this screen, the user should be able to enter 2 telephone numbers, one in each field.
When selecting a new customer, the content of the telephone field EPL_TELEPHONE should be examined for the customer selected. If the field contains a vertical bar, the data should be split and displayed in the multiple separate fields. If more than two are found, the remaining will be discarded.
When saving a new or edited record, the screen should consolidate the values in the two Telephone entry boxes into one string, delimited by a vertical bar character. Note that, if only one is entered in either box, no vertical bar character is required.
Android Client
Note: The Job Details, Collection/Delivery and Services forms are affected by this change.
When displaying the telephone contact number in any screen (EPL_TELEPHONE) the data should be examined.
If the field contains a vertical bar character, the data should be split on that character and all numbers displayed vertically aligned.
In the Job Details screen, if there are multiple contact numbers as shown above, and the user clicks the SMS or Call buttons, the screen should display a pop-up choice of the two contact numbers, through an Alert pop-up. When the user chooses a number, the normal Call or SMS functionality should be called, as now.
If there is only one contact number, the SMS and Call buttons should operate as now.
Appendix A: TEST PLAN
| Test Script / Scenario Reference | 2nd Contact Number | Call Number(s): 313052 312105/4 |
| Test Script / Scenario Description | To show that 2nd Contact Number functionality works as required | PASS / ISSUES / FAIL |
| Menu Access | Collection/Delivery | |
| Pre-requisites | No configuration required - this functionality is being required as standard. Ensure there are collection and delivery jobs with none to multiple contact numbers supplied. | Tested By: |
| Test Objective | To test that: Multiple contact numbers can be entered in Admin and; Multiple Contact numbers can be displayed on the android device and used for contact purposes. | Date: |
| Step | Action | Result | Remarks | P/F |
| 1 | Admin | |||
| 1.01 | Click New in the Customers Maintenance screen. | The pop-up should be displayed, allowing entry of 2 telephone numbers. | ||
| 1.02 | Enter a customer with no telephone information. Save | Nothing should be displayed in the Telephone column in the grid for this customer. | ||
| 1.03 | Enter a customer with only 1 contact number, in the first field. Save. | Only this number and no other characters should be displayed in the Telephone column in the grid for this customer. | ||
| 1.04 | Select and Edit the second customer. | The pop-up should display the telephone number. | ||
| 1.05 | Move the number to the second field and save. | Only this number and no other characters should be displayed in the Telephone column in the grid for this customer. | ||
| 1.06 | Edit the first customer and enter two numbers. Save. | The two numbers should be saved with a separating vertical bar character, and should be displayed as such in the Telephone column in the grid for this customer. | ||
| 1.07 | Click New in the Job Details screen. | The pop-up should be displayed, allowing entry of 2 telephone numbers. | ||
| 1.08 | Select a customer with no telephone information. | Nothing should be displayed in the Telephone fields. | ||
| 1.09 | Select a customer with 1 number. | The number will be displayed in the Telephone field. | ||
| 1.10 | Select a customer with 2 numbers. | Both numbers will be displayed in the Telephone fields. | ||
| 1.11 | Enter a Job Address instead of a customer. Enter no telephone information. Save. | Nothing should be saved in the Telephone field. | ||
| 1.12 | Edit the job. | No telephone numbers should be shown in the Job Address. | ||
| 1.13 | Enter 1 telephone number. Save and re-edit. | 1 telephone number should be shown. | ||
| 1.14 | Enter 2 telephone numbers. Save and re-edit. | 2 telephone numbers should be shown. |
| Step | Action | Result | Remarks | P/F |
| 2 | PDA | |||
| 2.01 | Select a job with no contact numbers. | The Job Details form should display nothing in the Telephone details. | ||
| 2.02 | Click the Call and SMS buttons. | Nothing should happen. | ||
| 2.03 | Start/Arrive the job (Delivery, Collection or Service) | The Job Details form should display nothing in the Telephone details. | ||
| 2.04 | Select a job with 1 contact number. | The Job Details form should display the single number in the Telephone details. | ||
| 2.05 | Click the Call and SMS buttons. | A Call or SMS should start directly, with no confirmation from the user. | ||
| 2.06 | Start/Arrive the job (Delivery, Collection or Service) | The Job Details form should display the single number in the Telephone details. | ||
| 2.07 | Select a job with 2 contact numbers. | The Job Details form should display both numbers in the Telephone details. | ||
| 2.08 | Click the Call and SMS buttons. | A pop-up confirmation should appear, asking for confirmation of the number to be used. | ||
| 2.09 | Press the Back button | The confirmation should disappear and return to the job details form. | ||
| 2.10 | Click the Call and SMS buttons. Select a number from the confirmation. | A Call or SMS should start using the selected number. | ||
| 2.11 | Start/Arrive the job (Delivery, Collection or Service) | The Job Details form should display nothing in the Telephone details. |
| Step | Action | Result | Remarks | P/F |
| 3 | Export | |||
| 3.01 | Export a job with a customer with no telephone details. | Nothing should be exported in the Telephone tag. | ||
| 3.02 | Export a job with a customer with 1 telephone number. | The export's Telephone tag should contain this number only. | ||
| 3.03 | Export a job with a customer with 2 telephone numbers. | The export's Telephone tag should contain both numbers, delimited with a vertical bar. | ||
| 0.00 | Export a job with a Job Address with no telephone details. | Nothing should be exported in the Telephone tag. | ||
| 3.04 | Export a job with a Job Address with 1 telephone number. | The export's Telephone tag should contain this number only. | ||
| 3.05 | Export a job with a Job Address with 2 telephone numbers. | The export's Telephone tag should contain both numbers, delimited with a vertical bar. |
Appendix B: Quote & Document References
| Cost Details | |||
| Activity | No. of Days | Rate per Day (£) | Cost (£ Exc. VAT) |
| Requirements | 0.00 | 0 | £0.00 |
| Change Request Evaluation | 0.00 | 0 | £0.00 |
| Functional Specification | 0.50 | 0 | £0.00 |
| Technical Specification | 0.00 | 0 | £0.00 |
| Development | 2.75 | 0 | £0.00 |
| Testing and Release | 0.50 | 0 | £0.00 |
| Implementation | 0.00 | 0 | £0.00 |
| Project Management | First argument to "number_format" must be a number. | 0 | £First argument to "number_format" must be a number. |
| TOTAL | First argument to "number_format" must be a number. | £First argument to "number_format" must be a number. | |
| Estimate excludes training, release to live and go live support. |
B.1 References
| Ref No | Document Title & ID | Version | Date |
| 1 | UG 291094 EPOD Admin User Guide | 2.0 | 4/4/2012 |
| 2 | UG 291097 EPOD Client User Guide | 3.0 | 23/4/2013 |
| 3 | REQ 312105 Andrew Porter EPOD Requirements | 0.3 | 01/10/2013 |
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
Julie Scott | OBS Project Manager | _____________________________ |
Hayley Ashton | Client Representative | _____________________________ |
