Aria6 Release 20

• The Aria UI now correctly displays the value set on the backend for the parameter "Auto Send Statement On Pending Invoice Approval." (TICKET-14053)
• 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)
• Aria's Netsuite dispatcher now posts Plan, Service, PlanServices, RateSchedule and Item objects to Netsuite. (TICKET-16240)
• 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)
• Aria's Netsuite dispatcher now preserves the order of object extraction; now, older changes no longer overwrite more recent changes related to the same account during a Netsuite dispatcher run. (TICKET-16547)

• save_paypal_bill_agreement, get_paypal_avs_status and init_paypal_bill_agreement 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)
• Service credits created for a tax line item during a proration calculation now reflect the correct discounted tax amount. (TICKET-16766)
• A rollover plan is now deleted from the queue upon cancelation/removal of the corresponding supplemental plan. In the Aria application, the status of the removed plan is now correctly identified as "Cancelled" on the list of Executed Plan Changes. (TICKET-16783)
• 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)
• 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)
• If a customer has multiple plans that include the same usage-based services, those services are no longer duplicated on invoices. Only the usage-based services for which usage was recorded appear on the invoices, as expected. (TICKET-17074)

• An unexpected error is no longer thrown when updating an account's status from "Active Non-Billable" to "Active" using update_acct_complete when the client parameter setting Enable Single Line Upgrade is set to "True", and no plan units are passed. This issue has been resolved by stopping the single line upgrade attempt by considering the current plan units as new units when new units is not passed. (TICKET-16085)
• Empty spaces in the <is_batch_running> output parameter are no longer being returned in get_virtual_datetime. 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)

• These 2 fixes have been implemented:

  • When you call the replace_supp_plan API and a prorated invoice is generated for the newly assigned supplemental (supp) plan, the customer is billed for any usage charges associated with the new plan, as expected.

  • When you use the assign_supp_plan API to assign a supplemental (supp) plan with a usage-based service and you pass in an <alt_proration_start_date>, the usage is now billed as of your specified <alt_proration_start_date> instead of the plan start date.
    (TICKET-16779)

• The date query strings in get_invoice_information, and get_all_invoice_information have been altered to search and return all objects reflecting just the date match. Previously, when a user entered a date, the code automatically assigned a timestamp of midnight as part of the search query. (TICKET-16786)
• If a customer has multiple plans that include the same usage-based services, those services are no longer duplicated on invoices. Only the usage-based services for which usage was recorded appear on the invoices, as expected. (TICKET-17074)

Stage Current

Stage Future

Production

Stage Current

Stage Future

Production