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

Aria for Salesforce 3.17

Table of contents
  1. Release Information
  2. Aria for Salesforce System Requirements
  3. Aria for Salesforce Features
    1. Record Payment at Invoice Level (SFDCDEV-203)
      1. Record Payment Received
    2. Client-defined User Redirect Destination When Committing Opportunities (SFDCDEV-204)
      1. Configure Redirect URLs for Organization After Opportunity Commit
      2. Configure Redirect URLs for User and/or Profiles After Opportunity Commit
    3. View and Edit Sequential Functional Groups (SFDCDEV-205)
      1. Sync the functional group ID values
      2. Set sequential functional group on account creation
      3. Update sequential functional group on an existing account
    4. Align Billing Dates to Specified Date or Another Master Plan Instance (SFDCDEV-206)
    5. API Changes Implemented to Handle Salesforce Platform Heap Size Limit (SFDCDEV-207)
    6. User Interface Enhancements (SFDCDEV-208)
      1. Account Page in the Account Plans Section
      2. Disable the “New Account Billing” pop-up
      3. Sync Account Tax Exemption Level and Tax Payer ID
      4. Update Billing/Statement Contact Information In the Billing Groups Module
      5. Selected Plans on the Opportunity Page are Sorted by Status and Alphabetical Order
      6. Amount Summary Displayed Includes Time Period
      7. User is Routed to the Selected Plans Screen after Adding Plans
      8. Capability to Work with Opportunities in the Scope of a Single Billing Group
    7. Response of the Programmatic Commit Returns List Success/Failure Messages (SFDCDEV-209)
      1. Example: 
  4. Aria for Salesforce Fixes
    1. Plan selection screen in the Aria General Configurations returned maximum view state size limit (TICKET-519)
    2. The field lengths of account plan and client plan supplemental fields were reset to 2000 (TICKET-513)
    3. Previous master plan section on account plan viewer was not showing any plans (TICKET-505)
    4. ARR Total on account plan viewer was not showing values (TICKET-504)
    5. Subscription temporary status help text removed (TICKET-502)
    6. List price and net price was the total of “List price x no. of units” (TICKET-492)
This article applies to:Aria Crescendo

Release Information

Salesforce Version

Version 3.17

Production Date

8/24/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


Record Payment at Invoice Level (SFDCDEV-203)

This feature allows you to manually record a payment at the invoice level. Previously, this feature was only available in the Collect Payment Electronically option under the Aria Payments and Credits page. 

The impact of this feature is on Record Payment Received option under the Aria Payments and Credits page.

Record Payment Received

Getting Here: Go to an existing account > Aria Payments and Credits button > Record Payment Received

Record payment at Invoice level 3.17.png

Note: Payments are recorded in the currency code on file for the account.

  1. Enter any applicable CSR comments in the CSR Comments field (optional).
  2. Enter a reference code that has not been previously used for the account in the Ref. Code field.
  3. Select one of the following options from the Payment Amount field:
  • Full Balance Due: Default option.
  • Other Amount: All invoices for the account are shown.
    • To select specific invoices to apply payment, populate the corresponding Amount to Pay fields.   
    • Otherwise enter the amount in the Other Amount field to apply the payment to the full balance.  

Other Amount OPtion 3.17.png

Note: The Other Amount textbox is disabled when a value is entered in an Amount to Pay field.

  1. Click Post Payment to review the payment information being submitted.
  2. Review the payment information being submitted.

Note: You can click Close to return to the Payments tab.

  1. Click Post Payment to submit the payment information. The payment history is displayed at the bottom of the screen.

Payment History 3.17.png


Client-defined User Redirect Destination When Committing Opportunities (SFDCDEV-204)

This feature introduces the ability of an administrator role to configure different redirect URLs (when committing opportunities) for various users/profiles. Previously, a user was automatically redirected to the opportunity detail page after commit. This feature enables integrated and natural work flows for users, reduces clicks and the risk of manual/user process errors.

