Optimizer Transactions Object
The Optimizer Transactions object is used to store the updates made to Event or Technician. Whenever a technician or event is created a record is created in the Optimizer Transactions object with the relevant details. Similarly, when an event or technician is modified the corresponding optimizer transaction record is updated too. The optimizer transaction records are then sent to the Optimizer to incorporate the changes.
Optimizer transactions play an important role when MaxQ scheduling is enabled in the org. For every action performed on the work order, technician, and event, a corresponding Optimizer Transaction record is created using specific whattypes. For information about whattyypes, see the WhatType Descriptions section.
 |
Optimizer Transactions views help you understand the transactions between ServiceMax and Schedule Optimization server on the Amazon Web Services (AWS). These views can help monitor and debug the transactions if needed. For more information about the Optimizer Transactions views, see Optimizer Transaction Views.
|
The following table describes the fields of Optimizer Transaction object records.
|
Field
|
Description
|
|---|---|
|
Optimizer Change Token
|
The token indicates the type of transaction. For example, token CHANGE_CREATE_TECH means that the record is created for new technician record creation.
|
|
Optimizer Error Text
|
The error code and error text if the transaction is not successful.
|
|
Optimizer Retry Count
|
The number of retries made if the transaction is not successful.
|
|
Optimizer Status
|
The current status of the transaction record with respect to the optimizer.
|
|
WhatId
|
The Salesforce id of the element. For example, Work Order, Technician, or Event.
The whatId of the transaction record is pushed to the RTO abstraction layer as input.
|
|
WhatType
|
The type of entity for which the transaction record is created. See the WhatType Descriptions table for the list of whatTypes used.
|
|
Work Order
|
Work order ID if the transaction record is created for the work order.
|
|
Optimizer Connection Identifier
|
The ID indicates the territory and dispatch process ID associated with the transaction.
|
WhatType Descriptions
The following table describes the various type of Optimizer Transaction object records.
|
WhatType
|
Description
|
||
|---|---|---|---|
|
WORK_ORDER
|
Record is created for the work order whenever an RTO work order is canceled or deleted.
|
||
|
NON_WO_EVENT
|
Record is created whenever a non-work order event is created, updated, or deleted.
|
||
|
Technician
|
Record is created whenever a technician record is created or updated.
|
||
|
BATCH_TECHNICIAN
|
Record is created when technician updates are performed.
|
||
|
ECO_WORK_ORDER
|
Record is created whenever MaxQ is enabled in the org, and a work order is created.
|
||
|
ECO_EVENT
|
Record is created whenever a RTO work order event is created, updated, or deleted.
|
||
|
ECO_TECHNICIAN
|
Record is created whenever a technician record is created or updated in RTO.
|
Examples
The following is an example of an Optimizer Transaction record.
|
Field
|
Value
|
|---|---|
|
Optimizer Change Token
|
CHANGE_CANCEL_WO
|
|
Optimizer Error Text
|
Return Code:200 | Return Msg:OK
|
|
Optimizer Retry Count
|
1
|
|
Optimizer Status
|
OPT_COMPLETED
|
|
WhatId
|
WO-00000503
|
|
WhatType
|
WORK_ORDER
|
|
Work Order
|
|
|
Optimizer Connection Identifier
|
a282g0000008mPdAAI_a2m2g0000005B3dAAE (Dispatch Process ID_Territory ID)
|