Connect to Epicor Kinetic Data in RunMyProcess through Connect AI

Akorbi Digital RunMyProcess makes it easy to create applications for complex business applications, such as budget application and contract management. CData Connect AI creates a live connection to Epicor Kinetic and can be used to generate an OData API (natively supported in RunMyProcess) for Epicor Kinetic. By pairing RunMyProcess with CData Connect AI, you get true cloud-to-cloud connectivity to all your SaaS and cloud-based Big Data and NoSQL sources - no need to migrate your data or write your own integrations. Simply connect to Connect AI from RunMyProcess as you would any other REST service and get instant, live access to your Epicor Kinetic data.

In this article, we walk through connecting to Epicor Kinetic from CData Connect AI and accessing Epicor Kinetic data through an OData feed in RunMyProcess.

Connect to Epicor Kinetic from RunMyProcess

To work with live Epicor Kinetic data in RunMyProcess, we need to connect to Epicor Kinetic from Connect AI, provide user access to the connection, and create a Workspace for the Epicor Kinetic data.

Connect to Epicor Kinetic from Connect AI

CData Connect AI uses a straightforward, point-and-click interface to connect to data sources.

1. Log into Connect AI, click Sources, and then click Add Connection
👁 Adding a Connection

2. Select "Epicor Kinetic" from the Add Connection panel
👁 Selecting a data source

3. Enter the necessary authentication properties to connect to Epicor Kinetic.

   To successfully connect to your ERP instance, you must specify the following connection properties:

   • Url:the URL of the server hosting your ERP instance. For example, https://myserver.EpicorSaaS.com
   • ERPInstance: the name of your ERP instance.
   • User: the username of your account.
   • Password: the password of your account.
   • Service: the service you want to retrieve data from. For example, BaqSvc.

   In addition, you may also set the optional connection properties:

   • ApiKey: An optional key that may be required for connection to some services depending on your account configuration.
   • ApiVersion: Defaults to v1. May be set to v2 to use the newer Epicor API.
   • Company: Required if you set the ApiVersion to v2.
   👁 Configuring a connection (Salesforce is shown)
   
4. Click Save & Test
5. Navigate to the Permissions tab in the Add Epicor Kinetic Connection page and update the User-based permissions. 👁 Updating permissions
   

Add a Personal Access Token

When connecting to Connect AI through the REST API, the OData API, or the Virtual SQL Server, a Personal Access Token (PAT) is used to authenticate the connection to Connect AI. It is best practice to create a separate PAT for each service to maintain granularity of access.

1. Click on the Gear icon () at the top right of the Connect AI app to open the settings page.
2. On the Settings page, go to the Access Tokens section and click Create PAT.
3. Give the PAT a name and click Create. 👁 Creating a new PAT
   
4. The personal access token is only visible at creation, so be sure to copy it and store it securely for future use.

Configure Epicor Kinetic Endpoints for RunMyProcess

After connecting to Epicor Kinetic, create a workspace for your desired table(s).

1. Navigate to the Workspaces page and click Add to create a new Workspace (or select an existing workspace). 👁 The Workspaces page.
   👁 Adding a new Workspace.
   
2. Click Add to add new assets to the Workspace.
3. Select the Epicor Kinetic connection (e.g. EpicorERP1) and click Next. 👁 Selecting an Asset (Salesforce is shown).
   
4. Select the table(s) you wish to work with and click Confirm. 👁 Selecting Tables (Salesforce is shown).
   
5. Make note of the OData Service URL for your workspace, e.g. https://cloud.cdata.com/api/odata/{workspace_name}

With the connection, PAT, and Workspace configured, you are ready to connect to Epicor Kinetic data from RunMyProcess.

Retrieve Epicor Kinetic Data from RunMyProcess DigitalSuite Studio

With the connection to Epicor Kinetic and OData endpoints created, we are ready to add Epicor Kinetic data to RunMyProcess for Retrieval.

Create a Provider

1. Log into RunMyProcess and open DigitalSuite Studio.
2. Click Resources to bring up the Resources page, then select then the CONNECTORS tab. 👁 Connectors page
   
3. Click the + (New Provider) button to create a new provider, choose the account to use, then click Confirm. 👁 Create a new provider
   
4. In the provider settings page, configure the following properties.
   • URL: Set the OData endpoint in the Connect AI OData page: https://cloud.cdata.com/api/odata/{workspace_name}.
   • Authentication Schema: Select Login/Password.
   • Login: Specify a CData Connect AI username (e.g. [email protected]).
   • Password: Specify the PAT of the Connect AI user.
   👁 Selecting a connector
   
5. Fill in the same properties in the ACCEPTANCE and TEST tabs. Note: You can copy the configured settings by clicking 'Copy this configuration button,' then pasting the content in the new tab by clicking 'Paste previously copied configuration.'
6. Click Save to save the properties.

Retrieve Epicor Kinetic Data by Creating a Connector

1. In the CONNECTORS tab, click the button with three dots to create the provider, then select Add connector from the menu.
2. In the following page, set Connector URL to the OData endpoint configured in Connect AI (e.g. https://cloud.cdata.com/api/odata/{workspace_name}) 👁 Connector settings page
   
3. Click Save then Launch to test the connector execution. Click Launch test to execute. The process is successful if you get the JSON response of your configured table information. 👁 Execution test page
   

More Information & Free Trial

Now, you have created a provider and connector to retrieve Epicor Kinetic data. For more information on creating OData feeds from Epicor Kinetic (and more than 100 other data sources), visit the Connect AI page. Sign up for a free trial and start working with live Epicor Kinetic data in RunMyProcess.