Release 6.41

Ability to Display Purchase Order Numbers on Invoices (DEV-5624)

This enhancement provides the ability to display purchase order numbers on invoices in Aria. A new client parameter, Show Purchase Order Number, is configurable within the Invoice Settings section of Aria. Once enabled, the parameter controls the display of purchase order numbers on invoices, as well as on the following screens:

Summarize Invoice Line Items for Usage Services and Rates  (DEV-5625)

This improvement summarizes usage line items based on line item type, as opposed to listing each usage line item separately. This results in a smaller number of line items being sent to the tax engine, eliminating application timeouts.

New Notification Methods (DEV-5640)

This enhancement adds the following three new account notification methods:

• XML Master File and HTML Email - When this notification method is selected, the statements for the account and/or master plan instances are added to the XML master file and sent to the customer using HTML email.
• XML Master File and Text Email - When this notification method is selected, the statements for the account and/or master plan instances are added to the XML master file and sent to the customer using text email.
• PDF Master File and HTML Email - When this notification method is selected, the statements for the account and/or master plan instances are added to the PDF master file and sent to the customer using HTML email.

Selecting any of these new notification methods displays a new field titled List Account First in Master File.

Choose Yes if you want the account to be listed at the start of the XML or PDF master file, when produced.

In addition, the List Account First in Master File field displays on the Billing Groups screen.  

Improved Handling of Transactions for Child Accounts with Parent-Pay Responsibility (DEV-5680)

New Electronic Payment Events (DEV-5712)

• ​Electronic Payment Succeeded - This event is triggered when the payment status in Aria changes to "Approved."
• Electronic Payment Failed - This event is triggered when the payment status in Aria changes to “Failed."

Improved Display Of Tax Charges on Statements (DEV-5767)

Updated Password Policy (DEV-5907)

Updated Paymetric Payment Processor Endpoints (DEV-5977)

Application Fixes   

• A Validation Message Failed to Display Upon Adding Mandatory Supplemental Plans to the Plan Exclusion Group (TICKET-9890)
• Newly Added Rate Currencies Failed to Display Within the Configure Selected Inventory Items Section During Plan Creation (TICKET-10070)
• XML Nodes <total_pretax_charges/> and <total_tax_charges/> Were Empty in XML Statements (TICKET-10136)
• Master Plan Instances That Contained a Supplemental Plan Were Listed Twice in Ad-Hoc Search Results (TICKET-10156)
• Issues Occurred When Performing a Copy Configuration (TICKET-10170)
• Special Characters Were Not Supported in Rate Schedule Names (TICKET-10183)
• Users Were Able to Create Plans With "0" Minimum Units/Maximum Units Child Plans (TICKET-10189)
• Invoices Failed to Generate When Supplemental Plans Were Not Fulfilled (TICKET-10227)
• A Zero Amount Invoice Was Generated When an Account Had Two Master Plan Instances With Different Billing and Usage Intervals (TICKET-10370)
• Non-Subscription Offerings Did Not Display on the Orders Screen When Creating an Account (TICKET-10386)
• Invoicer Batch Jobs Failed Unexpectedly (TICKET-10406)

APIs Updated to Support Proration Invoice Timing (DEV-5829)

The following APIs now support proration invoice timing:

• update_acct_plan_unit_instance_m  - The input parameter <proration_invoice_timing> is now available and determines whether to create a separate invoice for prorated charges immediately, or to defer the charges to the next anniversary date. This overrides the Proration Invoice Timing configuration saved with the plan in the Product Catalog.
• modify_acct_plan_unit_instances_m - The input parameter <proration_invoice_timing> is now available and determines whether to create a separate invoice for prorated charges immediately, or to defer the charges to the next anniversary date. This overrides the Proration Invoice Timing configuration saved with the plan in the Product Catalog.
  
  The input parameter <do_write> is now available and determines whether Aria performs the fulfillment change. If "false" is passed in this field, then Aria calculates, if applicable, any potential proration effect that would result from this call. Aria then returns that value in the output field <proration_result_amount> without actually performing the requested operation or charging/crediting the account. This is useful to interfaces that present the user with a confirmation page, informing them of the effect of the requested operation prior to actually performing it.