User-Defined Fields - Revision history

Anw: Categorisation

2025-06-20T10:06:33Z

Categorisation

← Older revision		Revision as of 12:06, 20 June 2025
Line 61:		Line 61:
	In these cases, you can add specific buttons to these forms, so that the application can validate the data entry. In this case, the system can display alerts and confirmations, allowing the system to be widely configured.		In these cases, you can add specific buttons to these forms, so that the application can validate the data entry. In this case, the system can display alerts and confirmations, allowing the system to be widely configured.

	<gallery widths=300px heights=450px perrow=3>		<gallery widths="300px" heights="450px" perrow="3">
	File:ePOD_Job_Prework1.PNG\|''Pre-work - location barcode''		File:ePOD_Job_Prework1.PNG\|''Pre-work - location barcode''
	File:ePOD_Job_Prework2.PNG\|''Pre-work - Validation''		File:ePOD_Job_Prework2.PNG\|''Pre-work - Validation''
Line 88:		Line 88:


	<gallery widths=300px heights=450px perrow=3>		<gallery widths="300px" heights="450px" perrow="3">
	File:EPOD_Collection1.PNG\|''Collection Capturing Pallets Unloaded''		File:EPOD_Collection1.PNG\|''Collection Capturing Pallets Unloaded''
	File:EPOD_Delivery1.PNG\|''Delivery Capturing Pallets Unloaded''		File:EPOD_Delivery1.PNG\|''Delivery Capturing Pallets Unloaded''
Line 170:		Line 170:


	<gallery widths=300px heights=450px perrow=3>		<gallery widths="300px" heights="450px" perrow="3">
	File:ePOD_Job_PrejobSign1.PNG\|''Pre-job Signature''		File:ePOD_Job_PrejobSign1.PNG\|''Pre-job Signature''
	File:ePOD_Signature1.PNG\|''Customer Signature''		File:ePOD_Signature1.PNG\|''Customer Signature''
Line 210:		Line 210:


	<gallery widths=300px heights=450px perrow=3>		<gallery widths="300px" heights="450px" perrow="3">
	File:EPOD_Load_Metrics.PNG\|''Start Metrics''		File:EPOD_Load_Metrics.PNG\|''Start Metrics''
	</gallery>		</gallery>
Line 270:		Line 270:
	The most common use of this is to capture additional details on inspection, installation, removal or service of a tyre, such as tyre pressure, tread depth, etc.		The most common use of this is to capture additional details on inspection, installation, removal or service of a tyre, such as tyre pressure, tread depth, etc.

	<gallery widths=300px heights=450px perrow=3>		<gallery widths="300px" heights="450px" perrow="3">
	File:EPOD_Service_Tyres_Inspect2.png\|''Inspection details''		File:EPOD_Service_Tyres_Inspect2.png\|''Inspection details''
	File:EPOD_Service_Tyres_Remove.png\|''Removal details''		File:EPOD_Service_Tyres_Remove.png\|''Removal details''
Line 282:		Line 282:
	This could be used to capture general additional information about the service item, for example, in Fleet Management, to capture torque details, services supplied against the vehicle in general, etc.		This could be used to capture general additional information about the service item, for example, in Fleet Management, to capture torque details, services supplied against the vehicle in general, etc.

	<gallery widths=300px heights=450px perrow=3>		<gallery widths="300px" heights="450px" perrow="3">
	File:EPOD_Service_Tyres_Completion2.png\|''Completion''		File:EPOD_Service_Tyres_Completion2.png\|''Completion''
	</gallery>		</gallery>
Line 316:		Line 316:


	<gallery widths=300px heights=450px perrow=3>		<gallery widths="300px" heights="450px" perrow="3">
	File:EPOD_VehicleChecks.PNG\|''Vehicle Checks''		File:EPOD_VehicleChecks.PNG\|''Vehicle Checks''
	</gallery>		</gallery>
Line 398:		Line 398:


	<gallery widths=300px heights=450px perrow=3>		<gallery widths="300px" heights="450px" perrow="3">
	File:EPOD_Collection_ContainerUDF.PNG\|''Container UDF''		File:EPOD_Collection_ContainerUDF.PNG\|''Container UDF''
	File:EPOD_Collection_ProductUDF.PNG\|''Product UDF''		File:EPOD_Collection_ProductUDF.PNG\|''Product UDF''
