FS 314964 Palletforce Interface changes

From Calidus HUB





Aptean Logo.png







PartnerLink

Palletforce Interface Changes

CALIDUS ePOD

7th February 2014 - 0.1
Reference: FS 314964











































Functional Overview

Client Requirement

Palletforce Interface changes. Add Delivery Status Code and POD Notes.

File:FS 314964 1.PNG

Solution Overview

The Palletforce export format will be altered in line with their recent format changes.

The export format will be altered to include two extra fields: Delivery Status Code and POD Notes used to indicate that the delivery has been successful but with exceptions or minor damages.

In order to achieve this, a reason code may be prompted for when making a successful delivery.

Scope

  • These changes will be made in the latest version of the CALIDUS ePOD system.

Set-up

Pre-requisites

Menu Structure

None

Data

New "Clause" type reason codes will be expected to be setup for the Palletforce Job Group. Initially reason codes of 'PODC' and 'PODD' will be expected to be defined with descriptions of 'Delivered with Exception' and 'Delivered with Damage' respectively.

Functional Description

Database Changes

Table EPOD_JOB_GROUPS requires the following modifications:

  • EPL_CLAUSE_DELIVERY (New field) - nvarchar(1)

The existing EPOD_JOB_GROUP DAL object will be changed to include:

  • EPL_CLAUSE_DELIVERY of EPOD_JOB_GROUP

Existing packages will be modified to allow the creating, editing and selecting of the new fields, including but not limited to:

  • EPOD_JOB_GROUPS_INSERT
  • EPOD_JOB_GROUPS_SEARCH
  • EPOD_JOB_GROUPS_SELECT
  • EPOD_JOB_GROUPS_SELECT_UPDATED_DATA
  • EPOD_JOB_GROUPS_UPDATE

Admin Changes

The Reason Code Maintenance screen (Reason_code.aspx) will be altered to include a new 'Type' of 'Claused' in the 'Type' drop-down list. Reason codes of this type will be used to indicate a complete delivery with exceptions, e.g. 'PODD' or 'PODC'.

The Job Group Maintenance screen (job_group.aspx) will be altered to include a 'Claused Delivery' flag. This will appear as a drop-down list in the 'PDA' tab. The list will have three possible values:

  • '0' - don't prompt for a claused delivery description or claused reason code
  • '1' - prompt for a claused delivery description without a claused reason code
  • '2' - prompt for both a claused delivery description and a claused reason code

Note that if the current Site level 'Claused Delivery' tickbox is set, then this will mean that the 'Claused Delivery' text box will appear regardless of the value of the Job Group setting.

The Container Maintenance screen (product_containers.aspx) will be altered to allow the user to choose a reason code when entering a Claused Delivery. In the Container Details popup box, the user is currently able to enter free text within the Claused Delivery field. The program will be changed to check the 'Claused Delivery' flags mentioned above. If the flag is set to the appropriate value and if there are any 'Claused' type reason codes defined for the Job Group in question, then a drop-down list will appear labelled as 'Claused Reason'. The user will be able to choose a reason code from the list. The list will not be made a required field.

Palletforce File Export Changes

Two extra fields will be added to the current layout for the outbound Palletforce file:

  • Delivery Status Code - to be set as EPL_REASON_CODE of EPOD_CONTAINER if populated. If not then set as 'POD'.
  • POD Notes - to be set as EPL_CUST_COMMENTS of EPOD_CONTAINER if populated. If not and EPL_REASON_CODE of EPOD_CONTAINER is populated, then set as EPL_DESCRIPTION of EPOD_REASON_CODE for that reason code record. Otherwise, this field should be left blank.

Note that the layout is to remain as a comma-separated file so the new fields will need to be separated with extra commas.

Message Process Changes

The message process class (messageprocess.cs) that sends data to the PDA will need to verified to ensure that the EPL_CLAUSE_DELIVERY flag is sent as part of the Job Group message.

Pda Changes

Table PDA_JOB_GROUPS requires the following modifications:

  • EPL_CLAUSE_DELIVERY (New field) - nvarchar(1)

The existing PDA_JOB_GROUPS DAL object will be changed to include:

  • EPL_CLAUSE_DELIVERY of PDA_JOB_GROUPS

The login request process will be altered to allow the EPL_CLAUSE_DELIVERY flag to be populated when Job Group level data is passed in.

The Claused Container pop-up screen will be altered to check for the EPL_CLAUSE_DELIVERY of PDA_JOB_GROUPS flag. If this is set to '2', then the program will check for the existence of PDA_REASON_CODES for the Job Group in question of Reason Type 'CLA'. If records exist then a new drop-down list will be displayed Labelled as 'Claused Reason' to allow the user to choose the reason for marking the delivery as claused. The list will not be made a required field.


Appendix A: TEST PLAN

Test Script / Scenario ReferencePalletforce Interface ChangesCall Number(s): 314964
Test Script / Scenario DescriptionTo test the production of the outbound Palletforce export process to ensure the new Claused delivery fields are included in CALIDUS ePODPASS / ISSUES / FAIL
Menu AccessJob Group Maintenance, Reason Code Maintenance 
Pre-requisitesEnsure that Palletforce job groups are defined against the required sitesTested By:
 
Test ObjectiveTo test the additional fields required for the Palletforce export process are populated. Check that the claused reason code field is prompted for on the device.Date:
 



Step Action Result Remarks P/F
1 Server/PDA - DTO      
  Ensure that there are multiple configurations, one for site 1 and one for site 2.      
