Search the Aria Knowledgebase for
User Documentation, APIs, SDKs, and more!

 

Home > Aria Crescendo Documentation > Aria for Salesforce 3 Release Notes > Aria for Salesforce 3.16

Aria for Salesforce 3.16

This article applies to:Aria Crescendo

Release Information

Salesforce Version

Version 3.16

Production Date

6/22/2015

Aria for Salesforce System Requirements

Supported Browsers

  • Chrome, most recent stable version
  • Firefox, most recent stable version
  • Internet Explorer 9, 10, 11
  • Safari 5, 6, 7 on OS X

Screen Resolution

1024 x 768 or higher

Aria for Salesforce Features

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

  1. Click Edit. The Plans screen displays. 

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. 

  1. Select Configure from the Action drop-down.

Configure 3.16.png

  1. Scroll to the Parent Plan Relationship section. 

Parent PLan Selection 3.16.png

  1. Specify a Parent Account by typing in the name, or by clicking the magnifying glass icon and searching. 
  2. Once a Parent Account is defined, the plan that is being configured is designated as a child plan and the Billing Responsibility drop-down displays. 

Billing Responsibility 3.16.png

  1. Select from the following options: 
  • Standard Self-Pay: The Child account is responsible for payment. 
  • Parent Pay: The Parent Account specified is responsible for payment. If usage applies to the account, the child plan is responsible for the usage costs.
  • Parent Usage & Pay: The Parent Account specified is responsible for payment, including any usage costs. 
  1. Click Done.  The Parent plan has been linked to the plan, and the relationship for payment has been specified.  

New update_acct_plan_multi_m API to update plans of billing groups in a single API call (SFDCDEV-198)

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. 

Aria for Salesforce Fixes

Electronic payments methods were not displaying in drop-down (TICKET-491)

Getting HerePayments 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.

Phone format was removed during contact sync (TICKET-494)

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.

Account contact updated in Aria for Salesforce was overridden by old account information in Aria (TICKET-500)

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. 

Contact and account updates were creating redundant future job Aria Refresh transactions (TICKET-501)

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. 

 

 

You must to post a comment.
Last modified
15:01, 22 Jun 2016

Tags

This page has no custom tags.

Classifications

This page has no classifications.