Version 3.8
Salesforce Version
Version 3.8
Production Date
11/24/2015
Supported Browsers
Java Settings
Java 7.0
Screen Resolution
1024 x 768 or higher
Salesforce Connector UX Enhancements (SFDCDEV-162)
Several screens within Aria for Salesforce have been redesigned to improve the user experience.
Getting Here: Select an account > select an opportunity
Changes to the Account Plans screen, shown below, include the following:
Getting Here: Select an account > Select an opportunity > Add/Modify Plans
Changes to the Add/Modify Plans screen within an opportunity, shown below, include the following:
A custom section has been added to the Add/Modify plans screen. This section contains client-configured fields that can run custom Javascript. You can add up to 20 of these sections to the Add/Modify Plans screen.
Setting Up A Custom Section
Getting Here: Click + > Aria General Configuration > Custom Section
You can create a new custom section or edit an existing one from this screen. The screen below shows a populated custom section called "Greeting". To create a new custom section, enter a value in the Section Name field that is not assigned to an existing custom section. The fields in the section are as follows:
Viewing A Custom Section
Getting Here: Select an account > Select an opportunity > Add/Modify Plans
The following screen shows the "Greeting" custom section on the Add/Modify Plans screen after it has been configured as shown above.
This feature allows users to control the Suppress flag used by Aria for Salesforce to avoid callouts to Aria. Aria for Salesforce uses a Suppress flag in Apex code to suppress contact update callouts to Aria when updating contacts on billing group, payment methods and accounts internally. Previously, a custom client application trying to update a contact when creating a billing group or payment method using Aria for Salesforce did not see the contact update going to Aria. This was because the connector suppresses the contact callout during internal updates. To address this issue, this feature exposes the Suppress flag to client applications so they can control the Suppress flag in their customizations. This allows their application to leverage the Aria for Salesforce callouts to Aria during overlapping updates.
The following customization information allows you to link contacts to a billing group or payment method outside Aria for Salesforce, during creation of billing groups and payment methods by Aria for Salesforce.
The ASF3.AriaGlobalOperationResource class has the following static method to set the Suppress flag to true or false.
For the statement contact update callout, use the setSuppressStatementContactUpdateCallout(boolean) method as shown in the following example:
public Class checkRecursive
{ public static boolean isFirstRun = true; }
trigger TestStatementCon on ASF3_Aria_Billing_Group_c (after insert, after update) { String actId; if(checkRecursive.isFirstRun == false )
{ return; }
checkRecursive.isFirstRun = false; for (ASF3_Aria_Billing_Group_c abg : Trigger.new)
{ actId = abg.ASF3__Account__c; }
List<Account> ac = [select ASF3__Aria_Account_Contact__c from Account where id =: actId]; ASF3_Aria_Billing_Group_c abg = Trigger.New[0]; ASF3_Aria_Billing_Groupc billingGrp = new ASF3Aria_Billing_Group_c (id=abg.Id); billingGrp.ASF3_Statement_Contactc = ac[0].ASF3Aria_Account_Contact_c; ASF3.AriaGlobalOperationResource.setSuppressStatementContactUpdateCallout(false); update billingGrp; ASF3.AriaGlobalOperationResource.setSuppressStatementContactUpdateCallout(true); }