Home > Aria Crescendo Documentation > Aria for Salesforce 3 Release Notes Archive > Aria for Salesforce 3.22

Aria for Salesforce 3.22

Table of contents
  1. Release Information
    1. Salesforce Version
    2. Production Date
  2. Aria for Salesforce System Requirements
    1. Supported Browsers
    2. Screen Resolution
  3. Aria for Salesforce Features
    1. Support for Contacts That Do Not Use Email (SFDCDEV-237)
      1. Add the Dummy Email Address to Aria General Configurations
      2. Specify That a Contact Does Not Use Email
    2. Notification Message Added for Aria Account Plan Data Conflicts (SFDC-238)
    3. Assignment Scope Change Does Not Remove Plan Configurations (SFDCDEV-239)
    4. User Tracking Enabled for Create, Delete, or Update Record Events (SFDCDEV-240)
      1. View User ID and Related Information in Account's Recent Comments
      2. View User ID in Web Service API Calls Audit Log
    5. Enhancements to Credit Memo and Rebill Functionality (SFDCDEV-241)
      1. Display of Additional Information for Credit Memos 
      2. Set a Single Tax Address for Rebill Invoice Line Items
      3. Set Custom Permissions for Credit Memos and Rebills
  4. Aria for Salesforce Fixes
    1. Various fields for setting bill dates were able to configured globally (TICKET-621)
    2. Tax and net price tooltip was not displaying correctly (TICKET-652)
    3. One-time product lookup was not functioning prior to commit (TICKET-653)
    4. Supplemental fields were not updating to Aria (TICKET-707)
    5. Invalid error was occurring with provided primary payment method (TICKET-714)
    6. The Master Plan Instance name and Master Plan Instance ID was not displaying on credit memo line (TICKET-727)
    7. Reference on contract plan relationships for accounts was not correct (TICKET-730)
    8. Suspended plans were not displayed (TICKET-741)
    9. Alternate Billing Start Date was not syncing in Aria for master pan instance (TICKET-743)
    10. Retroactive billing start date was not saving in Aria (TICKET-744)
    11. Programmatic commits were failing without an error message (TICKET-756)
    12. Error occurred when selecting assignment scope (TICKET-758) 

Release Information

Salesforce Version

Version 3.22

Production Date

3/29/17

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 Contacts That Do Not Use Email (SFDCDEV-237)

Aria requires a statement contact’s email address to trigger the statement generation event. This feature provides a method for triggering the statement generation event for contacts who do not use email without syncing a dummy email to Salesforce.

To use this feature, a dummy email address is entered in the Aria General Configurations. Subsequently, when configuring a contact’s information, select the option to indicate that the contact does not use email. By selecting this option, when the contact syncs from Salesforce to Aria, the dummy email is populated as the contact's email in Aria. When syncing back from Aria to Salesforce, if the "do not use email" parameter is checked, the dummy email address does not sync. 

During syncs, the dummy email configured in Aria General Configurations is only migrated from Salesforce to Aria.

Add the Dummy Email Address to Aria General Configurations

Getting Here: Aria Systems App > Aria General Configurations tab > Other Configs

Dummy Email Config 3.22.png

  1. Enter the dummy email address in the Dummy Email field.
  2. Click Save. 

Specify That a Contact Does Not Use Email

The functionality to indicate that a contact does not use email is accessible through various locations in the interface. These include the Billing Groups Module, Account Overview screen, and the Contacts tab.

Billing Group Module

Getting Here: Navigate to an Opportunity > Add/Modify Plans button > Billing Groups module > Edit

billing contact check box 3.22.png

  1. Check the This Contact Does Not Use Email checkbox. 
  2. Click Save.
Account Overview Screen or the Contacts tab

Getting Here: Accounts tab > Select an account > Scroll to Account Contacts > Edit 

or

Getting Here: Contact tab > Select an account > Select a Contact 

Contact Edit Email 3.22.png

  1. Check the Do Not Use Email checkbox. 
  2. Click Save.

Notification Message Added for Aria Account Plan Data Conflicts (SFDC-238)

