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

 

Home > User Documentation > Aria for Salesforce Release Notes > Aria Salesforce Connector 1.0 Release 1.11

Aria Salesforce Connector 1.0 Release 1.11

Release Information

Salesforce Version

Connector 1.0

Production Date

9/12/2014

Aria SFDC System Requirements

Supported Browsers

  • Internet Explorer 9, 10, 11
  • Firefox 31
  • Chrome 36

Java Settings

Java 7.0

Screen Resolution

1024 x 768 or higher

Aria SFDC Features

SFDCDEV-40    Order Pending (Not Billed) Until Confirmed Via SFDC

Currently, the SFDC connector allows a one-time order to be created with the status “Order Billed” (to bill immediately) or “Order Filled” (to bill on anniversary). This functionality has been enhanced to allow users to create a one-time order in a Pending state, indicated by an “Order Held” status, which is not billed, and can later be updated to a status of “Order billed,” “Order Filled,” or “Order Cancelled”

Order Syncing

For an account in SFDC that also exists as an account in Aria – If an order is created in Aria in a pending state (status “Order Held”), and if Aria triggers event notifications for “Order Held,” then these orders created in Aria will sync to SFDC in real time via the Aria event notification. If Aria does not support event notifications for the “Order Held” status, then the order will not flow to SFDC in real time.

For an account in SFDC that exists as an account in Aria – If the orders on the account in Aria are updated from “Order Held” to “Order Billed,” “Order Filled,” or “Order Cancelled,” these orders will sync in real time from Aria to SFDC via order event notifications.

For an account in SFDC that exists as an account in Aria – One-time orders on the account in Aria with a status of “Order Held” will sync to SFDC via the SFDC Apex scheduled batch job “AriaBatchAccountPlansUpdaterScheduler”.

Aria SFDC Fixes

SFDCQA-190    MRR Incorrect – Unit Pricing Not Calculated Correctly

Previously, the MRR total was considering the units for service type as “recurring". This meant that the unit price was not calculated correctly for recurring service having one rate tier with a Flat Rate tiered pricing rule. For example, a service with a Flat Rate per tier price of $50.00 with 3 units was calculating an MRR total of $150.00 ($50.00 x 3 units). Instead, the Flat Rate tiered pricing rule indicates that the MRR should be the price for that rate tier, meaning the MRR should be $50.00.

To correct this issue, the logic has been modified to only multiply the Flat Rate per tier with one unit, so the MRR is always accurate.

You must to post a comment.
Last modified
20:39, 20 Jul 2015

Tags

This page has no custom tags.

Classifications

This page has no classifications.