External Commits

External commits can be optionally configured on workflow tasks to immediately synchronize approved changes in a governance request to an external target system when the request is committed. For example, an external operation can run an SQL statement that inserts, updates, or deletes data, or it can invoke a SOAP or REST Web service to create, update, or delete data in an external system. When you use external commits in Oracle Data Relationship Governance, external data updates can be initiated after a Data Relationship Governance request is successfully committed. The external data source is accessed using external operations defined for database and Web service connections.

After a Data Relationship Governance request has been successfully committed, external operations for each item are performed as configured by each item’s task.

• Operations are performed synchronously in the order defined, by item and task.

• Operations are performed in the context of the local node for the request item, allowing output parameters to be based on properties which may not be selected for the task.

• If an error occurs during an external operation, the error message is added to the request item as an External Commit Failure.

• Request activity is updated with success or failure after each external operation.

• If a Commit Status property is defined for the external operation, then that property will be updated to True if the operation completed with no errors, and updated to False if the operation completed with errors.

• If any external operations did not complete successfully, then Data Managers and Commit stage participants are notified.