Home > Aria Crescendo Documentation > Aria Release Notes > Release 28

Release 28

Overview

Enhancements and fixes to Aria functionality for this release are described below.

Release Date

Stage Future Release Date

 24-March-2020

Production Release Date

16-April-2020

System Requirements

Supported Browsers

  • Chrome 63
  • Firefox 52
  • IE11
  • Safari 11 on MacOS 

Screen Resolution

1024 x 768 or higher

Release 28 Contents

Application Features 

Multiple Rate Schedules For Non-Subscription Offerings (DEV-6953)

This feature introduces the ability to create multiple rate schedules for Non-Subscription Offerings (NSOs) in Aria Crescendo. Now, for each currency supported in your Aria instance, you can offer pricing for NSOs based on the number of units a customer purchases.

Now, when configuring a rate schedule for a Non-Subscription Offering associated with a plan, you can specify rate tiers.

To maintain backwards compatibility, Aria has introduced a new client parameter: INVENTORY_ITEM_APIS_PRICE_BEHAVIOR. This parameter governs the behavior when retrieving NSOs via API. View details about this client parameter in the API Features section of these release notes.

Notification Template Group List Performance Improvement (DEV-9789)

This feature enhances the performance of the Notification Template Group Notification Template Group list screen accessible in the Aria UI under Configuration > Notifications > Notification Template Group.

Daily-Weekly Billing Phase 2 (DEV-9790)

This feature includes another iteration of Aria's Daily/Weekly Billing, which will be released in phases. In this phase, Aria adds proration features (previously available only on billing intervals that were monthly or greater) to accommodate plan replacement scenarios.

All types of proration (no proration, charge only, credit only, and full) with different Assignment Directives (immediate, anniversary, and future) are supported for Daily-Weekly Billing.

See Proration and Daily-Weekly Billing for more details.

Also added to Daily/Weekly Billing in Phase 2:

  • invoice unbilled usage
  • plan status (i.e. active for new plan and inactive for old plan)
  • alternate proration start date (applicable only for master plan instance)
  • coupon application

Offset options (offset interval and offset months) are not yet supported. Support for these options is planned for a future release. 

Improved Performance of Event Audit Logs (DEV-9817)

You will notice improved response time of the audit logs for events. This improvement will be noticed primarily by those who subscribe to multiple account-related events.

Include Service Group Totals in Statements (DEV-9831)

You can now include the new replacement strings (fields) listed below in your statement templates to provide the identified information in your customers' statements. Please contact Aria Customer Support for more information and for help with setting up your service groups and statement templates.

  • insertServGrp[1-29]Total: Total non-tax charges for all services within a service group (for up to 29 service groups)
  • insertServGrp[1-29]Label: Name of a service group (for up to 29 service groups)
  • insertServGrp[1-29]Taxes: Total taxes for all services within a service group (for up to 29 service groups)
  • insertServGrp[1-29]Gross: Gross charges (non-tax charges + taxes) for all services within a service group (for up to 29 service groups)
  • insertService[1-19]Total: Total non-tax charges for an individual service within a service group (for up to 19 services)
  • insertService[1-19]Label: Name of an individual service within a service group (for up to 19 services)

 

Note: The calculations for the fields listed above are done at the service group level for each statement and not at the master plan instance (MPI) level. This is true even if there are multiple MPIs in a statement.

