Skip to main content
Aria Knowledge Central

Release 19

Overview

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

Release Date

Stage Future Release Date

6-December-2018

Production Release Date

9-January-2019

System Requirements

Supported Browsers

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

Screen Resolution

1024 x 768 or higher

Release 19 Contents


Application Features














Application Fixes 

  • Payment applications are no longer rounded when created in Aria batch processes. Previously, rounding errors were causing issues with downstream reporting. (TICKET-16664)
  • Date formats are now consistently and correctly displayed in the Aria UI Plan Instance Detail, All Service Rates, and Rate Schedule Detail pages based on the client-defined parameter setting in > Configuration > Client Settings > Miscellaneous Settings > Date Format Mask. (TICKET-16669)
  • $0 refund line items are no longer displayed on an invoice when you issue a full or partial refund that applies to an invoice:
    • With multiple charges; and
    • With or without service credits included.
      (TICKET-16671)
  • Your selection of either of these values for the Dispute Hold Expiration Action parameter is now correctly saved in Aria: Restore and Re-age or Restore or Do Not Re-age. Those values are no longer replaced with each other. (TICKET-16684)
  • An error no longer occurs when Aria adds queued services to plans. Instead, the queued services are added to the plans on your specified dates, as expected. (TICKET-16703)
  • An error message "Bulk Usage cannot exceed more than 1000 records" is now returned when a user tries to upload more than 1000 records via the Aria UI. (TICKET-16719)
  • Errors no longer result when scheduled reports are copied via Copy Config. (TICKET-16725)
  • The Universal Activity Loader (UAL) batch job now runs successfully via the Aria UI. (TICKET-16726)

API Features











API Fixes

  • You can now pass a valid date without a time into date fields in the following APIs: get_coupon_history_m, get_all_invoice_information_m, and get_invoice_history_m. When you do that, an error no longer occurs and the data matching your query is returned. (TICKET-8308)
  • 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)
  • $0 refund line items are no longer displayed on an invoice when you issue a full or partial refund that applies to an invoice:
    • With multiple charges; and
    • With or without service credits included.
      (TICKET-16671)
  • Plan unit instances are now successfully removed when plan instance units is downgraded via the update_acct_plan_multi_m API. (TICKET-16678)
  • You can now successfully create a surcharge having multiple rates schedules and rate tiers using create_surcharge_m. (TICKET-16685)
  • You no longer encounter an error when you call the validate_payment_information_m API and you pass in a cvv (card verification value) that is less than 3 characters long. This is because that field is now formatted correctly. When the payment method is American Express, Aria now adds zeros to the cvv to make the field 4 characters long. When the payment method is not American Express, Aria now adds zeros to the cvv to make the field 3 characters long. These changes apply to the following payment gateways:
    • Adyen
    • BrainTree
    • Chase Paymentech
    • Merchant e-Solutions
    • First Data Payeezy
    • Paymetric
    • PayPal PayFlow Pro
    • First Data PayPoint
    • TNS

For supported payment gateways not listed above, the cvv field was already formatted correctly. (TICKET-16744)

  • API Live no longer prevents users from entering values in certain fields due to incorrect pick lists in some APIs. (TICKET-16746)

WSDL File Locations

Stage Current

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

Stage Future

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

Production

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

Object Query WSDL Files

Stage Current

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

Stage Future

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

Production

US https://secure.ariasystems.net/api/AriaQuery/wsdl/19/integration_services_m-doc_literal_wrapped.wsdl
EUR https://secure.prod.cph.ariasystems.net/api/AriaQuery/wsdl/19/integration_services_m-doc_literal_wrapped.wsdl
AUS https://secure.prod.aus.ariasystems.net/api/AriaQuery/wsdl/19/integration_services_m-doc_literal_wrapped.wsdl
  • Was this article helpful?