Line 420:		Line 420:


	<gallery widths=300px heights=450px perrow=3>		<gallery widths="300px" heights="450px" perrow="3">
	File:EPOD_Service_Tyres_Tyre_Swap1.png\|''Tyre Swap - Twinning service''		File:EPOD_Service_Tyres_Tyre_Swap1.png\|''Tyre Swap - Twinning service''
	File:EPOD_Service_Tyres_Tyre_Swap2.png\|''Tyre Swap - Swap button''		File:EPOD_Service_Tyres_Tyre_Swap2.png\|''Tyre Swap - Swap button''
Line 428:		Line 428:

	[[Category:UG 291097 EPOD Advanced Guide\|250]]		[[Category:UG 291097 EPOD Advanced Guide\|250]]
			[[Category:FAQ]]

Anw: Added details of Tyre-based systems. Minor corrections.

2024-08-07T14:49:37Z

Added details of Tyre-based systems. Minor corrections.

← Older revision		Revision as of 16:49, 7 August 2024
Line 223:		Line 223:
	* Pre-work - optional information required to be entered before the item is worked on.		* Pre-work - optional information required to be entered before the item is worked on.
	* Activities - the activities undertaken.		* Activities - the activities undertaken.
	* Installed Products.		* Products
			* Installed/Returned Products.
			* For Tyre service jobs, Installed or Removed tyres and services supplied actions.
	* Returned Products.		* Returned Products.
	* MC Refs - IDs or references of the item being worked on.		* MC Refs - IDs or references of the item being worked on.
Line 236:		Line 238:
	* Diagnosis.		* Diagnosis.
	* Post-work.		* Post-work.
			* Tyre Service jobs
			* Service Product
			* Service Activity

	You can configure these against:		You can configure these against:
Line 241:		Line 246:
	* the job group.		* the job group.
	* the product group - the type of item being worked on.		* the product group - the type of item being worked on.
			* Additionally Service Activity can be configured to Service Type level, for Tyre Services.


Line 261:		Line 267:


	Diagnosis UDF is useful for straight data capture in addition to the standard information. This has been used in the past solely for additional notes entry but could be used to capture any information required for the customer's process.		When using a Fleet Management (tyre-based) service job, activities and products can have UDF attached to them, which must be completed or the service product or activity is considered incomplete.
			The most common use of this is to capture additional details on inspection, installation, removal or service of a tyre, such as tyre pressure, tread depth, etc.

			<gallery widths=300px heights=450px perrow=3>
			File:EPOD_Service_Tyres_Inspect2.png\|''Inspection details''
			File:EPOD_Service_Tyres_Remove.png\|''Removal details''
			File:EPOD_Service_Tyres_Install.png\|''Installation details''
			File:EPOD_Service_Tyres_Services.png\|''Services Supplied details''
			</gallery>


			Diagnosis (or Service Completion) UDF is useful for straight data capture in addition to the standard information. This has been used in the past solely for additional notes entry but could be used to capture any information required for the customer's process.

			This could be used to capture general additional information about the service item, for example, in Fleet Management, to capture torque details, services supplied against the vehicle in general, etc.

			<gallery widths=300px heights=450px perrow=3>
			File:EPOD_Service_Tyres_Completion2.png\|''Completion''
			</gallery>


	Diagnosis UDF is added to the Diagnosis tab for entry, beneath any standard fields configured for the style of the system.		Diagnosis UDF is added to the Diagnosis tab for entry, beneath any standard fields configured for the style of the system.


	More details on the operation of this process can be found here: [[PDA Service]].		More details on the operation of this process can be found here: [[PDA Service]] and here: [[PDA Service Tyres]].


Line 335:		Line 359:
	* displaying additional instructions to the driver.		* displaying additional instructions to the driver.

			<!--
	<gallery widths=300px heights=450px perrow=3>		<gallery widths=300px heights=450px perrow=3>
	File:EPOD_CancellationUDF1.PNG\|''Cancellation UDF''		File:EPOD_CancellationUDF1.PNG\|''Cancellation UDF''
	</gallery>		</gallery>
			-->

	More details on the operation of this process can be found here: [[PDA Exception]].		More details on the operation of this process can be found here: [[PDA Exception]].
