Overview
Enhancements and fixes to Aria functionality for this release are described below.
Overview
Enhancements and fixes to Aria functionality for this release are described below.
Release Date
1-October-2020
27-October-2020
1024 x 768 or higher
Aria Billing Cloud now provides additional unit instance payload data for the following events (under Configuration > Notification > Events > Accounts and Master Plan Instances Event Group):
The following payload field data has been added:
Master Plan Instance (MPI) unit instance data:
|
Supplemental Plan Instance (SPI) unit instance data:
|
These fields can be obtained by subscribing to your chosen event and selecting any method, including XML, name-value pair format, and Email message format payloads.
Provisioning Settings must also be configured as follows (from Configuration > Notifications > Provisioning Settings):
Event | Setting |
Provisioning Request Creation Status | True |
Provisioning Request Processing Status | Active |
In addition, the client parameter value for the PROV_ACCOUNT_MPI_CLASS_VERSION_M client setting must be 3.0. Please contact Aria Customer Support to enable this setting.
This feature improves the performance of the Invoicer batch job for accounts with a large number of Master Plan Instances (MPIs) and Supplemental Plan Instances (SPIs).
This feature updates Aria behavior when taking an MPI out of suspension and moving it out of dunning. Rather than assigning an 'Active' status to the MPI, Aria now assigns the status it had before it was suspended.
The fields listed below are now available for you to include in your payment reminder and dunning email templates. Please contact Aria Customer Support if you want to include this information in the email templates mentioned above:
This feature adds the input fields “bank name” and “bank city” for the Direct Debit payment method on the Create Account screen in the Aria UI.
This enhancement includes another iteration of Aria's Daily/Weekly Billing, which will be released in phases. In this phase, Aria added the key features listed below. Please see the documentation linked to below for more details:
The latest iteration of the Aria Data Streaming Web Service introduces the Plan Relationship, Usage Types, and Usage Unit Types objects in the Aria Data Stream. View the Data Streaming Logical Object Model for details.
This feature increases the length of the Custom Dashboard URL field to 1000 characters in the Aria UI on the Configuration > Client Settings > Company Profile screen.
Aria's integration with the Chase Paymentech payment gateway has been enhanced with support for 3D Secure (3DS) Authentication 2.0. The 3DS authentication feature provides additional fraud prevention when transactions are processed. This is supported for the Visa and MasterCard card types.
Click here to access the Chase Paymentech payment processor page for detailed instructions.
Additional Field Enhancements
Also, as part of this feature, the following URL fields have been expanded to 200 characters for the following payment processors:
Processor | Impacted URL Field |
Adyen | 3DS Termination URL |
Cybersource | 3DS Client JS Library URL |
Ingenico | 3DS Termination URL |
Worldpay |
Challenge Posting URL |
When you create or update an order, you can now provide an Order Fulfilled Date that is in the past.
Note: Currently, setting the Order Fulfilled Date makes that data available for informational purposes only. Setting the Order Fulfilled Date does not result in changes to an order or account.
This feature modifies the Products > Plans > [specific plan] > Rates tab > [click Rate Schedule icon] screen in the Aria UI: The fields Billing Interval and Usage Interval have been updated to Recurring Billing Interval and Usage Billing Interval respectively.
More information on Rate Settings can be accessed from here.
When searching for Customer Support Representative (CSR) Activity (Analytics and Reporting > Reports > CSR Activity), the Customer Support Representative (CSR) Internet Protocol (IP) Address is now masked with the word “Internal” if an address is found as part of the search results. (TICKET-18068)
The API calls create_order_m and update_order_m have been updated to create “order qualifiers” based on the inputs received from the existing <optional_transaction_qualifiers> input. The get_order_m API has been updated to include the <order_qualifiers> array output fields.
An order qualifier provides an additional level of detail concerning an item on an order. For example, an order item can be a router. In the order qualifier field/qualifier value array, you can pass information such as the router manufacturer, serial number, or connection speed (such as 5GHz). This eliminates the need to create individual order items for every possible combination of a particular item.
Field Name | Value |
<bill_immediately> | 0, 1, 2 |
<do_write> | True |
Enter the details in the existing fields of the <optional_transaction_qualifiers> input array and run the API.
Field Name | Value |
<bill_immediately> | 0, 1, 2 |
<do_write> | True |
Enter the details in the existing fields of the <optional_transaction_qualifiers> input array and run the API.
Note: If order qualifiers are created using create_order_m and update_order_m is run for that order with no new order qualifiers, the order qualifiers generated using create_order_m will be retained.
Start of <order_qualifiers> output array | |
Field Name | Description |
<qualifier_name> | Name of the field you want to associate with this API call. |
<qualifier_value> | Corresponding value of the field you want to associate with this API call. |
End of <order_qualifiers> output array |
You can now use the get_invoice_history_m API to retrieve the invoice history of all master plan instances (MPIs) or your specified set of MPIs for an account. To do so:
This feature updates Aria logic so when the client parameter REJECT_USAGE_WHEN_USAGE_TYPE_NOT_ON_PLAN is set as "true," the APIs record_usage_m and bulk_record_usage_m will now return "Error 20006 Usage code, or type not on active plan" when those API calls reference a usage type that is not mapped to the given plan instance, or when the plan instance is inactive.
This enhancement includes another iteration of Aria's Daily/Weekly Billing, which will be released in phases. In this phase, Aria added this feature: you can now use the edit_acct_plan_queued_changes_m API to complete daily/weekly plan updates and billing date resets with any <queue_edit_directive> or <assignment_directive>.
Aria's integration with the Chase Paymentech payment gateway has been enhanced with support for 3D Secure (3DS) authentication 2.0. The 3DS authentication feature provides additional fraud prevention when transactions are processed. This is supported for the Visa and MasterCard card types.
The following output field is new for this feature (for the <proc_3dsecure_data/ proc_3d_secure_auth_data> array):
Field Name | Description | Affected APIs |
<pa_3ds_from_content> |
If the issuer’s Access Control Server (ACS) supports this feature, this field will receive content to populate the client’s form page to enable 3DS authentication. If the issuer’s ACS does not support this feature, no information for authentication will be returned to this field. |
authorize_3dsecure_m |
Click here to access the Chase Paymentech payment processor page for detailed instructions.
Note: Currently, setting the <fulfilled_date> makes that data available for informational purposes only. Setting the <fulfilled_date> does not result in changes to an order or account.
Invoices will no longer be generated when updating test accounts with the API update_acct_plan_multi_m. (TICKET-18161)
Stage Current
US | https://secure.current.stage.ariasys...l_wrapped.wsdl |
EUR | None |
AUS | https://secure.current.stage.aus.ari...l_wrapped.wsdl |
Stage Future
US | https://secure.future.stage.ariasyst...l_wrapped.wsdl |
EUR | https://secure.future.stage.cph.aria...l_wrapped.wsdl |
AUS | https://secure.future.stage.aus.aria...l_wrapped.wsdl |
Production
US | https://secure.ariasystems.net/api/A...l_wrapped.wsdl |
EUR | https://secure.prod.cph.ariasystems....l_wrapped.wsdl |
AUS | https://secure.prod.aus.ariasystems....l_wrapped.wsdl |
Stage Current
US | https://secure.current.stage.ariasys...l_wrapped.wsdl |
EUR | None |
AUS | https://secure.current.stage.aus.ari...l_wrapped.wsdl |
Stage Future
US | https://secure.future.stage.ariasyst...l_wrapped.wsdl |
EUR | https://secure.future.stage.cph.aria...l_wrapped.wsdl |
AUS | https://secure.future.stage.aus.aria...l_wrapped.wsdl |
Production
US | https://secure.ariasystems.net/api/A...l_wrapped.wsdl |
EUR | https://secure.prod.cph.ariasystems....l_wrapped.wsdl |
AUS | https://secure.prod.aus.ariasystems....l_wrapped.wsdl |