Updating or Inserting a Workflow Action Set (Upsert)
This topic describes how to use the Upsert
command
to update a workflow action set (if it exists) or insert a workflow
action set (if it does not exist) in your Oracle CRM On Demand environment;
that is, a customer test environment or production environment. For
the purposes of the Oracle Migration Tool On Demand client, this
is known as an Upsert operation.
Running an Upsert operation on a workflow action set is a synchronization operation. At the end of the operation, the workflow action set matches the action set in the XML file, where possible. Existing workflow actions are updated, new actions are inserted, and actions that are not in the request are deleted. The order of the actions in the workflow request matches the order of the actions in the action set XML file. The updates to workflow action sets in an Upsert operation are applied completely or not at all.
Syntax
The following is the syntax for using the Oracle Migration Tool On Demand client to update a specific workflow action set (if it exists) or to insert the workflow action set (if it does not exist):
migrationtool -u UserID -s ServerURL Upsert WorkflowActionSet WorkflowActionSetXML
where:
UserID is the user sign-in ID that has the appropriate privileges to run the Oracle Migration Tool On Demand client commands.
ServerURL is the URL for the Oracle CRM On Demand server where your company resides.
WorkflowActionSetXML is the fully qualified path name of the workflow action set XML file, for example:
C:\My Files\My WorkflowActionSet.xml
Example of Updating or Inserting a Workflow Action Set
The following is an example of updating a workflow action set (if it exists) or inserting a workflow action set (if it does not exist) in your Oracle CRM On Demand server:
migrationtool -u UserID -s ServerURL Upsert WorkflowActionSet "C:\My Files\My WorkflowActionSet.xml"