| Print Open PDF Version of Online Help

#### Creating Workflow Actions: Create Integration Event A Create Integration Event action on a workflow rule automatically sends an integration event to one or more integration queues when the conditions on the workflow rule are met and a change is detected in at least one of the fields that are tracked by the Create Integration Event action. ### About Create Integration Event Actions and Wait Actions If you want to use a Create Integration Event action to create an integration event that captures the changes made to a record by the event that triggers a workflow rule, then you must place the Create Integration Event action before any Wait action in the sequence of actions on the workflow rule. If a Wait action precedes a Create Integration Event action on a workflow rule, then the Wait action prevents the Create Integration Event action from detecting changes to the record. When the waiting period on the Wait action ends, the record is read again before the remaining actions on the rule are performed, and the values of the fields on the record before the event that triggered the workflow rule are not preserved. Therefore, the previous value and the current value of a field are considered to be the same, and the Create Integration Event action does not create an integration event because it does not detect any change in the tracked fields. ### About Picklist Value Formats in Integration Events Depending on how you set up your integration event queues, the values in picklist fields in the integration events are recorded either in the language of the user whose action causes the integration event to be created, or as language-independent code (LIC) values. For information about specifying the picklist value format for an integration event queue, see Creating Integration Event Queues and Managing Integration Event Settings. ### About the Billing, Shipping, and Primary Flags in Account and Contact Address Records In integration events for the Account Address record type, you can include the Billing and Shipping flags that indicate whether an address is the designated billing address or shipping address for the account. Similarly, in integration events for the Contact Address record type, you can include the Primary flag that indicates whether an address is the primary address for the contact. However, you cannot track changes to the Billing, Shipping, and Primary flags. This means that changes to these flags cannot be used to trigger the creation of integration events, even if you select the Always Include check box for the flags. If you include one of these flags in an integration event, and if that flag is changed at the same time as a field for which the changes are tracked, then the integration event that is created as a result of the change to the tracked field does not show the new value of the flag. Instead, the integration event shows the value of the flag before the update was made. However, the next time that an integration event is created as a result of a change to a tracked field, the integration event includes the value of the flag field after the previous update was made. For example, assume that you have two addresses, Address A and Address B, linked to a contact called Jane Smith. Address A is the primary address for Jane Smith. You have a workflow Create Integration Event action for the Contact Address record type that is configured as follows: The Track Changes check box is selected for the Address Type field only. The Always Include check box is selected for the Primary field. If a user updates the Address Type field on Address A from the contact address record for Jane Smith and also deselects the Primary check box for Address A, then the integration event that the workflow action creates as a result of the change to the Address Type field shows the new address type, but the value of the Primary flag in the integration event still indicates that the Address A is the primary address for Jane Smith. However, the next time that the Address Type field on Address A from the contact address record is changed and an integration event is created as a result of the change, the Primary flag in the integration event shows that Address A is not the primary address for Jane Smith. NOTE: You can create multiple actions for a workflow rule, up to a maximum of 25 actions for each rule. The following procedure describes how to create a Create Integration Event action. Before you begin. To perform the procedure described here, you must have the Manage Data Rules - Manage Workflow Rules privilege in your user role. For information on adding privileges to roles, see Adding Roles. To create a Create Integration Event action Navigate to the rule where you want to create the action: In the upper-right corner of any page, click the Admin global link. In the Business Process Management section, click Workflow Configuration. On the Workflow Rules List page, find the rule where you want to create the action. For information about searching for workflow rules in the list page, see Filtering Lists. Click the Workflow Name link on the rule. In the Actions title bar on the Workflow Rule Detail page, click Menu, and select Create Integration Event. NOTE: The trigger event on the workflow rule determines what types of actions can be created on the rule. TIP: You can create a copy of an existing workflow rule action by clicking the Copy link for the action. In the Workflow Action Edit page, enter a name for the action. If you want to enable the action, select the Active check box. Select the integration queues to which the integration events will be written. In the Schema Version field, if the record type for the workflow rule supports the schema for both Web Services v1.0 and Web Services v2.0, then select the Web service version that is to be used for the integration events. If the record type for the workflow rule supports the schema for both Web Services v1.0 and Web Services v2.0, then Web Services v2.0 is selected by default in the Schema Version field, but you can change the selection before you save the workflow action. NOTE: After you create and save the workflow action, you cannot change the value in the Schema Version field. If the record type for the workflow rule supports only one schema, then that Web service version is selected by default. For more information about the Web services, see Oracle Web Services On Demand Guide. Save the workflow action. From the record-level menu in the list of actions, select Configure for the integration event action that you want to configure. NOTE: The Configure option is not available for actions where the trigger event is When Records Are Merged. In the Configure Integration Event Tracking page, select the check boxes for the fields, as needed: Select the Always Include check box if you want the field to be included in the integration event even if the value of the field has not been changed. Select the Track Changes check box if you want an integration event to be generated each time this field is updated. Save your changes. The following table describes the fields on the Configure Integration Event Tracking page.
Field | Description
--- | ---
Display Name | The name of the field as it is displayed in the user interface.
Integration Tag | The integration tag that is used when the field is included in the integration event. Integration tags are displayed in the Integration Tag Web Services v2.0 column in the record type Fields page.
Required | This read-only check box indicates if the field has been set up as a required field.
Always Include | Select this check box if you want the field to be included in the integration event even if the value of the field has not been changed. NOTE: The Always Include check box is selected by default and cannot be deselected for certain fields used by Oracle CRM On Demand.
Track Changes | Select this check box if you want an integration event to be generated each time that this field is updated. For more information about the Track Changes check box, see About the Track Changes Check Box in this topic.
### About the Track Changes Check Box The Track Changes check box is not available if the trigger event for the workflow rule is Before Record Is Deleted, After Association With Parent, or After Dissociation From Parent. Also, if the trigger event for the workflow rule is After Association With Parent, or After Dissociation From Parent, then the set of fields displayed on the page will be the set of fields at the child record level. You cannot configure the set of fields included in the integration event at the parent record level. For workflow actions on which the Track Changes check box is available, the workflow action creates an integration event only if the Track Changes check box is selected for at least one field, and if a change is detected in at least one of the fields for which the Track Changes check box is selected. When the integration event is created, all of the fields that have the Always Include check box selected in the workflow action are included in the integration event. ### System Field Exceptions If the trigger event for the workflow rule is anything other than When New Record Saved, then Oracle CRM On Demand does not generate integration events in cases where the Track Changes check box is selected for one or more of the following system fields, and the Track Changes check box is not selected for any other field: ModifiedDate ModifiedById CreatedDate CreatedById Id For more information about integration events, see About Integration Events. For step-by-step procedures for creating other types of workflow actions, see the following topics: Creating Workflow Actions: Assign a Book Creating Workflow Actions: Create Task Creating Workflow Actions: Send Email Creating Workflow Actions: Update Values Creating Workflow Actions: Wait #### Related Topics See the following topics for related information about workflows: About Workflow Rules About Workflow Actions About Time-Based Workflow Rules Creating Workflow Rules Changing the Order of Workflow Rule Actions Deactivating Workflow Rules and Actions Deleting Workflow Rules and Actions About Integration Events

Published 5/23/2022 | Copyright © 2005, 2022, Oracle and/or its affiliates. Legal Notices.