Line 386:		Line 410:
	Sub-forms are in a category by themselves. They aren't linked to any particular process, but can be used on any other UDF form, by adding a button linked to this form.		Sub-forms are in a category by themselves. They aren't linked to any particular process, but can be used on any other UDF form, by adding a button linked to this form.

	Its use cases are predominantly anywhere where there is a lot of data to be entered and only a small amount of space - sub-forms always display on the device in a full screen, triggered when the driver presses the button that links to this sub-form.		Its use cases are predominantly anywhere where there is a lot of data to be entered and only a small amount of space - sub-forms always display on the device in a full screen, triggered when the driver presses the button that links to this sub-form. As buttons can be made conditional based on another field (i.e. check this box, a button appears to enter more details through a sub-form), this is also useful to save clutter on complicated forms.


	Use cases:		Use cases:
	* Optional or required form entry at any stage.		* Optional or required form entry at any stage.
	* Specifically, Gift Aid Declaration at customer signature.		* Specifically,
			* Gift Aid Declaration at customer signature.
			* Tyre Swap information when installing or servicing a Tyre (tyre services only)


			<gallery widths=300px heights=450px perrow=3>
			File:EPOD_Service_Tyres_Tyre_Swap1.png\|''Tyre Swap - Twinning service''
			File:EPOD_Service_Tyres_Tyre_Swap2.png\|''Tyre Swap - Swap button''
			</gallery>



	[[Category:UG 291097 EPOD Advanced Guide\|250]]		[[Category:UG 291097 EPOD Advanced Guide\|250]]

Anw: Minor correction

2023-11-08T11:42:58Z

Minor correction

← Older revision		Revision as of 13:42, 8 November 2023
Line 15:		Line 15:


	You can use ~~rach~~ of these processes to resolve certain use cases - this guide will highlight some of the requirements UDF the application has been used to fulfill, as well as expanding on how to enter and maintain UDF in general.		You can use each of these processes to resolve certain use cases - this guide will highlight some of the requirements UDF the application has been used to fulfill, as well as expanding on how to enter and maintain UDF in general.

	UDF is an import part of configuring ''CALIDUS'' ePOD to capture the data required at the right points. In most cases, you can use UDF instead of software changes to achieve the processes your customers require.		UDF is an import part of configuring ''CALIDUS'' ePOD to capture the data required at the right points. In most cases, you can use UDF instead of software changes to achieve the processes your customers require.

Anw: Passive voice

2019-04-09T07:17:36Z

Passive voice

Show changes

Anw: Grammar corrections

2019-01-23T15:52:57Z

Grammar corrections

← Older revision		Revision as of 17:52, 23 January 2019
Line 15:		Line 15:


	Each of these processes can be used to resolve certain use cases, and this guide will highlight some of the requirements UDF has been used to ~~fulfil~~, as well as expanding on how to enter and maintain UDF in general.		Each of these processes can be used to resolve certain use cases, and this guide will highlight some of the requirements UDF has been used to fulfill, as well as expanding on how to enter and maintain UDF in general.

	UDF is an import part of configuring ''CALIDUS'' ePOD to capture the data required at the right points. In most cases, UDF can be used instead of software changes to achieve the processes required by a customer.		UDF is an import part of configuring ''CALIDUS'' ePOD to capture the data required at the right points. In most cases, UDF can be used instead of software changes to achieve the processes required by a customer.
Line 96:		Line 96:

	== Terms And Conditions ==		== Terms And Conditions ==
	''CALIDUS'' ePOD features an ability to define Terms and Conditions (T&Cs) and up to 3 ~~check boxes~~ at the point of customer signature on any job of a particular job group. For many customers, this is perfectly reasonable. Using UDF however, T&Cs can be greatly expanded and as much data can be captured as is desired.		''CALIDUS'' ePOD features an ability to define Terms and Conditions (T&Cs) and up to 3 checkboxes at the point of customer signature on any job of a particular job group. For many customers, this is perfectly reasonable. Using UDF however, T&Cs can be greatly expanded and as much data can be captured as is desired.


