Topics: |
A work order processes data for a given subject through a series of work order items. A work order is associated with a transaction ID. Records marked with the work order transaction ID will be included in subsequent processing.
The following list describes the types of work orders.
The following syntax shows the REST API service:
/server/processInstance
In a DELETE_STALE work order, all INACTIVE records of a given subject that were last updated before the Purge Inactive Age are deleted. This includes source, instance, and history reference records. The Purge Inactive Age is a Runtime setting to specify the number of days after which INACTIVE records will be deleted.
The following list describes the work order states.
Topics: |
This section lists and describes the work order items.
In this step, the work order state moves from SCHEDULED to ACTIVE. This is the first item in every work order.
The following processes describe the steps involved in the RAMP_TO_MODEL work order item, which is invoked for non-mastered, non-cleansed subjects.
For more information on the Ramp Load policy, see the Omni-Gen Integration Edition Relational OnRamp User's Guide.
A list of codes and the fields which reference those codes are also collected in memory during ramp processing. checkForMissingCodeXRefs identifies the new code-field references and adds them to the os_source_code_xref table.
Note: When a SourceInstanceID is trimmed of leading and trailing whitespace, a warning message is logged. If the trimmed SourceInstanceID contains a space or a colon, the record will not be moved to the source table and an error is logged.
Parent records are not auto-generated for orphan records.
The following steps will be included if the captureHistory attribute in the instance is true.
This step runs only if the Enable/Disable CDC Notification runtime setting is true.
The os_cdc_change table is populated with the XML representation (Omni Interface Document) of instance records in the current transaction for which a CDC subscription exists.
In this step, the status, result type, and end date of the work order are updated. This is the last item in every work order.
Topics: |
The following is a high-level summary of how to automate a sequential set of batches to process:
The automation job is a work order of its own. It is composed of a series of work order items that may also create other work orders. With this in mind, you are able to track the progress of the automation from the work order processing screen.
Each automation work order item will be attempted until one fails or the work is complete. This is no different than regular work order processing.
To support automation, the following functions were added:
You are required to use a text editor and a Swagger interface for automation purposes.
Automation creates a work order and corresponding work order items from the provided JSON document. The tags match the role and purpose of the tags in their respective tables.
The following syntax shows a sample automation JSON document.
{ "sourceType":"USER_DEFINED", <-- Required. "subject":"dynamic", <-- Required, value up to user, should not be the name of a subject. "sourceName":"devops", <-- Required, value up to user. "omniSystemType":"SERVER", <-- Only SERVER supported at the moment. "workOrderItem":[ { "workOrderItemName":"START_BATCH", <-- Required as is. "workOrderItemNameExtension":"car-batch", <-- Used to differentiate different batches. "processorOrder":1, <-- Required and must be sequential across work order items. "jsonContext":{ <-- These are the parameters passed in to starting the batch. "subject":"Car", "batchId":"abb5bca6-0565-4344-b85a-fa975456ec11", "sourceSubType":"MERGE_PRESERVE_ON_NULL", "source" : "TestSource” } }, { "workOrderItemName":"WAIT_FOR_ALL_COMPLETE", <-- This task has an 1 min idle time, be patient. "processorOrder":2 <-- Make sure to increment this. }, { "workOrderItemName":"START_BATCH", "workOrderItemNameExtension":"pet-batch", "processorOrder":3, "jsonContext":{ "subject":"Pet", "batchId":"e24f889a-bc4d-473b-85e3-3cd97d06dd42", "sourceSubType":"MERGE_PRESERVE_ON_NULL", "source" : "TestSource" } }, { "workOrderItemName":"WAIT_FOR_ALL_COMPLETE", "processorOrder":4 } ] }
To start the automated work order:
https://<hostname>:9500/swagger-ui.html#!/WorkOrder/postWorkOrderUsingPOST
View the automation executing on the console work order screen.