These redirect URLs are configured in the Aria Hierarchy Custom Setting.  

  • If no redirect URL is configured for any user, profile, or organization, then the user is redirected to the opportunity detail page after commit.
  • If a redirect URL is only applied at the Default Organization Level, then this redirect is used as the default.
  • If a redirect URL is applied for a user or profile and also at the Default Organization Level, then the redirect URL for the user or profile takes precedence.

When the user is redirected, the opportunity ID is added to the configured URL as a parameter.

Configure Redirect URLs for Organization After Opportunity Commit

The instructions below describe how to set a new default redirect URL at the Default Organization Level. 

Note: A user must have administrator role to configure these URLs. 

Getting Here: Setup > Develop > Custom Settings > Aria Hierarchy Custom Setting

Aria Hierarchy Custom Settings 3.17.png

  1. Click Manage. The custom settings for the organization display.  
  1. Click New

Default Organization Level 3.17.png

Note: If a redirect URL has already been configured for the organization, an Edit button displays next to the New button.  Click Edit if you want to edit the redirect URL, and follow the steps below. 

  1. Enter a redirect URL. URLs are configured using Salesforce merge fields (e.g.  /apex/configureServiceDelivery?id={!opportunity.opportunityid})

Enter URL Organization Level 3.17.png

  1. Click Save. A confirmation page displays. The redirect URL specified is now the default for the organization. 

Configure Redirect URLs for User and/or Profiles After Opportunity Commit

Getting Here: Setup > Develop > Custom Settings > Aria Hierarchy Custom Setting

Aria Hierarchy Custom Settings 3.17.png

  1. Click Manage. The custom settings for the organization display.  
  2. Click New.

New User or Profile URL 3.17.png

Note: If user and/or profile redirect URLs have already been assigned, these records display with the option to View, Edit, or Delete.  To edit, click Edit and follow the steps below. 

  1. Select User or Profile from the Location drop-down. 
  2. In the adjacent field, enter the User name or the Profile name. 
  3. Enter the redirect URL. URLs are configured using Salesforce merge fields (e.g.  /apex/configureServiceDelivery?id={!opportunity.opportunityid})
  4. Click Save. Whenever a user or a user with this profile commits an opportunity, they are directed to the redirect URL specified. 
  5. The assigned redirect URL for the organization, user, and/or profile displays on Aria Hierarchy Custom Setting page. 

Company and Profile Redirects 3.17.png


View and Edit Sequential Functional Groups (SFDCDEV-205)

This feature adds the ability to set the <client_seq_func_group_id> when creating accounts via an opportunity in the Aria for Salesforce user interface. The <client_seq_func_id> is the functional account group number specifically designated for statement sequence number assignment. This parameter is configured when creating an account under the Aria Account Functional Group drop-down. 

You can now sync sequence groups from Aria to Aria for Salesforce during client plan sync and add/view/edit the sequence groups on accounts in Aria for Salesforce. When an account is created, this value is passed to Aria during commit. In an existing account, the user can view the sequence group and update it. 

This feature ensures that statement numbers are generated correctly even for statements/invoices generated directly by the creation of the account.

Sync the functional group ID values

This step only needs to be performed once to sync the values and does not need to be done for each account.

  1. Go to Aria Systems App.
  2. Select the Client Plans tab.
  3. Click Refresh Client Plans from Aria.

Set sequential functional group on account creation

  1. Create a new account in Salesforce.
  2. Select the Aria Account Functional Group on the account page.

Aria Account Functionla Group UI 3.17.png

  1. Click Save. 
  2. Create an opportunity
  3. Add/Modify Plans for the opportunity. 
  4. Commit opportunity.  The account is created in Aria with the Aria Account Functional Group value as defined in Salesforce and can be invoiced.

Update sequential functional group on an existing account

  1. Go to an Account Detail page.
  2. Click the pencil icon next to the Aria Account Functional Group.  The field displays a drop-down. 

Edit Functional Group 3.17.png

  1. Select the updated Aria Account Functional Group
  2. Click Save. The group ID is saved and updated to Aria in real time.

