Managing Your Custom Data

Andrew Dotto Updated by Andrew Dotto

Custom Data represents the building blocks that DRS uses to store additional information against key objects such as Customers, Orders, Jobs and Workers. It allows you to capture both operational and contextual data, which can be used for reference or to support scheduling decisions.

Custom Data fields can be configured in different formats depending on the type of information being captured:

  • Fixed values, such as Number or Date/Time
  • Closed lists, providing a predefined set of selectable options
  • Free text, allowing flexible, user-defined input

These options provide the flexibility to tailor the system to your specific business needs while maintaining structure where required.

Managing your Custom Data

You can select the Custom Data Type (area of the system) you wish to view the attributes for by using the dropdown menu: 

When editing Custom Data, you can: 

  • Amend the display mode to hide it, make it modifiable or non-modifiable 
  • Make it a mandatory field 
  • Give it a default value 
  • Add/Edit/Remove possible values 
  • Make the value depend on the value of another attribute.
  • Make it a comment field and therefore displayed on the Update Comments section.
  • Audit the field and therefore store any changes to a particular field within the object history. Please note to use this sparingly as will increase the size of your database.
  • If Job Custom Data, you can also show on scheduling / re-scheduling of a job such as appointment reason to ensure a value is selected.

Key Custom Data Items

There are a number of Key Custom Data Items that could come created by default in your system.

Object Type 

Custom Data Item

Function 

Customer / Order

CONTRACT

These are used to categorise Contracts either for the Customer or the Order object allowing further control of the allocation of jobs to workers. These values must also be added to Contract Rename

Order

PRIORITY

These must match the priority values coming from your back-office integration. These determines what type of impact the job has and how quick it needs to be attended. i.e., Routine, Planned or Emergency

Job 

APPOINTMENT_SEQUENCE 

Additional appointment sequence values can be added. So, when a follow on is made, additional values could be selected.

Job 

APPOINTMENT_REASON 

Ability to amend the reasons of why appointments have been changed. 

Job 

USER_QUEUE 

Ability to create additional user queues which are used to place jobs that for any reason cannot be planned/scheduled in or for future reference. These can be selected when viewing a job > User Queue. This value can also be utilized in views.

Job 

TASK_COMPLETION_STATUS 

Ability to add/edit/remove completion reasons that are indicated once a job has been completed. This much match with the value sent from the mobile device.

Worker 

MOBILE_DEVICE_TYPE 

Messaging or Non-Mobile used when you have users not active on mobile devices and work off daily run sheets 

Worker 

REPORTING_GROUP 

Can be used to group workers together i.e., an area group or reporting manager.

­

Was this article useful?

Managing Your Organisations and Agencies

Managing your Contracts

Contact