Integrations settings control how the Epicor CPQ platform connects to your other resources.
Learn more about the types of integrations available with Epicor applications and external systems.
| Setting | Description |
|---|---|
|
General | |
| Auto-create New Logins for CRM Users |
If you are using a CRM integration (such as one of the Salesforce.com integrations), some of your CRM users may use Epicor CPQ as a tool embedded into another web page. Rather than have those users authenticate twice – first in that CRM tool and then a second time in Epicor CPQ – turn this feature on. Default: off |
|
Assign User's Role Based on Email Domain |
If the previous box is checked, then this option appears to help you control what these CRM users can see and do by assigning them a role. There are two ways to assign native Epicor CPQ roles to visiting CRM users.
Examples:
|
| Roles for new CRM users |
If "Assign User's Role Based on Email Domain" is unchecked, this is a simple list of roles each new user connecting from the CRM will be assigned. |
| Group Mappings |
If "Assign User's Role Based on Email Domain" is checked, this allows you to select which email domains map to which roles. Click "Add New Mapping" to enter an email domain (e.g. example.com) and select which roles users coming in via that email domain that will map to. |
|
Single Sign-On | |
| Enable SSO | Allow some users to authenticate to Epicor CPQ through your own federated authentication service. Default: off We suggest at least one Epicor CPQ User with the company administrator role be created in Epicor CPQ directly, through Settings > Users, not through SSO. In this way, if there is a problem with your SSO service at least one Epicor CPQ company administrator will still be able to do their work. |
|
Tenant ID |
The SSO tenant ID provided to you. Click the "Sign Up" button to begin the provisioning process. Default: blank |
| Group Mappings |
After SSO is fully connected, you have the opportunity to map Azure AD groups to Epicor CPQ roles. As users sign in via SSO, they will be assigned their roles accordingly. |
| Epicor Kinetic ERP | |
| Enable Kinetic Integration | Check this box to activate a connection between this Epicor CPQ org and a specific instance of Epicor Kinetic. |
| Kinetic Base URL | Enter the path to your kinetic instance. |
|
Kinetic Username Kinetic Password |
Enter the credentials for the kinetic user who will be transacting on behalf of the integration process. This is usually a dedicated role, like "Integration Service" or "Data Robot", and not a specific person. |
| Test Connection | Use this button to confirm your URL and credentials work. |
|
Salesforce | |
| Enable Salesforce Integration |
If your company uses Salesforce.com, and you've installed the Epicor CPQ App from the AppExchange, enter the correct settings here to activate the integration. Step-by-step instructions are available. Default: off |
| Integrate with Salesforce CPQ |
Check here to activate the Salesforce CPQ integration. Default: off |
|
Salesforce API Username Salesforce API Password Salesforce API Token |
Epicor CPQ needs a way to log into your Salesforce data. After you create a Epicor CPQ user in your salesforce org, gather up the username, password, and token and enter these three credentials here. Step-by-step instructions are available. |
|
Salesforce Canvas App Consumer Key Salesforce Canvas App Consumer Secret |
Epicor CPQ needs a way to insert its information into the salesforce.com web page where your users work. After installing the Epicor CPQ App from the Salesforce.com AppExchange, you'll see these two parameters in salesforce. Copy and paste them here. |
|
Use Salesforce Files instead of Attachments |
Earlier versions of Salesforce used Attachments to store PDFs, images, and other large files. We suggest you use the more modern Salesforce storage object, called Files. For backwards compatibility with legacy salesforce orgs, you can turn this off. |
|
Use Salesforce Sandbox |
If you intend to connect to a sandbox on test.salesforce.com, check this box. For example, your DEV and TEST instances may connect to a salesforce sandbox, so this would be turned on, and your PROD instance may connect to production salesforce (so this would be turned off). |
|
Oracle CPQ | |
| Enable Oracle CPQ Integration | If you use this integration, activate it by checking this box. |
Oracle CPQ Company Domain |
Epicor CPQ needs a way to log into your Oracle data. After you create a Epicor CPQ user in your Oracle instance, gather up the username, password, and company domain and enter these three credentials here. |
| Check Credentials | Use this button to confirm your Oracle domain and credentials work. |
Depending on the features your company has activated, some choices listed here may not appear.