Align Billing Dates to Specified Date or Another Master Plan Instance (SFDCDEV-206)

Aria for Salesforce now supports aligning the billing dates of newly added plans to a date specified or to another master plan. You can specify an Override Bill Through Date (the date through which services and usage are billed) when adding plans to an opportunity.

Getting Here: Go to an Opportunity > Add/Modify Plans > Plan Selection and Configuration > Add a new plan

Override Bill Through Date.png

Note:  If an Override Bill Through Date is defined, the system defaults to prorated invoicing.

The Override Bill Through Date drop-down contains:

  • Sync Master Plan Instance: This option aligns the bill through dates for the new plan being assigned with the bill through dates of an existing master plan instance. Choose the existing master plan instance from the Master Plan Instance drop-down. 

Note: The option to sync with a master plan instance is only shown if a master plan for the account has already been committed to Aria. 

Bill Date as MPI 3.17.png

  • Use Bill Through Date: The date specified in the Bill through Date field is used as the bill through date for the new plan being assigned to the account.

Use Override Bill Through DAte 3.17.png


API Changes Implemented to Handle Salesforce Platform Heap Size Limit (SFDCDEV-207)

Changes the get_client_plans_all_m and the get_acct_plans_all_m core APIs have been made in the 6.49 Release (DEV-7149) to lessen the data load when retrieving product catalogs from Aria. Aria for Salesforce has been re-factored to accommodate these API changes.

This enhancement allows you to sync plans having more that 200 children plans and other use cases without hitting the heap size limit. Refer to API Updates to Accommodate Aria for Salesforce Heap Size Limit (DEV-7149) in the Aria 6.49 Release for more specific information.  


User Interface Enhancements (SFDCDEV-208)

User interface enhancements have been made to the following pages: 

Account Page in the Account Plans Section

Getting Here: Go to an Account > Scroll to Account Plans

Account Plans Missing Coupons 3.17.png

1.png The Next Statement link generates a preview of the next invoice.
2.png Total row that summarize the monetary values by column.  The total that shows is based on the selected billing group.

On the Previous Master Plans tab, a new column displays the Termination Date.

Terminate Plan 3.17.png

Disable the “New Account Billing” pop-up

Note:  You need an administrator role to disable or enable the billing group pop-up.

  1. Select the Aria Systems app.
  2. Select the Aria General Configurations tab. 
  3. Select Other Configs.
  4. In the Account Section, check Disable New Account Billing Popup for Add/Modify Plans.

Disable Billing Group 3.17.png

  1.  Click Save Settings. The New Account Billing popup is not displayed when a user selects Add/Modify Plans.

Sync Account Tax Exemption Level and Tax Payer ID

Getting Here: Go to an Account > Scroll to Aria Fields

Update tax ID 3.17.png

  1. Update the following fields: 
  • Aria Tax Payer ID (optional)
  • Exempt from State/Province Taxes
  • Exempt from Federal/National Taxes
  1. Click Save. Fields are synced to Aria.  These fields are also synced from Aria to Salesforce during an Aria to Salesforce account sync.

Update Billing/Statement Contact Information In the Billing Groups Module

Getting Here: Select an Account > Select an Opportunity > Add/Modify Plans > Billing Group module

From the Billing Group module, you can now update contact information by clicking the adjacent Edit link. 

Edit Contact Info 3.17.png

  1. Click Edit. A new tab opens with the contact information. 

Edit Contact Pop up 3.17.png

  1. Click either the top or the bottom Edit button. 
  2. Update contact information fields. 
  3. Click Save. 

Note: Changes to the contact are not available on the Billing group screen until the billing group screen is refreshed.

Selected Plans on the Opportunity Page are Sorted by Status and Alphabetical Order

Getting Here: Select an Account > Select an Opportunity > Add/Modify Plans button > Plan Selection and Configuration module

  1. Click +Add.
  2. Select plans to add to the opportunity.
  3. Click Add. The selected plans display. This table is sorted by plan status (new first and then existing status) and for each plan status, the plans are sorted alphabetically by plan name.

