Customers

The checkForAccountNumber preference creates a link between the customer and the task, based on the account number. If the account number doesn't exist, the customer record will be created automatically, based on the task information.

checkForAccountNumber
Type	Default Value	Example
Boolean	false	true

If an uploaded task contains a different geocode than the one stored with the customer entry, the customer geocode will overrule, if the checkForGeocode preference is set.

Note that the checkForAccountNumber preference needs to be set to ensure this functionality.

checkForGeocode
Type	Default Value	Example
Boolean	false	true

If an onSite attachment is processed and the attachment contains a GPS coordinate, the customer geocode will be overruled by the new coordinates, if the checkForGeocodeOverwrite preference is set.

Note that the checkForAccountNumber preference needs to be set to ensure this functionality.

checkForGeocodeOverwrite
Type	Default Value	Example
Boolean	false	true

By default, gps is the only format which is accepted to overwrite customer geocodes. The preference checkForGeocodeOverwriteFormat allows the definition of other formats, for example: "gps,network". In that case, both gps and network locations with onSite task attachments are accepted for capturing the latest customer geocode.

checkForGeocodeOverwriteFormat
Type	Default Value	Example
String	Undefined	gps,network

If an uploaded task contains a different email than the one stored with the customer entry, the customer email will overrule, if the checkForEmail preference is set.

Note that the checkForAccountNumber preference needs to be set to ensure this functionality.

checkForEmail
Type	Default Value	Example
Boolean	false	true

In cases where customers are visited on a regular basis, it is useful to store the various names of customer employees signing for the service (if signature is required). Optimize My Day is capable of storing the last three names used during the customer signature process. The names are stored as a comma-separated list in the department field of the customer. If an uploaded task contains a different department than the one stored with the customer entry, the customer department will overrule. To activate this functionality, set the checkForDepartment preference to true.

Note that the checkForAccountNumber preference needs to be set to ensure this functionality.

checkForDepartment
Type	Default Value	Example
Boolean	false	true

Tasks may still have different addresses, even when they refer to the same account. In those cases, the address can be used to identify different locations (service or delivery points, ...). The preference checkForTaskLocation indicates if seperate locations should be created for each address of the account. OMD will create a unique hashed key of the address data to identify the location. This key is also used when storing service sheets for a customer in OMD Document Hub. Find more details here.

This preference is only effective if the preference checkForAccountNumber is set.

checkForTaskLocation
Type	Default Value	Example
Boolean	false	true