This features adds a notification message that the account plan or plan data of an opportunity is out of sync with the information saved in Aria. The pop-up also provides options for how to proceed.  

The message displays if a discrepancy is recognized:

When

 Options
Opening an existing opportunity

Open Opp Conflict 3 3.22.png

  • Cancel: Cancel the notification and continue working with the plan data in the opportunity. 
  • Sync Only: Refresh the account plans or plan data with the information in Salesforce. This updates the account plans or plan data to match what is in Salesforce.
Clicking Save after modifying plans in the Plan Configuration screen

Conflict messages plan 3.22.png

  • Save Without Syncing: Save the plan changes without syncing from Aria and continue working with the opportunity.
  • Sync: Refresh the account plans or plan data with the information in Salesforce. This updates the account plans or plan data to match what is in Salesforce.
Clicking Commit from the
Add/Modify Plans module

Conflict messages commit 3.22.png

  • Cancel: Cancel the notification and continue working with the plan data in the opportunity. 
  • Sync Only: Refresh the account plans and/or plan data from Aria which replaces the current plan data on the opportunity.
  • Commit With Sync: Sync the plans and save or commit the plan changes.

Assignment Scope Change Does Not Remove Plan Configurations (SFDCDEV-239)

This feature enhances the functionality of the Plan Configuration screen to prevent assignment scope changes from removing plan configurations. Previously, if plan configurations were made but not saved prior to assignment scope changes, the plan configurations were removed.  

User Tracking Enabled for Create, Delete, or Update Record Events (SFDCDEV-240)

This feature enables recording the user ID for create, delete or update record events performed in Aria for Salesforce. When a user generates an update to Aria, his or her user ID is now passed in the <alt_caller_id> parameter field of the associated API.

With this enhancement, the following fields are populated with Aria for Salesforce data for any API that posts data to Aria from Salesforce:  

  • <alt_caller_id>: First 30 characters of the Salesforce login ID of the user initiating the call
  • <application_id>: Populates with "Aria For Salesforce 3"
  • <application_date>: Date time value including the user's time zone. For example "2015-05-21 21:50:14 (PST)".

You can access this information in the account's recent comments or search for the associated API in the web service API calls audit log.

View User ID and Related Information in Account's Recent Comments

Getting Here: Search for an account > Account Overview tab > Recent Comments section

Recent Comments 3.22.png

View User ID in Web Service API Calls Audit Log

Refer to Web Service API Calls for more information performing a search in the audit logs. 

Getting Here: Click Configuration > Audit Logs > Web Service API > Perform search

audit log 3.22.png

Enhancements to Credit Memo and Rebill Functionality (SFDCDEV-241)

This feature enhances credit memo and rebill functionality adding:

  • Display of additional information for credit memos
  • Ability to use a single contact address for rebill invoice line items
  • Ability to set custom permissions pertaining to credit memos and rebills
  • User-friendly error messages when creating rebill invoices

For more information about credit memos or rebills, refer to Account Actions. 

Display of Additional Information for Credit Memos 

Getting Here: Aria Payments and Credits > Credit Memo tab

Existing Credit Memos 3.22.png

From the Credit Memos tab you can now:

  • View a list of existing credit memos
  • Access detailed information by clicking the Credit Memo Number
  • View net total and tax amounts by hovering over the information icon (clipboard_ead17c6a1ca09d564f9b2b76322390884.png)
  • Void the memo 

Set a Single Tax Address for Rebill Invoice Line Items

This functionality enables you to specify the same contact for each invoice line item in one step, rather than setting the tax address individually for each line item.  The contacts available to choose depend on the configuration of contacts in your Aria instance.  Refer to Account Contacts for more information on how to configure these in Aria.   

To set each tax address for invoice line items individually, refer to Create a Rebill.

Getting Here: Aria Payments and Credits > Rebills tab > Select an invoice > Create a Rebill button

Address for rebills 3.22.png

  1. Check Use Single Address for all Invoice Line Items. The text becomes a link.
  2. Click the link. The Edit Invoice Tax Address overlay displays.
  3. If there are no tax addresses configured, the following screen displays. You can click Save or Cancel.  No tax address is updated for the rebill. 

No address 3.22.png

