FS 314964 Palletforce Interface changes - Revision history

Rxe at 13:03, 19 March 2014

2014-03-19T13:03:42Z

← Older revision		Revision as of 15:03, 19 March 2014
Line 110:		Line 110:

	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 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 following is added for clarification purposes following testing:
			The Claused Container pop-up screen will only become visible if the site level flag is set to 'Y'.
			The decision to prompt for the Reason Code will then be dependant on the Job Group level flag.

	The Claused Container pop-up screen will be altered to check for the EPL_CLAUSE_DELIVERY of PDA_JOB_GROUPS flag.		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		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'.		of Reason Type 'CLA'.

Rxe: /* Palletforce File Export Changes */

2014-02-13T14:36:56Z

Palletforce File Export Changes

← Older revision		Revision as of 16:36, 13 February 2014
Line 94:		Line 94:
	* 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.		* 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.		Note that the layout is to remain as a comma-separated file so the new fields will need to be separated with extra commas. All fields will be checked for the existence of commas entered as part of the text. If they exist, they will be replaced with space characters before the message is sent.

			Note that cancelled containers will not be sent as part of the process. This may be expected to change in future. In this scenario further changes may be required.

	== Message Process Changes ==		== Message Process Changes ==

Rxe at 13:55, 12 February 2014

2014-02-12T13:55:43Z

