The following components need to be configured before this app can be used.
To modify configuration settings, navigate to Apps, select your app, and click the Configure icon.
Warning: Selecting the Reinstall icon will force you to go through the entire configuration process again. The app will be unavailable for all users during the reinstall.
The Connections page lists all of your CRM connections and associated credentials.
3. Click Save
In order to reset the password, click Manage Credentials.
A connected app is a framework that enables an external application to integrate with Salesforce using APIs and standard protocols, such as SAML, OAuth, and OpenID Connect. Connected apps use these protocols to authenticate, authorize, and provide single sign-on (SSO) for external apps.
Prerequisites: Salesforce connected app: Create a connected app in Salesforce so that you can get the following values to enter when creating a connection:
Consumer key: Displayed in the Salesforce connected app after creation.
Consumer secret: Displayed in the Salesforce connected app
Configuration:
The Connections page lists all your CRM connections and associated credentials.
3. To reset the connection details, click Manage Credentials.
The following instructions are based on Salesforce Classic. For Lightning Experience and Classic details, read Salesforce’s connected app documentation.
6. In the API (Enable OAuth Settings) section, select Enable OAuth Settings. Additional options are displayed.Keep the Require Secret for Web Server Flow option, which is selected by default.
7. Enter Call back URL, (https://edi.portqii.com/decisionService/getSFDCOAuth)
8. In the Selected OAuth Scopes section, select the appropriate scopes or select all available scopes.
At a minimum, the following scopes are required:
The custom_permissions scope is recommended. Determining whether it is needed depends on your Salesforce configuration.
9. Click on Save.
10. Select Create > Apps.
11. In the Connected Apps section, find your connected app in the list and click on its name.
12. In the connected app’s API (Enable OAuth Settings) section, record the Consumer Key and Consumer Secret values.
Snowflake is a data warehouse on top of the Amazon Web Services or Microsoft Azure cloud infrastructure. There is no hardware or software to select, install, configure, or manage, so it is ideal for organizations that don’t want to dedicate resources for setup, maintenance, and support of in-house servers.
To enable it please contact support@portqii.com for license and to get it installed in your instance. Once the license is enabled, must be configured on the application’s Admin Configuration page by the users who have Admin access:
The Connections page lists all your CRM connections and associated credentials.
3. To reset the password, click on Manage Credentials.
Adding external system objects will allow marketers to segment against these objects in the external system. External system objects added here will be imported into the Oracle Eloqua Contact table when executing the segment.
1. Click the Menu icon against the configured external system connection and select Configuration. A list of existing configured connections will be shown to the user.
2. To add an external object to execute segments against, click the Plus icon .
3. Choose the object and then click the Add button.
NOTE: Only objects containing an email address will be shown from the list of available objects. This is because records from this object will be imported into the Contact table in the Oracle Eloqua instance.
Field mappings are configured for external objects added in the configuration setting of the app. This allows data to be imported to the Oracle Eloqua Contact table from the base object of the external system plus any parent object from the base object.
1. Click the Menu icon against the added external system object and select Field Mapping. A list of existing configured field mappings will be shown to the user.
NOTE: By default, at least one field of type Email will be added by the system. This is to ensure that the system is passing in an email address field as it will be used as a match field for existing records that already exist in Oracle Eloqua.
2. To add more fields to the field mapping click the Plus icon
3. Choose the field from the base external system object (defaulted) or a parent object. Users can choose to map fields from parent objects 5 levels above the base external system object.
4. Choose the Unique Identifier field and Update Rule that has to be applied during file import. Users can choose to select any mapped field as Unique Identifier and choose an action from Update Rule dropdown.
Data priority compares new data to existing data, then determines whether to update contact data depending on the source. Further information on how Oracle Eloqua’s data import priority works can be found here.
1. Click the Menu icon against the added external system object and select Set Import Priority.
2. Select one of the import priorities configured in the Oracle Eloqua instance and click Save.
The use of this application is only available to those users that have been given permission by the Oracle Eloqua administrator in which the app is installed in.
1. To add a single user, type the user name under the Single User tab. As the user types ahead a list of users will become visible allowing the administrator to select one user from the list of users matching the search term.
2. Clicking the Plus icon will add the user to grid below giving that user permission to use the app.
3. Multiple users can also be added by searching for users under the Multiple Users tab and adding one or more user that meet the search criteria.
Global Exclusion Criteria will allow marketers to create segments with an automatic built in Exclusion Criteria. Once configured this exclusion criteria will apply to ALL feeder instances (new and existing) depending on the type of configuration. If an exclusion criteria is changed then ALL existing feeder instances will be updated. Note that end users configuring feeder instances will NOT be able to change the exclusion criteria. Only Admins will be allowed to define and adjust these exclusion criterias.
1.Click the Menu icon against the added external system object and select Global Exclusion.
2.In the left pane click Add. Then click on the following options
3. Choose to build your filter criteria condition using fields from the base table or from tables related to the base external object selected. Click Save once the filter criteria is defined.
4. Click on Enable to apply Global Exclusion Criteria to the New Segments. Click on Apply for Existing Feeders to apply Exclusion Criteria to all Existing and New feeders. This will exclude the contacts to be imported into Eloqua.
5. To Disable the Exclusion Criteria, click on Disable. This will not allow Exclusion Criteria to be applied to New Segments. Click on Apply for existing Feeders and then on Disable button to remove Exclusion Criteria from existing feeders and also to not allow Exclusion Criteria to be applied to new Segments.
Do not create contact in Eloqua is a helpful feature when a user does not want to create a new contact from an External system* to Eloqua, this feature allows the user to just update the already present contacts in Eloqua.
The user needs a license for Do not create contact in Eloqua. To enable this feature please contact sales@portqii.com to get it installed in your Eloqua instance. Once the license is enabled it must be configured on the application’s Admin Configuration page by the users who have Admin access:
The Do not create contact in Eloqua feature can be enabled/disabled in the following manner:
4. After enabling this feature, EDI will process the contacts using Segments and Picklists (By default EDI will create 10 segments and picklists).
5.Admin can select the folder by clicking on the edit icon on the right side, on click of edit one popup will open showing the folder list user need to select the folder, selected folder will be used for store created segments.
6. Now the DO not create contact in Eloqua is enabled for use.
When the Do not create contact in Eloqua feature is enabled if we find any Feeder or Decision Service activated for the connection that has the feature enabled. The system will check if already segments and picklists are there in the system it will use those to ensure to not create new contacts in Eloqua. If the feature is disabled Feeder service will Create/Update contacts in Eloqua that, we get from the salesforce query.
*This feature now available for both Salesforce and Snowflake connections.
Duplicate contact rule is a helpful feature when users have multiple contacts in salesforce with matching query criteria and the same email address. Eloqua does not allow to import contacts with the same email address.
The Duplicate contact rule must be configured on the application’s Admin Configuration page by the users who have Admin access:
The Duplicate Contact Rule can be applied in the following manner:
There are Four Duplicate Contact Rule
If the user has multiple contacts in salesforce with matching query criteria and same email address, and the duplicate contact rule selected in EDI Admin or Feeder Level it will import contacts based on the selected Duplicate Contact Rule.
Export Contact will help in exporting the contacts from Salesforce based on configured query and mapping.Export Contact will help in exporting the contacts from Salesforce based on configured query and mapping.
For the Export Contact feature user must have the Data Export access on the application’s Admin Configuration page by the users who have Admin access:
The Export Contact feature user access can be enabled/disabled in the following manner:
Following are the steps to be taken to initiate Export Contacts:
4. After the view contact popup is opened, click on Export.
5. On click of Export, it will check the user Access and download an Excel file (Maximum limit 50k Contacts)
1. If the user does not have export access it prompts User does not have access to Export.
2. If the contact count is more than 50k it will ask whether the user wants to export the top 50K contacts.
This feature lets users update Eloqua contacts with some Static values along with mapped Salesforce or Snowflake field values when importing contacts into Eloqua through EDI. As an example, if there is a requirement to know from where the contact information has been entered to Eloqua recently, adding a Static field that you can configure to contain the desired value can help the business know the recent source of contact update. This can be achieved through the admin settings or also at the EDI segment level. The following feature is available on both SFDC and snowflake connections.
4. Clicking on the + symbol will give you the option to add either SFDC fields (Snowflake fields for Snowflake connection) or Static fields. Choose ‘Add static field mapping ‘.
5. From the screen below, choose the data type of the field (Supported data types: Text, Numeric), give a label to the static field, choose the Target field from all Eloqua Contact fields dropdown, and then enter desired Static field value. Now you are set to add the static field to your field mappings.
6.Click on Add button to add it to your field mappings. You can add more than 1 static field to your field mappings and/or choose to delete any of these field mappings anytime.
7. Creating an EDI salesforce or snowflake feeder inside your campaign and clicking on view contacts will show you these static field values along with other salesforce or snowflake fields from Admin settings. These Static fields are suffixed with ** and an info message at the bottom of the table to differentiate them from the other Salesforce or Snowflake fields.
8. Users can also choose to override Admin level field mappings and add new/delete existing static fields at the feeder level. Go to Field Mappings on the feeder as shown below and repeat the actions mentioned in steps 4,5 and 6 to configure the feeder level field mappings.
9. Users can also choose to override Admin level field mappings and add new/delete existing static fields at the feeder level. Go to Field Mappings on the feeder as shown below and repeat the actions mentioned in steps 4,5 and 6 to configure the feeder level field mappings.
If the user has opened the field mappings on the Feeder and Static field values are added in Admin settings later, then that feeder no longer receives the updated field mappings from the Admin page and will not reflect new field mappings. In such cases, the user must configure desired field mappings on the feeder.
While configuring static field mappings, make sure that static field data type and the Eloqua contact field data type match. Any mismatch in field type will cause errors in the campaign when activated.
A Picklist is defined as a widget that shows a list of selectable options. When an option is selected, it is displayed as selected and the value of the read-only input is updated to match it. The picklist is a great way to keep data consistent and safe.
As Snowflake does not support the Picklist datatype, in External Data Intelligence applications we are providing a new feature to reuse the string field as picklist at the application level.
4. Choose the Object you want to add to the Picklist field mapping and click on the field mapping option.
5. From the screen below, choose the field from the base external system object (defaulted) or a parent object. Along with the mapping mark the checkbox to change the field as a picklist field and add it to the field mapping.
6.Click on Add button to add it to your field mappings. You can add more than 1 Picklist field to your field mappings and/or choose to delete any of these field mappings anytime.
1 After configuring the Picklist field mapping, click the Menu icon to add picklist values.
2. Save the values to make the field a picklist.
* We are releasing the automated feature to revert the Picklist field to normal in our upcoming releases.
This process is designed to add to the categories of people who receive notifications. From now on, apart from Portqii developers, even the EDI administrators will be notified of EDI related errors. The email address on the EDI admin configuration page is considered as the admin email – error notifications are sent to that email id.
Admin will be notified in case of following errors:
All the Notification emails sent from PortQii support will be CC’d to have PortQii Team members on the email.
Email alerts on product updates, new product announcements, special promotions and more!
