FS 293863 CDL EPOD Modifications - Revision history

Milesl: /* Export Functionality */

2012-10-08T10:18:10Z

Export Functionality

← Older revision		Revision as of 12:18, 8 October 2012
Line 1,186:		Line 1,186:
	The CDL host system will require the ability to poll a webservice within ePOD either on demand or on a poller to retrieve current ePOD job information.		The CDL host system will require the ability to poll a webservice within ePOD either on demand or on a poller to retrieve current ePOD job information.
	A webservice already exists for exporting data by Job/Load ID and Date. Another two will be added allowing loads and jobs to be exported that have been changed in a date and time range.		A webservice already exists for exporting data by Job/Load ID and Date. Another two will be added allowing loads and jobs to be exported that have been changed in a date and time range.
	The services will require a From Date and Time and will accept a option To Date and Time, this will allow for poller services to simply retrieve all updates since the last poll using only the From Date and Time as well as queries to data in a particular date and time range.		The services will require a From Date and Time and will accept a option To Date and Time, this will allow for poller services to simply retrieve all updates since the last poll using only the From Date and Time as well as queries to data in a particular date and time range. The data returned as part of this export will conform to the current standards documented in the current version of the ePOD XSD’s.
	===Job Level===		===Job Level===
	The Job level webservice should be added that will accept the following structure:		The Job level webservice should be added that will accept the following structure:

Milesl: /* Export Functionality */

2012-10-08T10:06:04Z

Export Functionality

← Older revision		Revision as of 12:06, 8 October 2012
Line 1,186:		Line 1,186:
	The CDL host system will require the ability to poll a webservice within ePOD either on demand or on a poller to retrieve current ePOD job information.		The CDL host system will require the ability to poll a webservice within ePOD either on demand or on a poller to retrieve current ePOD job information.
	A webservice already exists for exporting data by Job/Load ID and Date. Another two will be added allowing loads and jobs to be exported that have been changed in a date and time range.		A webservice already exists for exporting data by Job/Load ID and Date. Another two will be added allowing loads and jobs to be exported that have been changed in a date and time range.
			The services will require a From Date and Time and will accept a option To Date and Time, this will allow for poller services to simply retrieve all updates since the last poll using only the From Date and Time as well as queries to data in a particular date and time range.
	===Job Level===		===Job Level===
	The Job level webservice should be added that will accept the following structure:		The Job level webservice should be added that will accept the following structure:
Line 1,222:		Line 1,222:
	ELSE		ELSE
	RETURN XML of all loads that have a last changed date and time between the DATE_TIME_FROM and DATE_TIME_TO fields		RETURN XML of all loads that have a last changed date and time between the DATE_TIME_FROM and DATE_TIME_TO fields



	<!-- NEW PAGE -->		<!-- NEW PAGE -->

Milesl: /* Export Functionality */

2012-10-08T10:01:56Z

Export Functionality

← Older revision		Revision as of 12:01, 8 October 2012
Line 1,191:		Line 1,191:

	<EPOD_EXPORT_JOB_CHANGED EPL_USER_ID="" EPL_USER_PASSWORD="" EPL_SITE_ID="">		<EPOD_EXPORT_JOB_CHANGED EPL_USER_ID="" EPL_USER_PASSWORD="" EPL_SITE_ID="">
	<DATE_TIME_FROM></DATE_TIME_FROM>		<DATE_TIME_FROM>2012-10-05T18:40:00</DATE_TIME_FROM>
	<DATE_TIME_TO></DATE_TIME_TO>		<DATE_TIME_TO>2012-10-05T18:50:00</DATE_TIME_TO>
	</EPOD_EXPORT_JOB_CHANGED>		</EPOD_EXPORT_JOB_CHANGED>

Line 1,209:		Line 1,209:

	<EPOD_EXPORT_LOAD_CHANGED EPL_USER_ID="" EPL_USER_PASSWORD="" EPL_SITE_ID="">		<EPOD_EXPORT_LOAD_CHANGED EPL_USER_ID="" EPL_USER_PASSWORD="" EPL_SITE_ID="">
	<DATE_TIME_FROM></DATE_TIME_FROM>		<DATE_TIME_FROM>2012-10-05T18:40:00</DATE_TIME_FROM>
	<DATE_TIME_TO></DATE_TIME_TO>		<DATE_TIME_TO>2012-10-05T18:50:00</DATE_TIME_TO>
	</EPOD_EXPORT_LOAD_CHANGED>		</EPOD_EXPORT_LOAD_CHANGED>

