Application configuration is an integral activity prior to the process of integration. If your chosen application is Salesforce, credentials need to be provided for validating the agent. Here you will find the detailed description on how to configure the agents for the application of Salesforce, Troubleshooting issues and the attributes and action.
Salesforce is a REST Application which supports OAUTH 2.0 authentication. The Adapter of the application Salesforce provides the leverage to communicate and adapt with the AEC Portal. This section provides you the detailed process of validating the credential of the application Salesforce.
Pre-requisites for Salesforce Configuration
- Valid APPSeCONNECT Portal credentials.
- Select the Application Salesforce in the APP section.
- Create connection for Salesforce.
- Publish any Touchpoint, Update Adapters and Update Configuration in the agent.
Configure the Agent
To Know about Agent Configuration, Click here
Configure the Salesforce Application in the Agent
- In the App Configuration panel of the agent, click on the + button, beside the app Salesforce.
- Click the + button, the credential panel opens for the application Salesforce.
- To Validate the adapter for Salesforce you will need the Consumer Secret and Consumer Key.
- To generate these credentials, login to the Salesforce Application. This will take you to the default home page.
- In the Home page of Salesforce, navigate to Setup Module.
- Click the Setup icon from the drop-down list.
- Navigate to Apps > App Manager. Now, you can view the APP Manager page.
- Click New Connected App button.
- Enter name of your application, API Name, Contact email information, as well as any other information appropriate for your application and click on the checkbox to enable the Oauth Settings.
- Enable the checkbox, enter the callback URL and select the OAuth scope as Full Access for complete access.
Note: User can select the desired scopes as these scopes refer to permissions given by the user running the connected app.
Note: Callback URL is the URL that a user browser is redirected to after successful authentication. As this URL is used for some OAuth flows to pass an access token, the URL must use secure HTTP (HTTPS) or a custom URI scheme.
Provide the details, click SAVE button. Now you will get the following window with the Consumer Key and Consumer Secret generated. To view the Consumer Secret, press
Click to Revealbutton. Note:It takes 15-20 mins to reflect the Oauth2.0 settings in the Salesforce portal. Once it reflects, you can copy the generated credentials for validation process.
- On the Profile icon, click settings button to generate the Security Token.
My Personal Informationdropdown, Click on Reset My Security Token.
Note: The Security Token would be sent to the Email that was provided while creating the Salesforce Account.
- Enter all the generated credentials in the OP Agent for the validation process. Click SAVE followed by the Validate Button.
Following this process, the Salesforce application can be configured in the agent.
ISSUE 1:Source Application Data Not Found
Source Application Data Not Found even if Data is present is the Source Application.
Some of the basic troubleshooting issue happens due to improper validations or even if it is accurately validated and if touchpoints do not sync. This basic issue resolves after removing the Temp and Cache files from the portal and from your system. Therefore, after clearing all this, you need to publish the touchpoints again along with Update Configuration on the agent.
For E.g. If the
Source Application Data Not Found in the log file appears, the probable cause is due to the presence of the Temp and Cache Files.
Note: Integration between SAP B1 and Salesforce requires UDT & UDF creations
Attributes and Actions
While defining a connect to an API endpoint in Salesforce, you require clear understanding about the data requirements and endpoint configurations. You can refer to this document to find all the endpoint details of your Salesforce installation. To define the endpoint in APPSeCONNECT, you need to define Actions and Entities. Actions are specifically targeted for an endpoint while schema is the data needed to execute the API. Here is the list of some of the pre-packaged API actions defined for you which you can easily plug and play while doing your integration.
|Endpoint||Action||Action Type||Schema||UI Help||API Path|
|/query||/query||GET||Contact||Fetching Contacts from Salesforce and posting into Destination Application||API for fetching contacts from Salesforce|
|/query||/query||GET||order||Fetching sales orders from Salesforce and posting to destination application||API for fetching sales orders from Salesforce|
|/query||/query||GET||Accounts||Fetching customer Account from Salesforce and posting to destination application||API for fetching Accounts from Salesforce|
|POST||POST||Post||Product2||Posting product from source application to Salesforce||API for posting products to Salesforce|
|POST||POST||Post||Contact||Posting Contact from Source application to Salesforce||API for Posting Contacts to Salesforce|
|PATCH||PATCH||Patch||Account||Updating Accounts from Source Application to Salesforce||API for updating Accounts to Salesforce|