Application Fixes 

  • Aria no longer sends the Contract expired event (Event ID: 733) when contracts with only non-provisioned plans pass their expiry dates. Before this fix was applied, contracts with the following end actions were affected: Terminate service and billing; Terminate service and billing and prorate final invoice; and Rollover to a Plan and/or a Rate Schedule. (TICKET-17674)
  • Aria sandbox environments will now process changes in Notification Template Groups and allow them to be saved. (TICKET-17694)
  • From the Analytics and Reporting\Reports menu, select and run a report. From the Preview mode, select Download. The .csv file would take a line of data (with multiple rows per line) and, if the first three rows of the line contained less than 3,000 characters and the last row contained more than 1,000 characters with a space present in that row, an LF break appeared and incorrectly separated the last row. This has been resolved and the LF break field appears correctly on the last line. (TICKET-17714)
  • On the Account Overview screen, any large overpayments are now displayed as credits instead of positive balances. (TICKET-17718)
  • The invoice generation batch job no longer fails when fetching invoice lines that will be offset by proration credits. (TICKET-17726)
  • A plan's invoice is no longer voided when a credit memo was applied to it and you attempt to generate a prorated invoice (example: by canceling or replacing that same plan). Instead, this message is displayed: “The invoice cannot be voided because one or more credit memos have been applied to it.” (TICKET-17735)
  • You can now enter values with html characters (<,>,",/,:) for Non-Subscription Offering rate schedule names, then load the Create New Order and Order Details screens in the Aria UI without receiving an error. The Create Order SKU list database table is also populated as expected when such rate schedule names are used. (TICKET-17797)

API Features 

Multiple Rate Schedules For Non-Subscription Offerings (DEV-6953)

This feature introduces the ability to create multiple rate schedules for Non-Subscription Offerings (NSOs) in Aria Crescendo. Now, for each currency supported in your Aria instance, you can offer pricing for NSOs based on the number of units a customer purchases.

To maintain backwards compatibility, Aria has introduced a new client parameter: INVENTORY_ITEM_APIS_PRICE_BEHAVIOR. This parameter governs the behavior when retrieving NSOs via API. This parameter defines how Aria prices inventory items created prior to this enhancement. Possible values are:

  • "Backwards compatible price set only when currency default rate schedule has a non-zero first tier" ("FIRST_NONZERO")
  • "Backwards compatible price is set to zero if no currency default rate schedule" ("ZERO"),
  • "Backwards compatible pricing is not used, only rate schedules" ("NO_OLD_PRICE").

The default for new clients is "NO_OLD_PRICE". You should not use the deprecated old input (return_no_cost_items) and outputs (all_item_prices) once you add additional tiers to default rate schedule(s) or add more rate schedules for a currency.

Note: If you do use these deprecated field(s) after moving to a multi-tier or multi-price NSO, the results may not be accurate.

The following API calls have been updated with new or enhanced input fields to support this new functionality.

The following API calls have been updated with new output fields to support this new functionality.

The following API calls have been updated with new input and output fields to support this new functionality.

Worldpay Support for 3D Secure Authentication 2.0 (DEV-9779)

Aria's integration with the 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.

To use 3DS 2.0:

  1. Configure the new Payer Authentication Settings in your payment gateway and/or collection group options for Worldpay.
  2. Call APIs as described in the authorize_3dsecure_m documentation.

Please contact your Worldpay representative ​for additional information about using 3DS 2.0.

Daily-Weekly Billing Phase 2 (DEV-9790)

This feature includes another iteration of Aria's Daily-Weekly Billing, which will be released in phases. In this phase, Aria adds proration features (previously available only on billing intervals that were monthly or greater) to accommodate plan replacement scenarios.

Several APIs have been updated to include additional output parameters to accommodate Phase 2 of Daily-Weekly Billing features, which include:

  • replace plan proration scenarios
  • invoice unbilled usage
  • plan status (Active for new plan and Inactive for old plan)
  • alternate proration start date (applicable only for master plan instance)
  • coupon application
API Calls New Output Parameters

<weekly_fee>: If the plan interval is more than one week, this field will rate per unit per week'

<daily_fee>: If the plan interval is more than one week, this field will rate per unit per week

<recurring_billing_period_type>: Period type for billing cycles for recurring. Values:

  • 1—Daily
  • 2—Weekly
  • 3—Monthly
  • 4—Quarterly
  • 5—Yearly

<usage_billing_period_type>: Period type for billing cycles for usage. Values:

  • 1—Daily
  • 2—Weekly
  • 3—Monthly
  • 4—Quarterly
  • 5—Yearly

Use Braintree to Authorize Tokenized Credit Cards (DEV-9795)

If you use the Braintree payment gateway, you can now:

  • Authorize a tokenized credit card that was previously authenticated outside of Aria without having to repeat the authentication in Aria. To do so, follow the instructions described in the authorize_electronic_payment_m or validate_acct_fraud_scoring_m API documentation; and
  • Authorize a tokenized credit card when you change/add payment information. To do so, follow the instructions described in the update_payment_method_m API documentation.

Use Worldpay to Authorize Tokenized Credit Cards (DEV-9796)

If you use the Worldpay payment gateway, you can now:

  • Authorize a tokenized credit card that was previously authenticated outside of Aria without having to repeat the authentication in Aria. To do so, follow the instructions described in the authorize_electronic_payment_m or validate_acct_fraud_scoring_m API documentation. These two new inputs were added to the validate_acct_fraud_scoring_m API to support credit card tokenization: <bill_agreement_id> and <cc_id>; and
  • Authorize a tokenized credit card when you change/add payment information. To do so, follow the instructions described in the update_payment_method_m API documentation.

Enhancement Allowing the Responsible MPI to Be Set from any Account in its Ancestry (DEV-9808)

This enhancement to APIs set_payment_responsibility_m  and create_acct_complete_m allows the Responsible MPI (master plan instance) for a Parent Pay Child Account to be set from any account in the ancestry hierarchy. This allows a grandchild account MPI with Parent Pay, to have the responsible MPI be either the Child account, or the Parent account in the account hierarchy.

Use Adyen to Authorize Tokenized Credit Cards (DEV-9815)

If you use the Adyen payment gateway, you can now:

  • Authorize a tokenized credit card that was previously authenticated outside of Aria without having to repeat the authentication in Aria. To do so, follow the instructions described in the authorize_electronic_payment_m or validate_acct_fraud_scoring_m API documentation; and
  • Authorize a tokenized credit card when you change/add payment information. To do so, follow the instructions described in the update_payment_method_m API documentation.

Use Chase Paymentech to Authorize Tokenized Credit Cards (DEV-9816)

If you use the Chase Paymentech payment gateway, you can now:

  • Authorize a tokenized credit card that was previously authenticated outside of Aria without having to repeat the authentication in Aria. To do so, follow the instructions described in the authorize_electronic_payment_m or validate_acct_fraud_scoring_m API documentation; and
  • Authorize a tokenized credit card when you change/add payment information. To do so, follow the instructions described in the update_payment_method_m API documentation.

API Fixes 

  • The pre_calc_invoice_m API has been deprecated. If you want get a preview of an invoice without generating one, you can call the create_acct_complete_m API with the <do_write> field set to false. (TICKET-12718)
  • XML Exception error: Unexpected element: CDATA was being displayed in authorize_electronic_payment_m API response instead of in the correct XML format (TICKET-16091)
  • A plan's invoice is no longer voided when a credit memo was applied to it and you attempt to generate a prorated invoice (example: by canceling or replacing that same plan). Instead, this message is displayed: “The invoice cannot be voided because one or more credit memos have been applied to it.” (TICKET-17735)
  • The future plan changes are now completing as expected when:
    • using the update_acct_plan_multi_m API to remove the product field values from an existing plan instance; and
    • replacing the existing plan instance with a new plan instance that has a future effective date. (TICKET-17746)
  • If you 1) use an API to assign a plan and pass in an <override_bill_thru_date>, 2) change that plan's rate schedule to one with a shorter billing interval, then 3) regenerate the invoice for the plan, the new invoice will reflect the changed billing interval, as expected. (TICKET-17747)
  • When you call the replace_acct_plan_m API and pass 1 into the <assignment_directive> field, this error message is no longer returned: "An Oracle database error has occurred." Instead, the plan replacement is scheduled for the anniversary date, as expected. (TICKET-17790) 
  • When calling the create_order_with_plan_m API with <bill_immediately> = 1 the following  error message is no longer returned: "An Oracle database error has occurred." Instead, the order will complete as expected . (TICKET-17792) 