Milesl: /* Load Level */

2012-10-08T09:58:54Z

Load Level

← Older revision		Revision as of 11:58, 8 October 2012
Line 1,221:		Line 1,221:
	RETURN XML of all jobs that have a last changed date and time greater than the DATE_TIME_FROM field		RETURN XML of all jobs that have a last changed date and time greater than the DATE_TIME_FROM field
	ELSE		ELSE
	RETURN XML of all ~~jobs~~ that have a last changed date and time between the DATE_TIME_FROM and DATE_TIME_TO fields		RETURN XML of all loads that have a last changed date and time between the DATE_TIME_FROM and DATE_TIME_TO fields

	<!-- NEW PAGE -->		<!-- NEW PAGE -->

Milesl: /* Automatic email of POD/POC */

2012-10-08T09:44:39Z

Automatic email of POD/POC

@@ Line 1,182: / Line 1,182: @@
 *The process will take the rendered page and remove any code in between the new ''EMAIL SECTION'' comment tags
 *This rendered page will then be sent to the customer's email address through the standard email mechanism.
 <!-- NEW PAGE -->

Anw: v1.1 - Added customer-confirmed T&Cs; changed document format slightly

2012-06-28T13:32:33Z

v1.1 - Added customer-confirmed T&Cs; changed document format slightly

