FS 312827 BIU Force Product Qty Entry

From Calidus HUB





Aptean Logo.png







BIU Group

BIU Force Product Qty Entry

CALIDUS ePOD

18th October 2013 - 0.1
Reference: FS 312826 312018/6











































Functional Overview

Client Requirement

For Job Type 1 - Standard Planned Collection of Recycled clothing from Supermarket banks

  • Choose collection job
  • Review job as normal and confirm arrival. Co-Pilot has not been purchased yet but is on the table.
  • Containers will represent banks. Client will click on or scan each container to confirm how many bags have been collected. If container is so damaged that no bags will be collected,the container can be cancelled using the existing cancellation process. If the bank is damaged but bags can still be collected then the container should be claused. A claused container will still need a picture.
  • Default qty for product in container is 0. User must choose change qty to indicate how many bags have been collected. No reason code should be entered at this stage.
  • No signature is required
  • At the end of a load that contains these collections, the user must enter weighbridge ticket no (up to five numeric digits) and weight (up to five numeric digits)


Solution Overview

The Job Details tab will always be displayed, showing the customer contact information and any instructions on the Job.

On the Collection or Delivery process, a Products or Containers tab will be displayed (if there are any Banks to be serviced) - this will be labelled as 'Banks' for the BIU style. Each line will be a Bank to be processed (either collected or cancelled). The user will click on or scan each bank and will be prompted to confirm how many bags have been collected, through a pop-up quantity entry.

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

Android Client

A new BIU style will be created on the Android device, labelled as BIU.

The title of the Products tab will be modified for the BIU style, to show as 'Banks', rather than 'Products'. This will require the title of the Products window to be changed to the existing multi-lingual item 'Products' (using Ti.App.style.getString('Products')).

All occurrences of the word 'Product(s)' will be changed to 'Bank(s)', to ensure that the error messages displayed are applicable to the BIU process. This will be achieved through changing all literal references of the word 'Product' to a multi-lingual tag, and adding a replacement of these tags (Product or Products) to 'Bank' or 'Banks', in the labelIDs property object of the BIU-specific configItems object in the Ti.App.style object created in style.js.

The entry of Products on this tab will be modified to, when clicking on a line, check the original required quantity to be collected. If this quantity is 0, the form will pop up a quantity entry window before confirming that the product has been collected.

The pop-up window will display a title, a quantity entry box, a Back button and a Confirm button.

If nothing is entered here (or the quantity remains 0) and the user clicks the Confirm button, the pop-up will display a validation error. If Back is clicked (or the back button is pressed) the process should return to the Products grid and the product clicked should not be collected.

If a valid quantity is entered and the Confirm button is pressed, the process should save this quantity and confirm the line as collected as normal.

Note Note: This functionality should also be applied when identifying products through the scanner or typing them in directly through the text-box at the bottom of the screen.


Appendix A: TEST PLAN

Test Script / Scenario ReferenceBIU Force Product Qty EntryCall Number(s): 312826 312018/6
Test Script / Scenario DescriptionTo show that the required quantity entry functionality works.PASS / ISSUES / FAIL
Menu AccessCollection 
Pre-requisitesNo configuration required - this functionality is being required as standard. Ensure there is a collection with multiple loose products created (with all bar one with a zero quantity).Tested By:
 
Test ObjectiveTo test that: Labels display correctly and quantity is prompted for if zero.Date:
 


Step Action Result Remarks P/F
1 PDA      
       
1.01 Start the Load and start the collection. The 'Products' tab should be labelled as 'Banks'.    
1.02 Move to the Products tab (after selecting the Loose Products container (Note: This is dependant on further development to remove the container tab if there is no need for it). All reference to 'Product' should show as 'Bank' instead, including all standard validation messages.    
1.03 Click on a product line with a quantity of zero. A pop-up should be displayed, allowing the user to enter quantity.    
1.04 Press the back button on the device The Products table should be shown. The clicked product should remain and no further action taken.    
1.05 Click on a product line with a quantity of zero. Press the Back button. The Products table should be shown. The clicked product should remain and no further action taken.    
1.06 Click on a product line with a quantity of zero. leave the quantity as zero or blank. Press the Confirm button. A validation error should be displayed, requiring quantity entry. Clearing this error should return to the quantity pop-up.    
1.07 Enter a valid quantity. Press the Confirm button. The quantity should be saved. The Products table should be displayed again, with the completed product marked as collected and removed from the list.    
1.08 Click on a product line with a non-zero quantity. The Products table should be displayed again, with the completed product marked as collected and removed from the list.    
1.09 Complete all products and complete the collection. Check the data. The job should be completed. All product quantities should be passed back to the server as entered by the user.    


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.25 0 £0.00
Technical Specification 0.00 0 £0.00
Development 1.25 0 £0.00
Testing and Release 0.25 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 NoDocument Title & IDVersionDate
1UG 291094 EPOD Admin User Guide2.04/4/2012
2UG 291097 EPOD Client User Guide3.023/4/2013
3REQ 312018 Bag It Up EPOD Requirements0.301/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


Barry Preece
OBS Project Manager		_____________________________


Client Representative		_____________________________
Retrieved from ‘https://calidusassist.adcservices.apteancloud.com/calidus-assist/OBS/index.php?title=FS_312827_BIU_Force_Product_Qty_Entry&oldid=1283’