Line 138:		Line 138:
	In most cases, Terms and Conditions are simply text to be displayed - in this case, label fields can be used to enter the paragraphs of the terms.		In most cases, Terms and Conditions are simply text to be displayed - in this case, label fields can be used to enter the paragraphs of the terms.

	In the case where some data entry is required, standard T&Cs allows for up to 3 ~~check boxes~~ to be defined. No other types of fields (for example, drop-down lists, text entry, etc) can be specified. UDF allows all this and more:		In the case where some data entry is required, standard T&Cs allows for up to 3 checkboxes to be defined. No other types of fields (for example, drop-down lists, text entry, etc) can be specified. UDF allows all this and more:
	* All types of fields may be defined, for example, Text or Numeric entry, check boxes, drop-down lists and even Photos can be added.		* All types of fields may be defined, for example, Text or Numeric entry, check boxes, drop-down lists and even Photos can be added.
	* Validation can be enabled, to ensure the signatory isn't entering invalid data.		* Validation can be enabled to ensure the signatory isn't entering invalid data.
	* Values can be pre-set in the fields, for example, pre-checking a box for the signatory.		* Values can be pre-set in the fields, for example, pre-checking a box for the signatory.
	* Fields can be required to be entered, for example, "Check this box to agree to the T&Cs above" - not checking the box means that the signature cannot be completed.		* Fields can be required to be entered, for example, "Check this box to agree to the T&Cs above" - not checking the box means that the signature cannot be completed.
Line 160:		Line 160:
	Use cases for this functionality are:		Use cases for this functionality are:
	* Site Waiver documentation		* Site Waiver documentation
	* Gatehouse data capture for example, Weighbridge		* Gatehouse data capture, for example, Weighbridge
	* Capturing demurrage time		* Capturing demurrage time

Line 216:		Line 216:
	* Info - the key information about the item being worked on.		* Info - the key information about the item being worked on.
	* Pre-work - optional information required to be entered before the item is worked on.		* Pre-work - optional information required to be entered before the item is worked on.
	* Activities - activities undertaken.		* Activities - the activities undertaken.
	* Installed Products.		* Installed Products.
	* Returned Products.		* Returned Products.
Line 255:		Line 255:


	Diagnosis UDF is useful for straight data capture in addition to the standard information. This has been used in the past solely for additional notes entry, but could be used to capture any information required for the customer's process.		Diagnosis UDF is useful for straight data capture in addition to the standard information. This has been used in the past solely for additional notes entry but could be used to capture any information required for the customer's process.

	Diagnosis UDF is added to the Diagnosis tab for entry, under any standard fields configured for the style of the system.		Diagnosis UDF is added to the Diagnosis tab for entry, under any standard fields configured for the style of the system.
Line 264:		Line 264:

	== Vehicle Defect Checks ==		== Vehicle Defect Checks ==
	Vehicle Defect Checks are now configured exclusively through UDF. In earlier versions of the product, Vehicle Checks were configured using a bespoke screen, but worked as a (feature-limited) sub-set of UDF. With the switch to full UDF, vehicle defect checks now benefit from the new features of UDF, like multiple photos at any stage.		Vehicle Defect Checks are now configured exclusively through UDF. In earlier versions of the product, Vehicle Checks were configured using a bespoke screen but worked as a (feature-limited) sub-set of UDF. With the switch to full UDF, vehicle defect checks now benefit from the new features of UDF, like multiple photos at any stage.

	Vehicle Defect Checks UDF differs slightly to normal UDF, in that it may be configured with the following additional parameters on the form:		Vehicle Defect Checks UDF differs slightly to normal UDF, in that it may be configured with the following additional parameters on the form:
Line 363:		Line 363:

	Use cases:		Use cases:
	* Vehicle defect check against vehicles collected by carrier.		* Vehicle defect check against vehicles collected by the carrier.
	* Cone test against Mortar products when delivered.		* Cone test against Mortar products when delivered.
	* Lot/Batch capture against received item.		* Lot/Batch capture against the received item.

Anw: Updated based on version 4.0.02.29

2018-11-29T13:39:07Z

Updated based on version 4.0.02.29