If tax address(es) exist for the account, a screen displays with drop-downs to choose various contacts.  In the example below, Destination Contacts have been configured in Aria, and are available for selection: 

Destination contact 3.22.png

  1. Select the contact from the drop-down. 
  2. Click Save.  This contact is used for all invoice line items.

Set Custom Permissions for Credit Memos and Rebills

By default, all users can create, view and void credit memos and create and view rebills. Setting these custom permissions restricts access to only those permission sets specified. 

Getting Here: Aria Systems App > Aria General Configurations tab > Custom Permissions

Custom Permissions 3.22.png

  1. Click in the "Select Custom Permissions" field. The available permission sets display. 
  2. Select the profile to grant access.  
  3. Click Save.

Aria for Salesforce Fixes

Various fields for setting bill dates were able to configured globally (TICKET-621)

The fields for Alternate Bill Day, Alternate Billing Start Date and Retroactive Billing Start Date were displayed when when no plans were selected.  This has been corrected so that these fields only display when plans are selected.  

Tax and net price tooltip was not displaying correctly (TICKET-652)

The additional price information tooltip was not showing in the appropriate columns for ARR and Total Price in the Account Plan Viewer.  Updates have been made to the UI so that the tooltip displays where appropriate. 

One-time product lookup was not functioning prior to commit (TICKET-653)

The lookup for on-time product was displaying blank if the plan had not been committed.  Once committed, the lookup worked successfully.  This was due to the timing of the client plan stamp occurring during commit rather than creation.  This has been corrected so that the stamp occurs during creation and the lookup now returns values. 

Supplemental fields were not updating to Aria (TICKET-707)

Supplemental fields were not updating to Aria in some cases.  This issue was due to the <product_directive> attribute in the update_acct_plan_multi_m AP not being sent.  This has been updated and supplemental fields now update consistently.  

Invalid error was occurring with provided primary payment method (TICKET-714)

The provided primary payment method idx had an invalid error when the user's language was not English and the user had translated pick list values of payment method. The connector's logic checked some conditions based on the payment methods. So, when the user attempted to commit, an error displayed.The connector's logic has been updated to check the conditions based on picklist values, which are always in English. It is recommended to use the standard Salesforce feature of translation workbench to change the method picklist values rather than directly changing the picklist values to another language.  

The Master Plan Instance name and Master Plan Instance ID was not displaying on credit memo line (TICKET-727)

The Master Plan Instance name and Master Plan Instance ID was not displaying on credit memo line.  This has been updated and this information now displays.

Reference on contract plan relationships for accounts was not correct (TICKET-730)

The reference of account plans on the contract plan relationship records was not correct. It was referring to account plans rather than those plans available on current opportunity scope. The logic has been updated so that the related plans to the opportunity are now copied to the contract plan relationship records and validated. 

Suspended plans were not displayed (TICKET-741)

Plans with suspended status were not displayed. The code has been corrected to ensure proper checks of entire module to display plans on page. 

Alternate Billing Start Date was not syncing in Aria for master pan instance (TICKET-743)

The alternate billing start date was not stamped in Salesforce, and was not updated in Aria during sync.  This has been corrected and the alternate billing start date for master plan instances now updates in Aria during sync. 

Retroactive billing start date was not saving in Aria (TICKET-744)

The retroactive billing start date was not updating in Aria because it was not included in API parameters. The retroactive billing start date has now been mapped with API attributes.

Programmatic commits were failing without an error message (TICKET-756)

Programmatic opportunity commits were failing without an associated error message. This occurred in the case of a user cancelling all plans on the opportunity scope. Then the opportunity did not commit to Aria because canceled plans were not queried. The query has been modified and now returns all canceled plans. 

Error occurred when selecting assignment scope (TICKET-758) 

Some user's were receiving an error to select a future date when he or she did not select that value.  This error was occurring due to a conflct in the JavaScript functionality when a user had a different locale and the date time format was dd/mm/yyyy.  This has been corrected by converting the dates into the appropriate format (mm/dd/yyyy).

Last modified

Tags

This page has no custom tags.

Classifications

This page has no classifications.
Powered by CXone Expert ®