Creating step actions
Actions are data transactions between Oracle Eloqua and Salesforce. The Step Actions page is where you create the types of actions to be used in a program or campaign when using the app. You can create two types of actions: Create and Update. Create will create a new record in Salesforce, and Update will take an existing Oracle Eloqua contact and update their information in Salesforce. You can put actions through a test run with pre-configured contacts.
To create a step action:
- In the Salesforce.com Integration app, click Actions.
- Click Add Action and select a connection for which you want to create a new action.
- Complete the action details:
Note: Each action can map up to a maximum of 249 fields. See the Eloqua Developer Help Center for more information.
- Name: Enter a name for the action.
- Action Type: Select an action type from the list to either create or update contact records.
- Object Mapping: To see available fields for mapping, select an Eloqua object and Salesforce object. Top-level objects from your Salesforce instance are available in the Salesforce.com Object list.
If you select the Lead object from the Salesforce.com Object list for either a Create or Update action type, the Trigger Assignment Rule option is displayed. If you select Yes, a default assignment rule will be triggered in Salesforce upon lead creation when new Eloqua contacts are added. Only select Yes if you are using lead assignment rules in Salesforce. Setting it to Yes will cause the action to take longer to run and will increase your Salesforce API usage.
- Update Salesforce Fields: For each set of fields, specify the Salesforce field that will be mapped to Oracle Eloqua contacts. If you are updating contact records, the unique identifier is the first mapping shown in this list. Add more mappings by clicking Add Field Mapping. Click the menu to delete the mapping, or switch the field type to static text, static date, or dynamic date.
- Update Eloqua Fields: For each set of fields, specify the Eloqua field that will be mapped to Salesforce contacts. If you are creating contact records, the unique identifier is the first mapping shown in this list.
Note: After mapping a lead scoring model in an action, the other models will no longer be available for mapping in that action. Users will need to create another action to map another lead scoring model.Add more mappings by clicking Add Import Field Mapping. Click the menu to delete the mapping or switch a From Salesforce field type to static text, static date, or dynamic date.Salesforce field: Eloqua Object, Date, or Dynamic Date. You can also type static text into the box as needed. For contacts, you can use Advanced Mode to select a Contact and its fields. For custom objects, the Advanced Mode allows you to select a custom object and its related Contact fields.
- Import Rules: Specify data priority.
- Data Priority: Select the priority of data to resolve conflicts on imports, such as Bulk API and CRM Integration. If leads and contacts are being imported to Oracle Eloqua contacts, there may be situations where a lead and contact with the same email address exist. Eloqua's data priority can be used to instruct Eloqua which source, lead or contact, is higher priority. If the contact import is set to have a higher priority than the lead import, the data imported from the contact will not be overwritten by the lower priority lead data. Higher priority sources are never overwritten by lower priority sources. Data priority needs to be specified as part of an action to ensure that higher priority sources are not overwritten by lower priority sources from other imports.
- Click Save.
Your action is created and can be used in a program or campaign.
Click the drop-down list to modify the action. You can edit, enable, disable, duplicate, or view report data for the action. If an action is disabled, you can delete it. If you attempt to delete an action that is used on a canvas, a warning message will display, but it can be overwritten if desired.
Important: If an action is being used within a program or campaign and the action is disabled, contacts will not be processed until the action is enabled. Once the action has been re-enabled, the app will process all contacts.