← Older revision		Revision as of 15:39, 29 November 2018
Line 375:		Line 375:

	More details on the operation of this process can be found here: [[PDA Collection]] and [[PDA Delivery]].		More details on the operation of this process can be found here: [[PDA Collection]] and [[PDA Delivery]].


			== Sub-Forms ==
			Sub-forms are in a category by themselves. They aren't linked to any particular process, but can be used on any other UDF form, by adding a button linked to this form.

			Its use cases are predominantly anywhere where there is a lot of data to be entered and only a small amount of space - sub-forms always display on the device in a full screen, triggered when the button is pressed.


			Use cases:
			* Optional or required form entry at any stage
			* Specifically, Gift Aid Declaration at Customer Signature


	[[Category:UG 291097 EPOD Advanced Guide\|250]]		[[Category:UG 291097 EPOD Advanced Guide\|250]]

Anw: Included use case for photos before or during job, before completion

2018-03-27T16:56:01Z

Included use case for photos before or during job, before completion

← Older revision		Revision as of 18:56, 27 March 2018
Line 71:		Line 71:

	Use cases for additional job details:		Use cases for additional job details:
	* Capturing ad-hoc items collected/delivered		* Capturing ad-hoc items collected/delivered. For example, a list of pallet types that may be collected at the location for return, with a quantity returned for each type.
	* Weighbridge Weight and Number		* Weighbridge Weight and Number
	* ~~Arrival~~ Photographs		* Photographs taken before or during completion of the job. Furthermore, this process can be enhanced by making photos required (where at least one photograph must be taken) or having a required check-box associated with the job details, for example with the text "Have all required photos been taken?"


	~~This~~ requirement to enter the additional details can be based on whether the job is completed without any issues. So, in the case where some items could not be collected or delivered, the UDF must be entered, but if the job is completed fully, it need not be. ~~The~~ is primarily used when entering Failed Delivery or Collection checks or feedback.		The requirement to enter the additional details can be based on whether the job is completed without any issues. So, in the case where some items could not be collected or delivered, the UDF must be entered, but if the job is completed fully, it need not be. This is primarily used when entering Failed Delivery or Collection checks or feedback.


Line 143:		Line 143:
	* Values can be pre-set in the fields, for example, pre-checking a box for the signatory.		* Values can be pre-set in the fields, for example, pre-checking a box for the signatory.
	* Fields can be required to be entered, for example, "Check this box to agree to the T&Cs above" - not checking the box means that the signature cannot be completed.		* Fields can be required to be entered, for example, "Check this box to agree to the T&Cs above" - not checking the box means that the signature cannot be completed.
			{{Note}} At this time, photos may not be taken within Signatures. If the T&Cs is configured to have photos, the signature screen will simply display the text of the label, without the facility to enter the photos themselves.

	Use cases for data entry in T&Cs:		Use cases for data entry in T&Cs:
Line 149:		Line 150:
	* Acceptance of Terms and Conditions.		* Acceptance of Terms and Conditions.
	* Data Capture by the driver (for example, a number of empty pallets picked up, payment received, demurrage, etc).		* Data Capture by the driver (for example, a number of empty pallets picked up, payment received, demurrage, etc).
			* Exit Weighbridge Weight and Number


Line 159:		Line 161:
	* Site Waiver documentation		* Site Waiver documentation
	* Gatehouse data capture for example, Weighbridge		* Gatehouse data capture for example, Weighbridge
	* ~~Capturng~~ demurrage time		* Capturing demurrage time

Anw: Added Arrival Photographs as a use case for Job Details UDF

2018-02-01T11:48:54Z

Added Arrival Photographs as a use case for Job Details UDF

← Older revision		Revision as of 13:48, 1 February 2018
Line 55:		Line 55:
	* scanning of a location barcode to confirm arrival at the correct location.		* scanning of a location barcode to confirm arrival at the correct location.
	* Weighbridge Weight and Number		* Weighbridge Weight and Number
			* Arrival Photographs

	In these cases, specific buttons can be added to these forms, so that validation can occur. In this case, alerts and confirmations can be displayed, allowing the system to be widely configured.		In these cases, specific buttons can be added to these forms, so that validation can occur. In this case, alerts and confirmations can be displayed, allowing the system to be widely configured.
