Skip to main content
Aria Knowledge Central

Release 20

Overview

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

Release Date

Stage Future Release Date

21-February-2019

Production Release Date

14-March-2019

System Requirements

Supported Browsers

  • Chrome 63
  • Firefox 52
  • Safari 11 on MacOS

Screen Resolution

1024 x 768 or higher

Release 20 Contents

 


Application Features











Application Fixes

  • The Aria UI now correctly displays the value set on the backend for the parameter "Auto Send Statement On Pending Invoice Approval." (TICKET-14053)
  • Accounts with pending invoices no longer generate "Internal errror: Invalid plan instance no" when a plan is replaced immediately. If any errors occur while replacing a plan then the system will rollback the applied changes. (TICKET-14708)
  • Aria corrected the currency label for ERN to be "Eritrean Nakfa." (TICKET-14783)
  • Order totals are now displayed on the corresponding statements for the applicable customers instead of on the wrong statements. (TICKET-15593)
  • When a write-off is created successfully, the write-off amount in the confirmation message now shows the correct amount. (TICKET-15851)
  • A newly assigned Supplemental Plan(s) activation fees are now correctly being invoiced after activating/reactivating it's Master Plan Instance when the client parameter Multiply Activation Fees By Plan Unit is set to "True". (TICKET-16002)
  • If you have an account with a master plan instance in the active non-billable status and you try to create an order with the selection "Allow this order's line items to be reflected on the next regularly schedule periodic invoice for this account", the correct error message now appears: "single order billing not allowed plan instance status prevents it". You no longer encounter an ORA error. (TICKET-16109)
  • The fixes listed below have been implemented in the Aria application. When you assign a master plan and a supplemental plan at the same time:
    • The override bill through date is now honored when both plans have the same billing interval.
    • As expected, the override master plan instance number (Sync With Master Plan Instance option) is honored when both plans have the same billing interval. This is true whether the supplemental plan is mandatory or optional.
    • When you set a retroactive start date or alternate start date for the master plan, that date is now honored.
      (TICKET-16187)
  • If you use Chase Paymentech as your payment gateway, your selected Recurring Options in your Collection Group Options for that gateway are saved, as expected. (TICKET-16504)
  • Long-cycle combined invoices resulting from creating accounts with Supplemental Plans that include one-month rollovers now retain and bill for the initial (non-rollover) Supplemental Plans rather than immediately rolling over to the new plan. (TICKET-16544)
  • Usage submitted via bulk_record_usage_m inclusive of units and a pre-defined amount (rate = Null) with the client setting Include Usage Charges on First Invoice = "True" is now correctly billed and charged on the customer's first invoice. (TICKET-16609). 
  • save_paypal_bill_agreement_m, get_paypal_avs_status_m, and init_paypal_bill_agreement_m now successfully initialize audit records via the > Configuration > Audit Logs > Web Service API. (TICKET-16679)
  • All currency codes in the Aria databases are now mapped to their corresponding numeric ISO codes in support of downstream payment processing and/or taxation vendors where possible. In some cases non-ISO currencies were entered to support specific needs for particular payment processors and/or taxation providers. (TICKET-16747)
  • When you pass a <locality> along with a complete address (at the account, billing, or statement level) into the create_acct_complete_m API call, then the address on the Contacts screen and Orders (Assign a Contact) screen will be displayed in the same way as on the Account Overview screen. (TICKET-16754)
  • Service credits created for a tax line item during a proration calculation now reflect the correct discounted tax amount. (TICKET-16766)
  • Master Plan now gets replaced on anniversary. Custom rate details of the new master plan are updated after updating the plan_instance table with new plan details. (TICKET-16780)
  • The rollover credit screen in the Aria UI has been updated with text relating to currency when creating a new service credit. The text, "Your access level dictates that you may create Master Plan Instance credits of an unlimited amount. Fill out the form below using a valid US Dollars amount and click Create Credit", has been revised to state "Your access level....Fill out the form below using a valid currency amount and click Create Credit". For limited service credit creation the text has been altered to state "Your access level dictates that you may not create Master Plan Instance credits greater than <currency_code><currency_symbol>XXXX" to indicate the dynamic parts (currency would vary from account to account). (TICKET-16806)
  • The <master_plan_instance> tag in payload version 2.0 of the "Account Created" provisioning event is now spelled correctly; and, the order of the <user_id> and <client_acct_id> fields now matches the versions 1.0 and 2.0 payloads in the 1.0 and 2.0 XSDs. (TICKET-16817)
  • Editing a newly assigned contact now functions as expected. A user is now able to go back to an assigned contact and update the values. (TICKET-16836)
  • Custom Rate Tiers for a Supplemental Plan Instance are now displaying correctly in the UI via the > Account > Plans > Supplemental Plan Instance screen, when the Supplemental Plan's parent Master Plan Instance is canceled/suspended, and then reactivated. (TICKET-16869)
  • When usage accumulation reset months is set, and a plan with a usage service whose name exceeds 75 characters is processed by the Aria Invoicer, the invoicer no longer fails with a "character string buffer too small error occurred" error. (TICKET-16886)
  • When you cancel a supplemental plan, any recorded usage associated with that plan is billed, as expected. (TICKET-17007)
  • get_usage_history_m now correctly returns all usage records for a pending invoice when filtered using the <invoice_no> input parameter. (TICKET-17030)
  • General credit memo applied on the invoice is now correctly reflected in the statement by allowing the system to consider the "account-level credit memo" for the statement as well as loopers used for sending the statement invoice.(TICKET-17047)
  • An error no longer occurs when you try to create a new chart of accounts (COA) code while adding a new service to a new plan. (TICKET-17050)
  • Aria now correctly updates the due date for invoices in Dispute Hold, and now handles Dispute Hold for child account invoices as expected. (TICKET-17106)
  • Supplemental plans queued for cancellation on their Anniversary dates are no longer being billed in error. Aria now checks the future queued status assigned on anniversary date before calculating the recurring change and the plan instance is now canceled without billing as expected. (TICKET-17107)
  • The SPI's product field/plans locale description value column size has been extended to 1000 and events are processed as expected and no longer cause the event notification message creation to fail. Additionally, along with the SPI's product field, the account field value and plan's product field value have also been extended. (TICKET-17113)
  • A Product Catalog change event notification with a method delivery of XML Document is now successfully generated for a plan description having up to 1000 characters. (TICKET-17114)
  • Aria's Workflow integration now supports Active Orchestration Event 708 (Account Supplemental Field Value Deleted within the "Accounts and Master Plan Instances" event group). (TICKET-17161)
  • When you delete a plan and event 1202 (Plan Deleted) is triggered, that event is now successfully transmitted to Workflow. (TICKET-17170)