@@ Line 4: / Line 4: @@
 {{#vardefine:System|''CALIDUS'' ePOD}}
 {{#vardefine:Doc_Title|CDL EPOD Modifications}}
-{{#vardefine:Version|1.0}}
+{{#vardefine:Version|1.1}}
-{{#vardefine:Date|15th December 2011}}
+{{#vardefine:Date|28th June 2012}}
 {{#vardefine:Reference|293863}}
 </div>
@@ Line 108: / Line 108: @@
 *Office Instructions
 *Modifiable customer contact.
 == Scope  ==
@@ Line 151: / Line 157: @@
 The EPOD_SERVICE_PRODUCT_MASTER table will be modified to include a new Weight field. This will be a floating point field.
 <!-- NEW PAGE -->
@@ Line 1,042: / Line 1,053: @@
 This must be used on the POD/POC/Service reports created instead of the customer name.
 <!-- NEW PAGE -->
@@ Line 1,123: / Line 1,163: @@
 {{Note}} Multiple pages will be achieved when printing by using the CSS style '''page-break-before: always;''' set against the first element of the second page.
 <!-- NEW PAGE -->

Milesl: /* Appendix B: TEST PLAN */

2012-01-23T13:23:27Z

Appendix B: TEST PLAN

← Older revision		Revision as of 15:23, 23 January 2012
Line 1,154:		Line 1,154:
	\|Title={{#var:Doc_Title}}		\|Title={{#var:Doc_Title}}
	\|Log={{#var:Reference}}		\|Log={{#var:Reference}}
	\|Description=Full System Test for ~~Whiteline~~'s functionality		\|Description=Full System Test for CDL's functionality
	\|MenuAccess=N/a		\|MenuAccess=N/a
	\|Prerequisites=~~WhiteLines~~ Test Site configuration		\|Prerequisites=CDL Test Site configuration
	\|Objective=Fully test ~~Whiteline~~'s functionality		\|Objective=Fully test CDL's functionality
	}}		}}
	{{ #vardefine: Cycle \| 0 }}{{ #vardefine: SubCycle \| 0 }}		{{ #vardefine: Cycle \| 0 }}{{ #vardefine: SubCycle \| 0 }}
Line 1,166:		Line 1,166:
	}} <!--INSERT TESTS HERE --> {{TestPlan_Test		}} <!--INSERT TESTS HERE --> {{TestPlan_Test
	\|Test={{ #vardefineecho: SubCycle \| {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}		\|Test={{ #vardefineecho: SubCycle \| {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}
	\|Action=Create a ~~Delivery~~ with ~~Loose Products and include a customer reference~~ (~~Add~~ products ~~button within the Container.aspx page~~)		\|Action=Create a Ad Hoc collection with Office Instructions (collection with no containers or products)
	\|Result=~~Products appear as loose (not related to a container)~~		\|Result=
	\|Remarks=		\|Remarks=
	\|PassFail=		\|PassFail=
	}} {{TestPlan_Test		}}
			{{TestPlan_Test
	\|Test={{ #vardefineecho: SubCycle \| {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}		\|Test={{ #vardefineecho: SubCycle \| {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}
	\|Action=~~Create a Collection with Loose Products and include a customer reference~~ (~~Add products button within~~ the ~~Container~~.~~aspx page)~~		\|Action=Check the multi-part POC is produced correctly(printed as well), confirm the weights are calculated correctly.
	\|Result=~~Products appear as loose (not related to a container)~~		\|Result=
	\|Remarks=		\|Remarks=
	\|PassFail=		\|PassFail=
	}} {{TestPlan_Test		}}
			{{TestPlan_Test
	\|Test={{ #vardefineecho: SubCycle \| {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}		\|Test={{ #vardefineecho: SubCycle \| {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}
	\|Action=~~Check POD format is correctly formatted and data is shown correctly~~		\|Action=On job completion the POC should be emailed to the customers email address, automatically.
	\|Result=~~POD format will match documentation~~		\|Result=
	\|Remarks=		\|Remarks=
	\|PassFail=		\|PassFail=
	}} {{TestPlan_CycleFooter}}		}}{{TestPlan_CycleFooter}}

	{{TestPlan_CycleHeader		{{TestPlan_CycleHeader
Line 1,190:		Line 1,192:
	}} <!--INSERT TESTS HERE --> {{TestPlan_Test		}} <!--INSERT TESTS HERE --> {{TestPlan_Test
	\|Test={{ #vardefineecho: SubCycle \| {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}		\|Test={{ #vardefineecho: SubCycle \| {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}
	\|Action=Process a ~~delivery with Loose Products~~		\|Action=Process a ad hoc collection
	\|Result=~~No container~~ tab should ~~appear instead users will~~ be ~~directed straight to products (only if there are no other containers)~~		\|Result=Only Ad Hoc collection tab and instruction tabs should be shown.
	\|Remarks=		\|Remarks=
	\|PassFail=		\|PassFail=
	}} {{TestPlan_Test		}} {{TestPlan_Test
	\|Test={{ #vardefineecho: SubCycle \| {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}		\|Test={{ #vardefineecho: SubCycle \| {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}
	\|Action=Process a collection ~~with Loose Products~~		\|Action=Process a ad hoc collection using products configured in the service product master
	\|Result=~~No container tab~~ should ~~appear instead users will~~ be ~~directed straight to products (only if there are no other containers)~~		\|Result=Products should be added in the standard approach
	\|Remarks=		\|Remarks=
	\|PassFail=		\|PassFail=
	}} {{TestPlan_Test		}} {{TestPlan_Test
	\|Test={{ #vardefineecho: SubCycle \| {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}		\|Test={{ #vardefineecho: SubCycle \| {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}
	\|Action=Check ~~Naivation~~ is functioning. Start Co-Pilot in one job, check that the destination is sent to Co-Pilot. Minimise Co-Pilot and start it for another job. Minimise Co-Pilot and complete the Job. Exit the App and check that Co-Pilot is closed.		\|Action=Check driver signature is prompted
	\|Result=~~Co-Pilot~~ should ~~be started, prompted with locations and closed by~~ the ~~ePOD Client.~~		\|Result=Driver should sign as well as the customer
	\|Remarks=		\|Remarks=
	\|PassFail=		\|PassFail=
Line 1,209:		Line 1,211:
	{{TestPlan_Test		{{TestPlan_Test
	\|Test={{ #vardefineecho: SubCycle \| {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}		\|Test={{ #vardefineecho: SubCycle \| {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}
	\|Action=~~Check that~~ the ~~Payment recieved on delivery functions. Check the payment on delivery check box, at the end of product delivery/collection.~~		\|Action=Change the customers name when signing
	\|Result=This should ~~interface~~ back to the admin system and be shown against the job,		\|Result=This should process back to the admin system and be shown against the job.
	\|Remarks=		\|Remarks=
	\|PassFail=		\|PassFail=
	}}		}}
	~~{{TestPlan_Test~~		{{TestPlan_CycleFooter}}
	~~\|Test={{ #vardefineecho: SubCycle \| {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}~~
	~~\|Action=Check that the context menu for products functions. Long hold on a product with produce a context menu. Check the data on here is correct.~~
	~~\|Result=The context menu should display the following:~~
	*EPL_PRODUCT_CODE
	*EPL_DESCRIPTION
	*EPL_ITEM_TYPE
	*EPL_CUST_REF
	*EPL_PRODUCT_QTY_PLANNED

	~~\|Remarks=~~
	~~\|PassFail=~~
	}} {{TestPlan_CycleFooter}}

	<!-- MEDIA LANDSCAPE NO -->		<!-- MEDIA LANDSCAPE NO -->

Milesl at 12:55, 23 January 2012

2012-01-23T12:55:30Z

@@ Line 1,139: / Line 1,139: @@
 *This rendered page will then be sent to the customer's email address through the standard email mechanism.
 <!-- NEW PAGE -->
 = Appendix A: POC Document Formats  =
@@ Line 1,147: / Line 1,147: @@
 [[File:293863-POC-2.JPG|600px]]
-<!-- NEW PAGE -->
+<!-- MEDIA LANDSCAPE YES -->
 {{Doc_Appendix
-|Appendix=B
+|Appendix=C
 |Estimate=N
 |Glossary=EPOD

Anw: v1.0 - Issued to client

2011-12-15T11:48:56Z

v1.0 - Issued to client

← Older revision		Revision as of 13:48, 15 December 2011
Line 4:		Line 4:
	{{#vardefine:System\|''CALIDUS'' ePOD}}		{{#vardefine:System\|''CALIDUS'' ePOD}}
	{{#vardefine:Doc_Title\|CDL EPOD Modifications}}		{{#vardefine:Doc_Title\|CDL EPOD Modifications}}
	{{#vardefine:Version\|0.2}}		{{#vardefine:Version\|1.0}}
	{{#vardefine:Date\|~~1st~~ December 2011}}		{{#vardefine:Date\|15th December 2011}}
	{{#vardefine:Reference\|293863}}		{{#vardefine:Reference\|293863}}
	</div>		</div>
Line 1,150:		Line 1,150:
	{{Doc_Appendix		{{Doc_Appendix
	\|Appendix=B		\|Appendix=B
	\|Estimate=Y		\|Estimate=N
	\|Glossary=EPOD		\|Glossary=EPOD
	\|Ref1=[[FS 294229 Whiteline EPOD Modifications]]		\|Ref1=[[FS 294229 Whiteline EPOD Modifications]]

Anw: /* Ad Hoc Collection Process */

2011-12-15T11:47:10Z

Ad Hoc Collection Process

← Older revision		Revision as of 13:47, 15 December 2011
Line 1,019:		Line 1,019:
	==Ad Hoc Collection Process==		==Ad Hoc Collection Process==

	The Ad Hoc collection process will allow users of the PDA to specify items collected, at point of collection. This will appears as a ~~seperate~~ tab on the PDA within the Collections menu. Users will be able to select items that currently exists in the EPOD_SERVICE_PRODUCT_MASTER, from a drop down list and add or remove them from the collection. These products will be added to the Loose Products container 00000000.		The Ad Hoc collection process will allow users of the PDA to specify items collected, at point of collection. This will appears as a separate tab on the PDA within the Collections menu. Users will be able to select items that currently exists in the EPOD_SERVICE_PRODUCT_MASTER, from a drop down list and add or remove them from the collection. These products will be added to the Loose Products container 00000000.

	Once completed the server will then create this container if it does not exist and products.		Once completed the server will then create this container if it does not exist and products.

	This will be configurable against the SITE and the JOB GROUP. If configured as off the Ad Hoc tab within the ~~collecitions~~ menu will be disabled. If this is enabled the tab will be displayed allowing a combination of pre-defined containers and products as well as Ad Hoc additions. The functionality provided by Containers without products means that in the scenario that there are no products/containers pre-defined the Containers and Products tabs will be disabled. If the Loose Product container is pre-defined, the Ad Hoc products will be placed onto this container.		This will be configurable against the SITE and the JOB GROUP. If configured as off the Ad Hoc tab within the collections menu will be disabled. If this is enabled the tab will be displayed allowing a combination of pre-defined containers and products as well as Ad Hoc additions. The functionality provided by Containers without products means that in the scenario that there are no products/containers pre-defined the Containers and Products tabs will be disabled. If the Loose Product container is pre-defined, the Ad Hoc products will be placed onto this container.
	<!-- NEW PAGE -->		<!-- NEW PAGE -->

	==Multiple Signatures at Delivery/Collection==		==Multiple Signatures at Delivery/Collection==