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
Stage Future Release Date
24-November-2020
Production Release Date
12-January-2021
System Requirements
Supported Browsers
Screen Resolution
1024 x 768 or higher
We are happy to announce that on 11 December 2020, we will update Aria’s product documentation site with these enhancements:
Release 33 Contents
If you use Direct Post, you can now collect payments made using the Direct Debit payment method. To do so:
Please contact Aria Customer Support to set up your statement templates.
After using high water mark functionality when invoicing for billable usage units across more than one usage record, the billable units are now correctly updated to 0 as recorded units for all usage records not meeting the high water mark threshold. If two or more usage records have the same number of billable units meeting the threshold, the oldest usage record will be applied to track billable units for the usage service.
The Aria application has a new feature called Statement BCC Email Address. This gives you the ability to include a BCC email address in invoice statement emails. Statement BCC Email Address can be configured in Configuration > Notifications > Notification Settings > Statement BCC Email Address.
The enhancement allows more entries to display on the Invoices and Credit Memos screens. The Invoices screen will now display 2000 entries, and the Credit Memos screen will now display an unlimited number of entries.
This feature allows users of Aria's Data Streaming Web Service to subscribe to the objects that they want to see in their data streams. This optimizes the efficiency of the stream, because only the objects subscribed to appear in the streams.
Access this feature in the Aria UI via Configuration > Notifications > Stream Object Subscription for clients who have purchased the Data Streaming service, and its display is controlled via the roles of the logged in user. By default, all roles will have ‘read only’ access. Modifications to roles access can be done from the Roles module in the Aria UI.
Read more about subscribing to objects in the Data Streams.
A new client parameter has been added (Configuration > Payments > Payment Settings) called Include Credit Memo In Dunning. If set to True, this removes an account from dunning by applying an invoice-based credit memo to a master plan instance within the account to bring the outstanding balance below the dunning threshold (False is the default).
Click here to learn more about changing a payment setting.
The Cash Credit and Service Credit details can now be viewed as expected when you have access to the Payments & Credits > Cash Credits and Service Credits screens respectively. (TICKET-18205)
This feature adds Level 2 and 3 data processing support to the Ingenico payment gateway. Level 2 data are included for determining a card's affluence, which may influence your marketing initiatives, and Level 3 data includes invoice line item details that allow you to receive lower transactional fees from credit card processors. Level 2 and Level 3 data are supported by the Credit Card and Tokenized Credit Card payment methods and the Visa® and Mastercard® card types.
Note: Aria sends Level 2 and 3 data to Ingenico only when making a single API call to collect a payment. Level 2/3 data cannot be sent to Ingenico when payment collection is made with 2 separate API calls (e.g., using authorize_electronic_payment_m to authorize a $3 payment and collect_from_account_m to capture the $3 authorized amount).
Learn more about Aria's integration with the Ingenico payment gateway from here.
Aria has enhanced the get_acct_trans_history_m API with additional filtering options as described below. This enhancement will also allow you to control the number of records that you transfer to your other systems that may have size limitations:
API | Input | Description |
---|---|---|
|
<billing_group_no> | Aria-assigned identifier of the billing group whose collection group you want to use |
<client_billing_group_id> | Client-defined identifier of the billing group whose collection group you want to use | |
<master_plan_instance_no> | Aria-assigned identifier of the master plan instance associated with the billing group whose collection group you want to use | |
<client_master_plan_instance_id> | Client-defined identifier of the master plan instance associated with the billing group whose collection group you want to use | |
get_paypal_avs_status_m (pre-existing inputs) | <billing_group_no> | Same as above |
<client_billing_group_id> | Same as above |
If you use Direct Post, you can now collect payments made using the Direct Debit payment method. To do so:
The Ingenico payment gateway now processes Direct Debit transactions for United Kingdom (UK)-based payments. The existing <mandate_id> input field will be honored now for the Direct Debit Basic Bank Account Number (BBAN) payment method for payments and refunds.
This enhancement applies to the following APIs:
Learn more about Aria's integration with the Ingenico payment gateway from here.
The following output parameters have been introduced for the get_invoice_details_m API:
Field | Description |
---|---|
<usage_from_date> | The usage bill-from date of the invoice. |
<usage_to_date> | The usage bill-through date of the invoice. |
These are needed to explicitly identify usage period details for all invoices.
The new input <client_acct_id> (client-defined account identifier) has been added to the APIs listed below. You can pass in the <client_acct_id>, and/or <acct_no> and/or <user_id> (if available for the API) to identify the customer who will be affected when you call the APIs listed below. Please see the documentation for these APIs for more information:
This feature introduces enhanced support for concurrent calls to an API that causes plan rate updates or changes with better tracking of rate histories of Plan Instances. Enhanced APIs include assign_custom_acct_plan_rates_m, update_acct_plan_multi_m, assign_acct_plan_m, cancel_acct_plan_m, edit_acct_plan_queued_changes_m, modify_acct_plan_unit_instances_m, remove_acct_plan_custom_rates_m, replace_acct_plan_m, update_acct_plan_unit_instance_m, and update_acct_plan_m.
If you pass an invalid <promo_cd> into the get_promotion_details_m API, error code 1016 is returned, as expected, instead of error code 0.
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 |