View source for FS 343516 SCR-339867-06 Unmanned Location Process

<div class="noprint">
{{#vardefine:Client|MARS}}
{{#vardefine:ClientName|Marshalls Stone}}
{{#vardefine:System|''CALIDUS'' ePOD}}
{{#vardefine:Doc_Title|Unmanned Location Signature}}
{{#vardefine:Version|1.0}}
{{#vardefine:Date|14th June 2017}}
{{#vardefine:Reference|343516 SCR-339867-06}}
{{#vardefine:Year|2017}}
</div>
{{Doc_Title
|Client={{#var:ClientName}}
|System={{#var:System}}
|Title={{#var:Doc_Title}}
|Reference=FS {{#var:Reference}}
|Version={{#var:Version}}
|Date={{#var:Date}}
|Year={{#var:Year}}
}} 

<!-- TOC --> 
<div class="noprint">
= Functional Overview  =

== Client Requirement  ==
SCR-339867-06: Unmanned Location Signature Process

Unmanned locations or delivery out of hours may require that the driver sign PP for the customer, then taking photos to indicate the successful delivery. In the current system without change, this is expected that the driver would sign on behalf of the customer in the customer signature, then have an optional job photo process prompted after this.

{{Note}} For Landscape, it is expected that the Job Photo will always be required for every job.

It is requested that the mobile application is changed to account for this unmanned location process. It is expected that some kind of prompt or button press will be requested of the driver at Customer Signature stage (or before) to indicate whether a customer signature can be obtained. If a customer signature cannot be obtained, the device will be expected to require entry of driver signature and then enforce taking of at least one job photo to prove delivery.


== Solution Overview  ==
The C-ePOD system will be modified to allow configuration of this Unmanned Location Signature process. This will have two values initially:
* ''Disabled''
* ''Driver Sign, Photo required''
This will be configured against the Job Group.


On the device, when moving to signature, if this flag is not disabled against the job group, the device will have a button on the screen, labelled as '''Unmanned Location'''.

If a signature is entered in this customer signature screen, the screen will change this button to "Done", so that the driver can accept the customer signature.

If a customer is not available, the driver can click the '''Unmanned Location''' button. The device will prompt for confirmation from the user that no customer is available to sign for the job.

If confirmed, the device will check the configuration against the job group. If set to ''Driver Sign, Photo required'', the device will prompt for the Driver signature, then prompt for a Job Photo, where at least one photo ''must'' be taken by the driver. This will be done regardless of any other configuration set against the jobs or site.


The POD report generator will be modified to recognise this Unmanned Location signature, and will display a blank customer signature rather than "Image Not Available", as it does now. It is expected that no further changes will be required to these formats, as the POD formats are expected to already have the driver signature on the report format (labelled as "Driver Signature for Out of Hours Delivery").


== 	Scope ==
This change will be applied to system version 3.X.


It is expected that this functionality will be enabled only for customer with POD formats where both the Driver and Customer signature is present on the reports, in this case Premier Mortars. If this is enabled for customers without this, modifications may be required to their POD report format to allow for the driver signature to be added. This is not expected to be the case for Landscape. 


<!-- NEW PAGE --> 
= Set-up  =
== Pre-requisites  ==


== Menu Structure  ==


== Data  ==
Each business unit will have a site created for it, expected to be:
* "MAR-LAND" - for Landscape
* "MAR-PREM" - for Premier Mortars

There will be Job Groups set up for each site. The configuration of this is dependent on the requirements of the customer and the way that the data will be received from the ERP.


For Premier Mortars, the job groups may be set up as follows:
* "DELX" - for unmanned collections and deliveries.
* "DEL" - for all other collections and deliveries.
The new Job Group flag "Unmanned Location" will be configured to be "Driver Sign, Photo Required" for the first job group.


For Landscape, it is not expected that this is required, and therefore there will be only one job group ("DEL").


<!-- NEW PAGE --> 
= Functional Description  =
== Server Changes ==
=== Database & Data Access Layer ===
The following field will be added to the Job Group table EPOD_JOB_GROUPS:
* EPL_UNMANNED_LOCATION_IND - int - default 0.

This field will be added to all stored procedures in the database that require it.

This field is required on the device, as part of the Login Response message.

This field is not required to be contained within the Export.

This field is not required to be used when filtering data for selection.


==	Admin Changes ==
=== Job Groups Screen ===
The Job Groups screen (job_group.aspx) will be changed to add this new configuration flag.

[[File:FS_343516_JobGroup1.png|border|600px]]
<br />''Job Group Screen''<br />

The new configuration flag EPL_UNMANNED_LOCATION_IND will be added under the ''Customer Sign Delivery'' flag.

This will be labelled as "Unmanned Location", with the pop-up help of "Defines the Unmanned Delivery process".

This will be a drop-down list of options, defined in the database as:
* 0 (default value), labelled as "Disabled"
* 1, labelled as "Driver Sign, Photo Required"


=== Configurable POD Report ===
The POD report generator (ConfigPOD.aspx) will be modified to recognise this Unmanned Location signature, and will display a blank customer signature rather than "Image Not Available", as it does now. 

The process will check the value of this new flag. If the value is 0, the process will work as now in that, if no image is available for any signature, the standard "Image Not Available" image will be displayed. 

If the value is non-0, the customer signature will be checked to see if it is blank. If so, the standard "Image Not Available" image will not be used - instead, a blank signature will be displayed instead.

{{Note}} This applies to driver and customer signature. 


== Device Changes ==
=== Database & Data Access Layer ===
The following field will be added to the Job Group table EPOD_JOB_GROUPS:
* EPL_UNMANNED_LOCATION_IND - int - default 0.

The PDA_JOB_GROUPS Data Access Layer object will be modified to support this field.

The Logon Response processor will populate this field from the data sent to the device at log on.


=== Post-Job Processes ===
The Post-Job actions will be modified to take into account this new flag.


On the device, when moving to signature, if this flag has a non-0 value against the job group, the device will have a button on the screen, labelled as '''Unmanned Location'''. This will be in the position of the '''Done''' button. This will only be created if the flag is non-0, and if this is a Customer Signature at the end of a job.

If a signature is entered in this customer signature screen, the screen will change this button to "Done", so that the driver can accept the customer signature. The process will display the '''Done''' button over the new '''Unmanned Location''' button.

If the '''Clear''' button is pressed, the '''Done''' button should be moved again.

In either case, the level of the '''Done''' button should be changed to above or behind the '''Unmanned Location''' button, as required.

{{Note}} Alternatively, the '''Done''' button itself can be used for this functionality, changing the label as required.


If a customer is not available, the driver can click the '''Unmanned Location''' button. The device will prompt for confirmation from the user that no customer is available to sign for the job. A pop-up alert should be shown as follows:
* Title: "Unmanned Location"
* Description: "Confirm there is no customer available."
* Buttons: "OK" and "Cancel".

If '''Cancel''' is pressed, the driver will be returned to the Customer Signature screen.

If '''OK''' is pressed, the device will check the configuration against the job group. 

If set to ''Driver Sign, Photo required'' (value 1), the device will prompt for the Driver signature, then prompt for a Job Photo, where at least one photo ''must'' be taken by the driver. This will be done regardless of any other configuration set against the jobs or site.

The function funNextJobEndTask will be used to control this. 

If the driver backs out of any of the steps required by the unmanned location process, the driver will be returned to the job as normal.

Screen Shots
<gallery widths=300px heights=210px perrow=2>
File:FS_343516_Signature1.png|''Prompting for Customer Signature''
File:FS_343516_Signature2.png|''After entry of Customer Signature''
</gallery><br />



<!-- MEDIA LANDSCAPE YES --> 
= Appendix A: TEST PLAN  =
{{TestPlan_Header
|Title={{#var:Doc_Title}}
|Log={{#var:Reference}}
|Description=Testing the Unmanned Location processing
|MenuAccess=N/A
|Prerequisites=A system configured as Marshalls.
|Objective=To test that: the system can be configured with this new Unmanned Location process; the driver can sign on behalf of a customer when configured for this process and; the POD does not display "No Image Found".
}} {{ #vardefine: Cycle | 0 }}{{ #vardefine: SubCycle | 0 }}
{{TestPlan_CycleHeader
|Cycle={{ #vardefineecho: Cycle | {{ #expr: {{ #var: Cycle }} + 1 }} }}{{ #vardefine: SubCycle | {{ #var: Cycle }} }}
|Title=Admin (Configuration)
|Notes=
}} <!--INSERT TESTS HERE --> {{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Test that the new configuration flag can be set, saved and shown in the Job Group screen.
|Result=The new flag can be set. The values are as expected. The default value is as expected. The label and pop-up help are present and correct. The value is displayed correctly in the screen.
|Remarks=
|PassFail=
}}{{TestPlan_CycleFooter}} 

{{TestPlan_CycleHeader
|Cycle={{ #vardefineecho: Cycle | {{ #expr: {{ #var: Cycle }} + 1 }} }}{{ #vardefine: SubCycle | {{ #var: Cycle }} }}
|Title=Mobile Device
|Notes=Set up multiple job groups, two with Unmanned Location configured to "Driver Sign, Photo Required" and Optional Job Photo, and one as "Disabled" with Required Job Photo. Neither job group should required driver signature. Create 1 job of each job group on a load. Ensure both job groups are set to Optional 
}} <!--INSERT TESTS HERE --> {{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Start a job configured with Unmanned Location. Deliver all the items.
|Result=The Signature screen is shown, showing the '''Unmanned Location''' button.
|Remarks=
|PassFail=
}}{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Press the '''Unmanned Location''' button.
|Result=The alert shows as expected, asking for confirmation.
|Remarks=
|PassFail=
}}{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Press '''Cancel'''
|Result=The user is returned to the Signature screen.
|Remarks=
|PassFail=
}}{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Press the '''Unmanned Location''' button. Press '''Confirm'''.
|Result=The Driver Signature screen is shown. No "Unmanned Location" button is present.
|Remarks=
|PassFail=
}}{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Back-out of the driver signature screen.
|Result=The Collection/Delivery screen is shown.
|Remarks=
|PassFail=
}}{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Press '''Complete'''. Press the '''Unmanned Location''' button. Press '''Confirm'''. Enter a driver signature. Press '''Done'''. Confirm the signature.
|Result=The Job Photo screen is shown. The '''Skip''' button is not present.
|Remarks=
|PassFail=
}}{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Press '''OK'''
|Result=An error alert will be shown, that at least one photo must be taken.
|Remarks=
|PassFail=
}}{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Take a photo, enter a comment and complete the job. Start the next job with Unmanned Location enabled. Complete delivery of the items. Enter a signatory.
|Result=The '''Unmanned Location''' button is still present.
|Remarks=
|PassFail=
}}{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Enter a signature.
|Result=The '''Unmanned Location''' button is replaced with a '''Done''' button.
|Remarks=
|PassFail=
}}{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Press '''Clear'''
|Result=The '''Done''' button is replaced with a '''Unmanned Location''' button.
|Remarks=
|PassFail=
}}{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Enter a signature and press '''Done'''. Confirm.
|Result=The Job Photo screen is displayed. A '''Skip''' button is present.
|Remarks=
|PassFail=
}}{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Press '''Skip''' and confirm.
|Result=The job is completed and the job list is shown.
|Remarks=
|PassFail=
}}{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Start the job without Unmanned Location. Complete delivery of the items.
|Result=The signature screen is displayed. There is no '''Unmanned Location''' button.
|Remarks=
|PassFail=
}}{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Enter the signatory and signature and click the '''Done''' button. Confirm. 
|Result=The Job Photo screen is displayed. A '''Skip''' button is present.
|Remarks=
|PassFail=
}}{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Press '''Skip''' and confirm.
|Result=The job is completed and the job list is shown.
|Remarks=
|PassFail=
}}{{TestPlan_CycleFooter}} 

{{TestPlan_CycleHeader
|Cycle={{ #vardefineecho: Cycle | {{ #expr: {{ #var: Cycle }} + 1 }} }}{{ #vardefine: SubCycle | {{ #var: Cycle }} }}
|Title=Admin - POD Report
|Notes=These tests are based on the jobs completed in the previous cycle. Ensure the MPMS format is configured for each job group.
}} <!--INSERT TESTS HERE --> {{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Run the POD report for the first job completed.
|Result=There is no customer signature - this is blank. The driver signature is displayed.
|Remarks=
|PassFail=
}}{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Run the POD report for the second job completed.
|Result=There is no driver signature - this is blank. The customer signature is displayed.
|Remarks=
|PassFail=
}}{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Run the POD report for the third job completed.
|Result=There is no driver signature - this shows "Image Not Available". The customer signature is displayed.
|Remarks=
|PassFail=
}}{{TestPlan_CycleFooter}} 

<!-- MEDIA LANDSCAPE NO --> 
{{Doc_Appendix
|Appendix=B
|Estimate=Y
|Glossary=EPOD
|Ref1=[[REQ 339867 Marshalls Premier Mortars Solution Design]]
|RefV1=1.3
|RefDate1=25/05/2017
|EREQ=0
|EEST=0
|EFS=1.00
|ETS=0
|EDEV=5.0
|ESTT=0.50
|EIMP=0.25
|EPM=0.25
|REQ=0
|EST=0
|FS=1.00
|TS=0
|DEV=5.0
|ST=0.5
|IMP=0.25
|PM=0.25
|Client={{#var:Client}}
|Year={{#var:Year}}
|FSEST=Y
|FOC=N
|Rev1=Matt Turner
|Rev1Title=OBSL Account Manager
|Rev2=Simon Martin
|Rev2Title=Customer Representative
|Rev3=Debbie Linley
|Rev3Title=Customer Representative
}}</div> 
[[Category:{{#var:Client}} FS]]