Scheduling Change Token in Real-time Optimization
In Real-time Optimization, when the user changes the values in the scheduling-related fields of the work orders after the initial assignment by the Schedule Optimization engine, the changes are tracked in the Scheduling Change Token field in the form of tokens.
The tokens are updated as values in the Scheduling Change Token field differently for each update in the scheduling-related fields, which are as follows:
|
Work Order Field Update
|
Scheduling Change Token Value
|
Notes
|
|---|---|---|
|
Order Status=Canceled
OR
The Canceled Date Time is updated
|
CHANGE_CANCEL_WO
|
|
|
Zip
|
CHANGE_ZIP_CODE
|
|
|
Latitude/Longitude
|
CHANGE_LAT_LONG
|
|
|
Skill Set
|
CHANGE_SKILL_SET
|
|
|
Qualified Technicians
|
CHANGE_QUALIFIED_TECHNICIAN
|
|
|
Service Duration (in seconds)
|
CHANGE_SERVICE_DURATION
|
|
|
Preferred Technician
|
CHANGE_PREFERRED_TECH
|
|
|
Preferred Business Hours
|
CHANGE_ACCESS_HOURS
|
|
|
Preferred Start Time/Preferred End Time
|
CHANGE_PREFERRED_TIME
|
|
|
Component
|
CHANGE_COMPONENT_RESOURCE
|
This is applicable only if Resource Preference is defined in the work order.
The token is populated when component is added or updated in the work order when setting SET051 (Enable Resource preference management for Work Order) is True.
|
|
Site
|
CHANGE_SITE_RESOURCE
|
This is applicable only if Resource Preference is defined in the work order.
The token is populated when the Site information is added or updated in the work order when setting SET051 (Enable Resource preference management for Work Order) is True.
|
|
Dispatch Priority
|
CHANGE_PRIORITY
|
|
|
Contact
|
CHANGE_ACCOUNT_INFO
|
|
|
Country/City/State/Street
|
CHANGE_ADDRESS_INFO
|
|
|
Dispatch Process
|
CHANGE_DISPATCH_PROCESS
|
|
|
Lock Appointment Schedule=Lock To arrival window
|
CHANGE_SCHEDULE_LOCK
|
The Lock Appointment Schedule field value is also set to Lock To arrival window when the work order is a Ranked appointment Booking work order. However, the scheduling token does not change in that scenario.
|
|
Locked By DC
|
CHANGE_JOB_FIXED
|
|
|
When the following actions are performed on a manually assigned work order having token as CHANGE_JOB_FIXED the token is updated to CHANGE_JOB_UNFIXED:
• Unassign a force-fixed work order in Dispatch Console.
• Reset a work order in Service Board.
• Uncheck the Locked by DC flag.
• Change Lock Appointment schedule from Lock in Place to None.
|
CHANGE_JOB_UNFIXED
|
|
|
Primary Territory and Dispatch Process = Not Null
|
CHANGE_CREATE_WO
|
• When these field values are not null, the work order qualifies for the RTO dispatch process.
• Unlike the other scheduling change token updates, this update occurs immediately after the work order qualifies for the RTO dispatch process.
|
|
Account
|
CHANGE_ACCOUNT_RESOURCE
|
The token is populated with this value when the account information is added or updated in the work order when setting SET051 (Enable Resource preference management for Work Order) is True. If the setting is False, the token is updated to CHANGE_ACCOUNT_INFO.
|
 |
If multiple scheduling fields are updated, the token is updated with the value of the field having higher preference. For example, when the service duration and the preferred start time are updated in the same transaction, the token is updated to CHANGE_SERVICE_DURATION.
|