Plan Status Ordering 3.17.png

Amount Summary Displayed Includes Time Period

For all modules that display the account summary in the upper right-hand corner, the time period for which the summary applies is displayed. 

Pricing Structure 3.17.png

The following abbreviations apply:

  • Semi-Annual = SA
  • Annual = YR
  • Quarterly = QTR
  • Monthly = MO

Note: These values can be translated. 

User is Routed to the Selected Plans Screen after Adding Plans

Previously the user was redirected to the Overview page from the Add/Modify Plans page.

Capability to Work with Opportunities in the Scope of a Single Billing Group

When creating a new opportunity, you can view which plans belong to a billing group. When working with an existing opportunity, you can select the billing group to work with.

Getting Here: Select an Account > Create an Opportunity > Add/Modify Plans button

When you first click Add/Modify Plans after creating an Opportunity, a screen displays with a dropdown selector that displays billing groups. You may choose to work within only one billing group by only selecting plans within that billing group.  If you want to work with multiple billing groups, choose plans from more than one billing group by selecting the other billing group(s) from the drop-down. 

Note: If there is only one billing group available, the billing group displays as text only and you do not see the dropdown.

Select Billing Group Start 3.17.png

After you have selected the plans and billing groups, click Next and proceed with Add/Modifying Plans.  

When you return to the Billing Group module, the billing group information displayed depends on if you have more than one billing group assigned to the opportunity.

Getting Here: Select an Account > Select an Opportunity > Add/Modify Plans button > Billing Group module

If you have more than one billing group, the Select Billing Group dropdown displays. 

Select Billing Group Displayed 3.17.png

If you have selected plans from only one billing group, the Select Billing Group dropdown does not display. 

Billing Group Create New Link 3.17.png


Response of the Programmatic Commit Returns List Success/Failure Messages (SFDCDEV-209)

The programmatic commit has been enhanced to return a list of key value pairs indicating the success or failure of each API call. The key value pairs have the error code and the error message for each API used in the programmatic commit. An error code of "0" indicates success.

Example: 

List at index 0: error_code - "0", error_message - "create_acct_complete_m" successful with error message "..."
List at index 1: error_code - "12123", error_message - "create_order_m" failed with error message "..."


Aria for Salesforce Fixes

Plan selection screen in the Aria General Configurations returned maximum view state size limit (TICKET-519)

The Plan Selection screen in the Aria General Configurations was returning a maximum view state size limit.

A heap size error was occurring because of multiple visual force components displaying the data in different tabs. This caused large amounts of data to load simultaneously.  

To prevent this issue, the visual force components have been removed from Aria General Configurations, and the Plan Selection and Tax Percentage pages are only called when a user clicks on the respective tab. 

The field lengths of account plan and client plan supplemental fields were reset to 2000 (TICKET-513)

The length of plan supplemental fields were reset to the default length (2000) even after the fields had been created, because the metadata update call was sending the textarea length. The text area length has been removed from the metadata update call. 

Previous master plan section on account plan viewer was not showing any plans (TICKET-505)

The Previous Master Plan section on Account Plan Viewer was not showing previous plans. The query was fetching only Terminated plans, and not Cancelled plans. The query has been updated to fetch Cancelled plans.  

ARR Total on account plan viewer was not showing values (TICKET-504)

When the Total ARR field was added to the Account Plan Viewer via the field set, no values were shown in the Viewer. The SOQL was copying the column name twice, thus the query was failing and not displaying the plans.  The logic for the SOQL has been updated to remove the duplicate entry.

Subscription temporary status help text removed (TICKET-502)

The tooltip for Subscription Temporary Status was not correct and has been removed. 

List price and net price was the total of “List price x no. of units” (TICKET-492)

The List price and net price was the total of “List price x no. of units” rather than per unit. The calculation has been updated and the net and list price calculate based on the number of units assigned to plan. 

You must to post a comment.
Last modified
18:54, 24 Aug 2016

Tags

Classifications

This page has no classifications.