Home > Aria6 User Documentation > Aria for Salesforce Release Notes Archive > Aria Salesforce Connector 1.0 Release 1.15

Aria Salesforce Connector 1.0 Release 1.15

Release Information

Salesforce Version

Connector 1.0

Production Date

11/6//2015

Aria for Salesforce System Requirements

Supported Browsers

  • Internet Explorer 9, 10, 11
  • Firefox 31
  • Chrome 36

Java Settings

Java 7.0

Screen Resolution

1024 x 768 or higher

Aria for Salesforce Features

Support for Two-Way SSL from Aria for Salesforce (SFDCDEV-112)

This feature adds support of SSL certificates to Aria for Salesforce. Before adding a certificate, you must first install it in Salesforce using Salesforce's Certificate and Key Management function.

Configuration within Aria for Salesforce

To add an SSL certificate to Aria for Salesforce, use the following steps.

Getting Here: Click All Tabs (+) > Aria General Configuration > SSL Config

  1. Specify the name of the certificate. The SSL certificate name is the “unique name” that was provided while creating the certificate in “Certificate and Key management”."
  2. Click Save Settings.

Note: This is not the same as the CN name.

SSLConfig2.png

  1. Click All Tabs (+) > Aria General Configuration > Aria API Configurations. The Aria API Configuration screen displays

SSLConfig3.png

  1. Click Go to see a list of available API configurations. A list of API configurations displays.

Note: If the API configuration you wish to edit is visible, click Edit and skip the next step.

SSLConfig4.png

  1. Click Edit to modify the API configuration.
  2. Change the Aria Remote Site URL from https://secure . . . to https://api . . . 

SSLConfig5.png

  1. Click Save when you are finished. The certificate is added to Aria for Salesforce.

Configuration Within Aria

After configuring the certificate in Aria for Salesforce, use the following steps to upload them to Aria.

  1. Log in to Aria.
  2. Click Configuration > Integrations > SSL Certificates > New. The Create New SSL Certificate screen displays.

SSLCert1.png

  1. Enter the URL and select the .crt file you wish to upload. You do not need to enter an expiration date, as that is obtained automatically from the certificate. Leave the Status set to Active.
  2. You can optionally enter a description.
  3. Click Save. The certificate is uploaded to Aria.

Note that for publicly signed certificates, you normally get three or more certificates and you may have to upload all of them. As an example, you might need to upload all of the following:

  • Domain certificate, for example.www_aria_com.crt
  • Intermediate certificate for example, DigicertCA.crt
  • Root Certificate for example, TrustedRoot.crt
  1. Next you must turn on 2-way SSL authentication. Click Configuration > Client Settings > Miscellaneous Settings and scroll to Use SSL Authentication.

SSLCert2.png

  1. Select Use SSL Authentication. The Use SSL Authentication screen opens.
  1. Change Value to True and click Save. SSL authentication is now active for your Aria instance.

 SSLCert3.png

If the Use SSL Authentication setting is True, and an incorrect certificate or no certificate is configured in Salesforce, then calls from Salesforce to Aria, for example, to create an account, or any API call, fail. Failure messages, like authentication errors  are logged in Salesforce in the custom object “AriaErrorLog”.

Prevent Duplicate Opportunity on Refresh from Aria (SFDCDEV-64)

This feature removes the duplicate opportunity that Aria for Salesforce creates when refreshing an opportunity from Aria6.

Previously, when an account was synced from Aria, Aria for Salesforce created an opportunity to determine if there was a mismatch of account data between Aria for Salesforce and Aria6. If there was no mismatch, Aria for Salesforce deleted the newly created opportunity. However, if a user performing a refresh/sync did not have permission to delete an opportunity in Aria for Salesforce, the opportunity that should have been deleted remained in Aria for Salesforce as a duplicate opportunity.

This feature addresses this issue by holding the opportunity in memory instead of creating it, and, even if the user doing the refresh from Aria6 does not have permission to delete the opportunity, the opportunity used for determining the mismatch does not remain in Aria for Salesforce if there is no mismatch.

Last modified

Tags

This page has no custom tags.

Classifications

This page has no classifications.
Powered by MindTouch ®