1.01 Log on a PDA and check the Server logs. All UDF configuration sent to the device.    
1.02 Check the device database using SQLite Note Note: Only on an emulator. All UDF configuration is stored in the device database.    



Step Action Result Remarks P/F
2 PDA - Optionality      
  Start with no UDF configuration      
2.01 Add an Info UDF Configuration to the Site. Log on and start a Service job. Check the Info tab. All configurable fields required are present on the screen in a scrolling view, the final field showing that this is the correct Key Type and Key Value.    
2.02 Add a Pre-work UDF Configuration to the Site. Log on and start a Service job. Check the Info tab. A Pre-work check button is present with a label as configured. When pressed, all configurable fields required are present on the pop-up in a scrolling view, the final field showing that this is the correct Key Type and Key Value. All required buttons are present.    
2.03 Add a Diagnosis UDF Configuration to the Site. Log on and start a Service job. Check the Info tab. All configurable fields required are present on the screen in a scrolling view, the final field showing that this is the correct Key Type and Key Value.    
2.04 Add a Post-work UDF Configuration to the Site. Log on and start a Service job. Check the Info tab. A Post-work check button is present with a label as configured. When pressed, all configurable fields required are present on the pop-up in a scrolling view, the final field showing that this is the correct Key Type and Key Value. All required buttons are present.    
2.05 Repeat the first 4 tests, this time configuring for Job Group. The Job Group configurations should be used.    
2.06 Ensure the job being started has no Service Group set. Repeat the first 4 tests, this time configuring for Product Group. The Job Group UDF configurations should be used, as there is no Service Group present.    
2.07 Ensure the job being started has a Service Group set. Repeat the first 4 tests, this time configuring for Product Group. The Product Group UDF configurations should be used.    
2.08 Ensure the Service configuration allows entry of Product Group. Ensure a UDF configuration for a different product group exists. Change the Service Group to the new Product Group. The Post-work UDF configuration should be refreshed to the new Product Group's UDF configuration.    
2.09 Ensure UDF configurations exist for different sites and Job Groups. Retest the above using these new configurations. The UDF configurations of the expected Site, Job Group or Product Group are used, as expected.    


Step Action Result Remarks P/F
3 PDA - Process      
  Ensure a UDF configuration is set up for all areas (Info, Diagnosis, Pre-work, Post-work) for the Job Group of the job being processed.      
3.01 Click the Info tab All fields required to be entered at Info stage should be shown on the screen. A Pre-work button should be shown, labelled correctly.    
3.02 Click a Text field. A Text keyboard is shown to enter data.    
3.03 Enter data The data entered should be shown in the field.    
3.04 Click the Barcode button (requires a device). The Barcode Scan screen should be shown.    
3.05 Scan a barcode The data scanned should be shown in the field.    
3.06 Click a Numeric field A Number keyboard is shown to enter data.    
3.07 Enter data The data entered should be shown in the field.    
3.08 Check and Uncheck Options and Check Box elements The data should be entered as expected.    
3.09 Check a Drop-Down List (DDL) field. The default value should be selected.    
3.10 Click the DDL field. All options should be displayed for entry.    
3.11 Select a different one. The selected data should be shown in the field.    
3.12 Click the Pre-work button. A pop-up window should be displayed, showing the required fields in a scrolling view. The Save and Pre-completed buttons should be displayed.    
3.13 Do not enter any required data - click the Save button. A validation failure message should be displayed. The offending field should be highlighted in the screen.    
3.14 Click Pre-completed A confirmation pop-up should appear ("Please confirm that Risk Assessments have been pre-completed.), allowing Yes or No entry.    
3.15 Click No The Pop-up screen should stay - no action taken.    
3.16 Click Pre-completed and Yes. The Info tab should be re-displayed, as the Pre-work checks have been cancelled.    
3.17 Click the Pre-work button and enter all information. Click the Confirm button. The Info tab should be re-displayed, as the Pre-work checks have been saved.    
3.18 Click the Diagnosis tab All fields required to be entered at Diagnosis stage should be shown on the screen. A Post-work button should be shown, labelled correctly.    
3.19 Check entering data. As expected.    
3.20 Click the Post-work button. A pop-up window should be displayed, showing the required fields in a scrolling view. The Save and Pre-completed buttons should be displayed.    
3.21 Do not enter any required data - click the Save button. A validation failure message should be displayed. The offending field should be highlighted in the screen.    
3.22 Click Pre-completed A confirmation pop-up should appear ("Please confirm that Risk Assessments have been pre-completed.), allowing Yes or No entry.    
3.23 Click No The Pop-up screen should stay - no action taken.    
3.24 Click Pre-completed and Yes. The Info tab should be re-displayed, as the Post-work checks have been cancelled.    
3.25 Click the Post-work button and enter all information. Click the Save button. The Info tab should be re-displayed, as the Post-work checks have been saved.    
3.26 Before Pre-work and Post-work validations have been completed, click Done. Validation messages should be displayed, showing the errors.    
3.27 Before all required data on Info and Diagnosis tabs is entered, click Done Validation messages should be displayed, showing the errors. The first offending field should be highlighted on the tab.    
3.28 When all complete, click Done All data is saved and the job moves on to Completion (Signature Entry).    
3.29 Complete the Job. The job is sent back to the server (check the Server web-service logs). The job is saved, with all UDF data saved into the correct new fields (check the database).    



Appendix B: Document References

B.1 References

Ref NoDocument Title & IDVersionDate
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


Phil Harding
OBS Project Manager		_____________________________

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