Version 3.16
Salesforce Version
Version 3.16
Production Date
6/22/2015
Supported Browsers
Screen Resolution
1024 x 768 or higher
Support for Parent and Child Account Relationships (SDFCDEV-200)
Parent and child relationships for accounts can be used to indicate an account responsible for payment that is different than the account receiving the service. This aligns with current functionality available in Aria.
Getting Here: Select an account > Select an opportunity > Add/Modify Plans > Plan Selection and Configuration
Note: If you do not see the Edit button, you do not have a plan assigned to the opportunity. Refer to Add or Modify Plans to add a plan to the opportunity.
Select Configure from the Action drop-down.
This feature implements the update_acct_plan_multi_m API for Aria for Salesforce. This API updates plan billing and proration information for all plans within a single opportunity. Prior to implementing this API, Aria for Salesforce used a single API call for each plan assignment, replacement, update and cancellation. The update_acct_plan_multi_m API significantly improves performance and response time of Aria for Salesforce.
Getting Here: Payments and Credits tab > Payments
An electronic payment was unable to be made against a current payment method due to an issue that disabled payment methods related to credit card and ACH from being displayed in the drop-down. The drop-down was enabled to select the payment and now shows all payment types.
Previously, Aria APIs did not support special characters in phone numbers. As a workaround, Aria for Salesforce was sending the phone number after removing all the formatting. The API issue was resolved, and the workaround was no longer needed. Aria for Salesforce has been updated to send formatted phone numbers to Aria in all API calls.
During an account update, in cases where the account contact was the same as the statement contact, the account contact in Aria for Salesforce was replaced with outdated contact information. The functionality of the contact update has been modified and this issue has been resolved.
When an account or a contact was updated in Salesforce, redundant batch apex jobs were created in Salesforce due to the AriaRefeshTransactioncallout parameter. The trigger for running future job AriaRefeshTransactioncallout has been updated, and redundant batch jobs no longer occur during contact or account updates.