API Features







API Fixes

  • Aria now correctly charges for recurring arrears services when a Supplemental Plan with a monthly rollover is assigned via assign_acct_plan_m with alt_proration_start_date and combined_invoice set to "true." (TICKET-16027)
  • 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)
  • Aria now charges Activation Fees as expected when a prorated invoice results from assigning a master plan via update_acct_plan_multi_m. (TICKET-16178)
  • Empty spaces in the <is_batch_running> output parameter are no longer being returned in get_virtual_datetime_m. The data_type has been altered such that <is_batch_running> will return only a "Y" or "N" without empty spaces in the JSON response. (TICKET-16386)
  • All affected next bill dates are now set correctly when you assign or replace a master plan and/or supplemental plan using the update_acct_plan_multi_m API and you specify any of these billing date/billing options:
    • set your Override Bill Thru Date Supp Plan Behavior parameter to Align supplemental plans by backtracking from master plan renewal date (in the Aria application under Configuration > Billing > Invoice Settings); and/or
    • pass a value into the <override_bill_thru_date>, <force_master_bill_date_reset>, <offset_months>, <auto_offset_months_option>, or <alt_proration_start_date> field. (TICKET-16645)
  • When you use the update_acct_plan_multi_m API to a) replace one plan with another plan that has a different billing interval or b) update a plan's rate schedule, the next bill date and last bill through date are now set correctly for the assigned plan. (TICKET-16676)
  • You can now successfully update the early cancelation fee alone in a multi-plan contract when using modify_instance_contract_m. (TICKET-16752)
  • When a master plan is replaced on anniversary with custom rate given via update_acct_plan_multi_m API, then the master plan is replaced with the custom rate details of the new master plan after updating plan_instance table with new plan details. Future queued replace plan is displayed in the executed status and the plan should be replaced with corresponding custom rate given. (TICKET-16780)
  • When you use the update_acct_plan_multi_m API to assign a supplemental plan in the middle of a customer's billing cycle, the charges are prorated, as expected. (TICKET-16835)
  • When you pass a <locality> along with a complete address (at the account, billing, or statement level) into the create_acct_complete_m API call, then the address on the Contacts screen and Orders (Assign a Contact) screen will be displayed in the same way as on the Account Overview screen. (TICKET-16754)
  • When you call the update_acct_complete_m API and pass in an <acct_start_date>, that input is now honored. (TICKET-16875)
  • Minimum and maximum allowable plan units for the mandatory supplemental plan's units are now being suppressed when the input_parameter plan units is NULL and the value will no longer be changed to "1" when the update_acct_plan_m is called for updating the product fields alone. (TICKET-16944)
  • When you cancel a supplemental plan, any recorded usage associated with that plan is billed, as expected. (TICKET-17007)
  • get_usage_history_m now correctly returns all usage records for a pending invoice when filtered using the <invoice_no> input parameter. (TICKET-17030)
  • get_recurring_credit_info_m API is now honoring the locale_no input. The Oracle session context is now populated with the given locale to get to the translated values. The following Aria 6-related output fields were deprecated: <eligible_plan_no>, <eligible_plan_name>, <eligible_service_no>, <eligible_service_name>, <client_eligible_plan_id>, <client_eligible_service_id> (TICKET-17035)
  • These 2 fixes have been implemented:
    • When you pass an alphabetical value into the <existing_client_dunning_group_id> field in the update_acct_plan_multi_m API, an error no longer occurs.
    • Decimal numbers are honored, as expected, when you pass them into:
      • the <contract_cancel_fee> field in the create_acct_complete_m API; or
      • the <balance_forward> field in the update_acct_plan_multi_m API.
        (TICKET-17115)
  • When you use the update_acct_plan_multi_m API to complete multiple plan changes involving payments with multiple billing groups, if a collection attempt made with one billing group fails:
    • now plan changes are saved in Aria if the collections were made successfully with the associated billing groups and Aria no longer rolls back the changes;
    • plan changes are rolled back only if they were attempted with an unsuccessful collection made with its associated billing group, as expected. (TICKET-17133)
  • The issue that was causing timeouts and periodic 500 internal server errors when making calls to the get_account_details_m API with larger/more complex accounts has been resolved and the API calls now work as expected. (TICKET-17153)

WSDL File Locations

Stage Current

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

Stage Future

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

Production

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

Object Query WSDL Files

Stage Current

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

Stage Future

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

Production

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