Considerations That Apply to Upsert Operations

When you run the Upsert command for workflow rules, the existing workflow rules are updated, new workflow rules are inserted, and rules that are not in the request are deleted. For the purposes of the Oracle Migration Tool On Demand client, this is known as an Upsert operation.

The following considerations apply to Upsert operations for workflow rules:

• The workflow rules are ordered as they appear in the input XML file.

• You cannot upsert two workflow rules with the same order number.

• If the workflow rule name does not match an existing workflow rule name, then a new workflow rule is created.

• If the workflow rule name matches an existing workflow rule name, then the record type and trigger event cannot be modified.

• The migration service protects data from becoming corrupted if the workflow rule is edited during loading, or loaded twice simultaneously, or extracted while it is being loaded.

• The input file must contain only the workflow rules that are based on a unique combination of a record type and trigger event. For example, the input file can contain one or many workflow rules based on the Account record type and the When New Record Saved trigger event. The input file cannot contain another workflow rule with a different record type or trigger event.

• The user running the Upsert command must have access to the object so that the Upsert command completes successfully.

About Inserting, Updating, and Deleting Scheduled Events

A scheduled event is a workflow rule that is automatically executed when a specified date and time is reached. For more information about scheduled events, see Oracle CRM On Demand Online Help.

When you insert a new scheduled event record in a target environment, Oracle CRM On Demand generates a pending instance for the first scheduled occurrence of the event, if the scheduled event is active (that is, the <Active> element on the scheduled event record is set to true). If the scheduled event is not active, then a pending instance is not generated.

When you update a scheduled event record in a target environment, the following happens:

• Oracle CRM On Demand deletes any pending instance of the scheduled event in the target environment.

• If the scheduled event is active, then Oracle CRM On Demand generates a new pending instance for the next scheduled occurrence of the event.

When you delete a scheduled event record in a target environment, Oracle CRM On Demand deletes any pending instance of the scheduled event in the target environment.