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.13

Aria for Salesforce 3.13

This article applies to:Aria Crescendo

Release Information

Salesforce Version

Version 3.13

Production Date

4/7/2016

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

Display Bill_agreement_id in Salesforce UI (SFDCDEV-164)

This feature enhances Aria for Salesforce so it displays the full credit card token as a payment method when that has been entered as a payment method in the Aria UI. This feature also saves tokenized credit card information entered in Aria for Salesforce as a payment method within Aria. Tokenized credit card information is now searchable regardless of whether it is entered in the Aria UI or the Aria for Salesforce UI.

Custom object records are searchable in the Salesforce user interface only if the custom object is associated with a custom tab. Users are not required to add the tab for display. To search Payment Method by Token Number using Salesforce "global search", you must create a tab for the "Aria Payment Method" object, even if you do not display the tab in the UI.


Additional Field Support (SFDCDEV-193)

This feature enhances Aria for Salesforce by adding the following fields.

Balance Due

The Balance Due field now displays for accounts in Salesforce.

Getting Here: Select an account > Aria Invoices

or

Select an account > Aria Invoices > Select an invoice

Transaction Fields

The following fields are available:

  • Start Balance
  • Charge Amount
  • Ending Balance
  • Credit Reason Description

Getting Here: Select an account > Aria Transactions

or

Select an account > Aria Transactions > Select a transaction

Applied Amount

Getting Here: Select an account > Aria Payments


Renaming Aria Supplemental Fields in Salesforce (SFDCDEV-195)

This enhancement renames Aria supplemental fields when used in Salesforce. For an Aria field field_name, the following conventions apply.

Form_input_type Datatype Salesforce Field Name
text/textarea string t_s_field_name
text date t_d_field_name
text number t_n_field_name
checkbox string c_s_field_name
radio string r_s_field_name
select string s_s_field_name

The following rules also apply:

  • Special characters are replaced with "_".
  • Spaces are replaced with "_".
  • Consecutive spaces or a consecutive special character and a space are replaced with one "_".
  • The first 35 characters are read from the Aria Field Name and are prefixed as indicated in the above table.
  • The label name exactly matches the Aria field name for the first 40 characters.

Plan Catalog Supplemental Fields Enhancement (SFDCDEV-196)

This feature enhances the creation of plan catalog supplemental fields so they are created on client plans only, and not on account plans in Aria for Salesforce.


Aria for Salesforce Fixes

  • Plan instance values saved in the Plan Selection and Configuration section of the Add/Modify page in Salesforce were not synced to Aria. (TICKET-187)
  • Opportunity Amount/Opportunity Calculations did not update (TICKET-359)
  • Search functionality and pagination was not available on the Swap Plans pop-up (TICKET-412)
  • Error message was displayed while committing the account (TICKET-420)
  • Custom rate schedule on opportunity displayed as a standard rate schedule (TICKET-423)
  • After editing selected plans, the following error displayed: 'Attempt to de-reference a null object' (TICKET-424)
  • On the Swap Plans pop-up, fewer plans displayed than were listed in the pagination (TICKET-425)
  • Swap Plans Commit: Unexpected error message displayed after committing swapped plans (TICKET-426)
  • B2C accounts could still be updated from Aria for Salesforce after turning off "sync account update" custom setting (TICKET-429)
  • Could not terminate the last plan assigned to a customer (TICKET-430)
  • Could not assign custom permissions to plan instance supplemental fields (TICKET-431)
You must to post a comment.
Last modified
13:51, 6 Apr 2016

Tags

This page has no custom tags.

Classifications

This page has no classifications.