WSDL File Locations

Stage Current

US https://secure.current.stage.ariasystems.net/api/Advanced/wsdl/28/complete_m-doc_literal_wrapped.wsdl
EUR None
AUS https://secure.current.stage.aus.ariasystems.net/api/Advanced/wsdl/28/complete_m-doc_literal_wrapped.wsdl

Stage Future

US https://secure.future.stage.ariasystems.net/api/Advanced/wsdl/28/complete_m-doc_literal_wrapped.wsdl
EUR https://secure.future.stage.cph.ariasystems.net/api/Advanced/wsdl/28/complete_m-doc_literal_wrapped.wsdl
AUS https://secure.future.stage.aus.ariasystems.net/api/Advanced/wsdl/28/complete_m-doc_literal_wrapped.wsdl

Production

US https://secure.ariasystems.net/api/Advanced/wsdl/28/complete_m-doc_literal_wrapped.wsdl
EUR https://secure.prod.cph.ariasystems.net/api/Advanced/wsdl/28/complete_m-doc_literal_wrapped.wsdl
AUS https://secure.prod.aus.ariasystems.net/api/Advanced/wsdl/28/complete_m-doc_literal_wrapped.wsdl

Object Query WSDL Files

Stage Current

US https://secure.current.stage.ariasystems.net/api/AriaQuery/wsdl/28/integration_services_m-doc_literal_wrapped.wsdl
EUR None
AUS https://secure.current.stage.aus.ariasystems.net/api/AriaQuery/wsdl/28/integration_services_m-doc_literal_wrapped.wsdl

Stage Future

US https://secure.future.stage.ariasystems.net/api/AriaQuery/wsdl/28/integration_services_m-doc_literal_wrapped.wsdl
EUR https://secure.future.stage.cph.ariasystems.net/api/AriaQuery/wsdl/28/integration_services_m-doc_literal_wrapped.wsdl
AUS https://secure.future.stage.aus.ariasystems.net/api/AriaQuery/wsdl/28/integration_services_m-doc_literal_wrapped.wsdl

Production

US https://secure.ariasystems.net/api/AriaQuery/wsdl/28/integration_services_m-doc_literal_wrapped.wsdl
EUR https://secure.prod.cph.ariasystems.net/api/AriaQuery/wsdl/28/integration_services_m-doc_literal_wrapped.wsdl
AUS https://secure.prod.aus.ariasystems.net/api/AriaQuery/wsdl/28/integration_services_m-doc_literal_wrapped.wsdl
Last modified

Tags

This page has no custom tags.

Classifications

This page has no classifications.
Powered by CXone Expert ®