Line 72:		Line 73:
	* Capturing ad-hoc items collected/delivered		* Capturing ad-hoc items collected/delivered
	* Weighbridge Weight and Number		* Weighbridge Weight and Number
			* Arrival Photographs

Anw: Picture resolution

2017-11-29T09:28:45Z

Picture resolution

← Older revision		Revision as of 11:28, 29 November 2017
Line 58:		Line 58:
	In these cases, specific buttons can be added to these forms, so that validation can occur. In this case, alerts and confirmations can be displayed, allowing the system to be widely configured.		In these cases, specific buttons can be added to these forms, so that validation can occur. In this case, alerts and confirmations can be displayed, allowing the system to be widely configured.

	<gallery widths=~~250px~~ heights=~~300px~~ perrow=3>		<gallery widths=300px heights=450px perrow=3>
	File:ePOD_Job_Prework1.PNG\|''Pre-work - location barcode''		File:ePOD_Job_Prework1.PNG\|''Pre-work - location barcode''
	File:ePOD_Job_Prework2.PNG\|''Pre-work - Validation''		File:ePOD_Job_Prework2.PNG\|''Pre-work - Validation''
Line 84:		Line 84:


	<gallery widths=~~250px~~ heights=~~300px~~ perrow=3>		<gallery widths=300px heights=450px perrow=3>
	File:EPOD_Collection1.PNG\|''Collection Capturing Pallets Unloaded''		File:EPOD_Collection1.PNG\|''Collection Capturing Pallets Unloaded''
	File:EPOD_Delivery1.PNG\|''Delivery Capturing Pallets Unloaded''		File:EPOD_Delivery1.PNG\|''Delivery Capturing Pallets Unloaded''
Line 160:		Line 160:


	<gallery widths=~~250px~~ heights=~~300px~~ perrow=3>		<gallery widths=300px heights=450px perrow=3>
	File:ePOD_Job_PrejobSign1.PNG\|''Pre-job Signature''		File:ePOD_Job_PrejobSign1.PNG\|''Pre-job Signature''
	File:ePOD_Signature1.PNG\|''Customer Signature''		File:ePOD_Signature1.PNG\|''Customer Signature''
Line 200:		Line 200:


	<gallery widths=~~250px~~ heights=~~300px~~ perrow=3>		<gallery widths=300px heights=450px perrow=3>
	File:EPOD_Load_Metrics.PNG\|''Start Metrics''		File:EPOD_Load_Metrics.PNG\|''Start Metrics''
	</gallery>		</gallery>
Line 282:		Line 282:


	<gallery widths=~~250px~~ heights=~~300px~~ perrow=3>		<gallery widths=300px heights=450px perrow=3>
	File:EPOD_VehicleChecks.PNG\|''Vehicle Checks''		File:EPOD_VehicleChecks.PNG\|''Vehicle Checks''
	</gallery>		</gallery>
Line 326:		Line 326:


	<gallery widths=~~250px~~ heights=~~300px~~ perrow=3>		<gallery widths=300px heights=450px perrow=3>
	File:EPOD_CancellationUDF1.PNG\|''Cancellation UDF''		File:EPOD_CancellationUDF1.PNG\|''Cancellation UDF''
	</gallery>		</gallery>
Line 364:		Line 364:


	<gallery widths=~~250px~~ heights=~~300px~~ perrow=3>		<gallery widths=300px heights=450px perrow=3>
	File:EPOD_Collection_ContainerUDF.PNG\|''Container UDF''		File:EPOD_Collection_ContainerUDF.PNG\|''Container UDF''
	File:EPOD_Collection_ProductUDF.PNG\|''Product UDF''		File:EPOD_Collection_ProductUDF.PNG\|''Product UDF''

Anw: Added advanced guide

2017-09-04T08:05:26Z

Added advanced guide

← Older revision		Revision as of 10:05, 4 September 2017
Line 371:		Line 371:

	More details on the operation of this process can be found here: [[PDA Collection]] and [[PDA Delivery]].		More details on the operation of this process can be found here: [[PDA Collection]] and [[PDA Delivery]].


			[[Category:UG 291097 EPOD Advanced Guide\|250]]