← Older revision		Revision as of 15:55, 12 February 2014
Line 190:		Line 190:
	{{Doc_Appendix		{{Doc_Appendix
	\|Appendix=B		\|Appendix=B
	\|Estimate=N		\|Estimate=Y
	\|Glossary=EPOD		\|Glossary=EPOD
	\|Ref1=		\|Ref1=
Line 197:		Line 197:
	\|REQ=0		\|REQ=0
	\|EST=0		\|EST=0
	\|FS=0		\|FS=1.5
	\|TS=0		\|TS=0
	\|DEV=0		\|DEV=5.0
	\|ST=0		\|ST=1.0
	\|IMP=0		\|IMP=0.5
	\|Client={{#var:Client}}		\|Client={{#var:Client}}
	\|Year={{#var:Year}}		\|Year={{#var:Year}}

Rxe at 13:53, 12 February 2014

2014-02-12T13:53:21Z

← Older revision		Revision as of 15:53, 12 February 2014
Line 84:		Line 84:
	In the Container Details popup box, the user is currently able to enter free text within the Claused Delivery field.		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,		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.		then a drop-down list will appear labelled as 'Claused Reason'. The user will be expected to choose a reason code from the list. The list will be made a required field.

	== Palletforce File Export Changes ==		== Palletforce File Export Changes ==
Line 92:		Line 92:

	* Delivery Status Code - to be set as EPL_REASON_CODE of EPOD_CONTAINER if populated. If not then set as 'POD'.		* 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 only completed jobs~~		* 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.		Note that the layout is to remain as a comma-separated file so the new fields will need to be separated with extra commas.
Line 112:		Line 112:
	If this is set to '2', then the program will check for the existence of PDA_REASON_CODES for the Job Group in question		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'.		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.		If records exist then a new drop-down list will be displayed Labelled as 'Claused Reason'. The user will be expected to choose the reason for marking the delivery as claused. The list will be a required field.

Rxe at 13:50, 12 February 2014

2014-02-12T13:50:40Z

← Older revision		Revision as of 15:50, 12 February 2014
Line 68:		Line 68:
	== Admin Changes ==		== 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.		The Reason Code Maintenance screen (Reason_code.aspx) will be altered to include a new 'Type' of 'Claused' in the 'Type' drop-down list.
	Note ~~that~~ the ~~Text~~ will be displayed as 'Claused' but the value on the database will be ~~stored as~~ 'CLA'.		Note the text in the list will be displayed as 'Claused' but the value stored in the database will be 'CLA'.
	Reason codes of this type will be used to indicate a complete delivery with exceptions, e.g. 'PODD' or 'PODC'.		Reason codes of this type will be used to indicate a complete delivery with exceptions, e.g. 'PODD' or 'PODC'.

Line 84:		Line 84:
	In the Container Details popup box, the user is currently able to enter free text within the Claused Delivery field.		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,		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 ~~expected~~ to choose a reason code from the list. The list will be made a required field.		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 ==		== Palletforce File Export Changes ==
Line 91:		Line 91:
	In addition, two extra fields will be added to the current layout for the outbound Palletforce file:		In addition, 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 ~~and the status of the container record is 'C'~~. If not then set as 'POD'.		* 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.		* 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 only completed jobs
	~~The EPL_CUST_COMMENTS field will be checked for comma characters. If any are found, they will be replaced with space characters in the outbound file to ensure the integrity of the csv produced.~~
	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.		Note that the layout is to remain as a comma-separated file so the new fields will need to be separated with extra commas.
Line 101:		Line 99:
	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.		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 ==		== Pda Changes ==

	Table PDA_JOB_GROUPS requires the following modifications:		Table PDA_JOB_GROUPS requires the following modifications:
Line 114:		Line 112:
	If this is set to '2', then the program will check for the existence of PDA_REASON_CODES for the Job Group in question		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'.		of Reason Type 'CLA'.
	If records exist then a new drop-down list will be displayed Labelled as 'Claused Reason'~~. The~~ user ~~will be expected~~ to choose the reason for marking the delivery as claused. The list will be made a required field.		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.


	<!-- MEDIA LANDSCAPE YES -->		<!-- MEDIA LANDSCAPE YES -->
Line 191:		Line 190:
	{{Doc_Appendix		{{Doc_Appendix
	\|Appendix=B		\|Appendix=B
	\|Estimate=Y		\|Estimate=N
	\|Glossary=EPOD		\|Glossary=EPOD
	\|Ref1=		\|Ref1=
Line 198:		Line 197:
	\|REQ=0		\|REQ=0
	\|EST=0		\|EST=0
	\|FS=~~1.5~~		\|FS=0
	\|TS=0		\|TS=0
	\|DEV=5		\|DEV=0
	\|ST=1.0		\|ST=0
	\|IMP=0.5		\|IMP=0
	\|Client={{#var:Client}}		\|Client={{#var:Client}}
	\|Year={{#var:Year}}		\|Year={{#var:Year}}

Rxe at 13:31, 12 February 2014

2014-02-12T13:31:42Z

← Older revision		Revision as of 15:31, 12 February 2014
Line 84:		Line 84:
	In the Container Details popup box, the user is currently able to enter free text within the Claused Delivery field.		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,		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.		then a drop-down list will appear labelled as 'Claused Reason'. The user will be expected to choose a reason code from the list. The list will be made a required field.

	== Palletforce File Export Changes ==		== Palletforce File Export Changes ==
Line 114:		Line 114:
	If this is set to '2', then the program will check for the existence of PDA_REASON_CODES for the Job Group in question		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'.		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.		If records exist then a new drop-down list will be displayed Labelled as 'Claused Reason'. The user will be expected to choose the reason for marking the delivery as claused. The list will be made a required field.


	<!-- MEDIA LANDSCAPE YES -->		<!-- MEDIA LANDSCAPE YES -->

Rxe at 13:20, 12 February 2014

2014-02-12T13:20:10Z

← Older revision		Revision as of 15:20, 12 February 2014
Line 192:		Line 192:
	{{Doc_Appendix		{{Doc_Appendix
	\|Appendix=B		\|Appendix=B
	\|Estimate=N		\|Estimate=Y
	\|Glossary=EPOD		\|Glossary=EPOD
	\|Ref1=		\|Ref1=

Rxe at 13:17, 12 February 2014

2014-02-12T13:17:53Z

← Older revision		Revision as of 15:17, 12 February 2014
Line 68:		Line 68:
	== Admin Changes ==		== 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.		The Reason Code Maintenance screen (Reason_code.aspx) will be altered to include a new 'Type' of 'Claused' in the 'Type' drop-down list.
			Note that the Text will be displayed as 'Claused' but the value on the database will be stored as 'CLA'.
	Reason codes of this type will be used to indicate a complete delivery with exceptions, e.g. 'PODD' or 'PODC'.		Reason codes of this type will be used to indicate a complete delivery with exceptions, e.g. 'PODD' or 'PODC'.

Line 90:		Line 91:
	In addition, two extra fields will be added to the current layout for the outbound Palletforce file:		In addition, 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'.		* Delivery Status Code - to be set as EPL_REASON_CODE of EPOD_CONTAINER if populated and the status of the container record is 'C'. 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.		* 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.
			The EPL_CUST_COMMENTS field will be checked for comma characters. If any are found, they will be replaced with space characters in the outbound file to ensure the integrity of the csv produced.
			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.		Note that the layout is to remain as a comma-separated file so the new fields will need to be separated with extra commas.
Line 98:		Line 101:
	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.		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 ==		== PDA Changes ==

	Table PDA_JOB_GROUPS requires the following modifications:		Table PDA_JOB_GROUPS requires the following modifications:
Line 196:		Line 199:
	\|REQ=0		\|REQ=0
	\|EST=0		\|EST=0
	\|FS=0		\|FS=1.5
	\|TS=0		\|TS=0
	\|DEV=0		\|DEV=5
	\|ST=0		\|ST=1.0
	\|IMP=0		\|IMP=0.5
	\|Client={{#var:Client}}		\|Client={{#var:Client}}
	\|Year={{#var:Year}}		\|Year={{#var:Year}}

Rxe: /* Scope */

2014-02-12T09:46:26Z

Scope

← Older revision		Revision as of 11:46, 12 February 2014
Line 34:		Line 34:
	== Scope ==		== Scope ==
	* These changes will be made in the latest version of the {{#var:System}} system.		* These changes will be made in the latest version of the {{#var:System}} system.
			* These changes will only be made to the Android version of the PDA client.

			<!-- NEW PAGE -->

	~~<!-- NEW PAGE -->~~
	= Set-up =		= Set-up =

Rxe at 17:48, 11 February 2014

2014-02-11T17:48:45Z

← Older revision		Revision as of 19:48, 11 February 2014
Line 183:		Line 183:
	\|Result=Check the Claused Reason Code and Reason Code description are included in the output file produced.		\|Result=Check the Claused Reason Code and Reason Code description are included in the output file produced.
	\|Remarks= \|PassFail= }} {{TestPlan_CycleFooter}}		\|Remarks= \|PassFail= }} {{TestPlan_CycleFooter}}
	~~{{TestPlan_Header~~
	~~\|Title={{#var:Doc_Title}}~~
	~~\|Log={{#var:Reference}}~~
	~~\|Description=To test the production of the outbound Palletforce export process to ensure the new Claused delivery fields are included in {{#var:System}}~~
	~~\|MenuAccess=Job Group Maintenance, Reason Code Maintenance~~
	~~\|Prerequisites=Ensure that Palletforce job groups are defined against the required sites~~
	~~\|Objective=To 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.~~
	}}
	<!-- MEDIA LANDSCAPE NO -->		<!-- MEDIA LANDSCAPE NO -->
	{{Doc_Appendix		{{Doc_Appendix