Skip to main content
Aria Knowledge Central

Release 6.43

Multi-language Translation of Attributes Enabled By Locale Settings (DEV-5574)

This feature enables multi-language translation of customer-facing product catalog elements. The language displayed is controlled by the locale setting selected in the Company Profile and in the User Profile. To add a new locale option, refer to Create Locale Settings.

Note: The product catalog and configuration elements are displayed based on the locale setting in the Company Profile. The User Profile locale is honored only in account-related modules.

Company Profile Locale Setting

Getting Here: Click Configuration > Client Settings > Company Profile

The locale is defined in the Company Profile by the Locale Field. The default locale is "System_US_English_locale".

User Profile Locale Setting

Getting Here: Click the user's name in the upper right-hand corner of the application to open the User Profile.

The locale is defined in the User Profile by the "View Account Data In" field. The default locale is "System_US_English_locale".

Translation hyperlinks

For product catalog elements that are defined in open text fields, a translation link is provided. The translation link opens a contextual menu to select a locale and define a translation for the field.

Credit Card Authorization Reversal Process (DEV-5638)

This feature supports the reversal of a credit card pre-authorization amount for the following payment gateways:

  • Chase Paymentech
  • CyberSource
  • PayPal Payflow Pro
  • Vantiv (Litle)

Performing the Authorization Reversal

Getting Here: Click Accounts > Search for an Account > Payments & Credits > Current Authorization Reversals tab

  1. Click Create a New Auth Reversal. All pending authorizations that can be reversed display.
  2. Click the Authorization ID for the authorization you want to reverse. The following screen displays:
  3. Select a Reason from the drop-down. The following options are available:
  • Account charged in error
  • Goods/Services not delivered
  • Customer dissatisfaction
  • Cancellation of pre-paid service
  • Good will
  • Overpayment/Duplicate payment
  • Wrong/undesired payment source charged
  • Other
  1. Add your comments into the CSR Comments field (Optional).
  2. Click Generate Auth Reversal.

Note: Reversals against pending authorizations may not be reflected in the account holder's balance for several days, depending on the individual rules and processes of the payment processor and issuing bank/practice.

Role-based User Authentication for Workflow Access and Customization of Workflow Navigation Button Added (DEV-5906)

This features creates two roles for Workflow access, and allows the user to assign a URL to the Workflow button in the Aria navigation bar.

Assign Workflow User Access

For Workflow users, two roles are available to assign user permissions to Workflow:

  • Workflow Designer: This role grants access to folders in which designer entities are created for end users, allows the user to create new folders, and runs Workflows as end users in the Aria Workflow portal.
  • Workflow Administrator: This role grants full access to all folders and functions in Aria Workflow portal.

Getting Here: Click Configuration > Security > Roles

Check the appropriate access for the user.

Specify a URL for the Workflow Navigation Bar

By default, the Workflow button in the left-hand navigation directs to the Workflow landing page. To customize this button to direct you to your instance of Workflow, you must configure the URL Base Domain and the Subdomain in the Workflow Settings.

Getting here: Click Configuration > Integrations > Workflow Settings

Plan Unit Instance Details in Statement (DEV-5943)

Statements have the capability to display the following details of the Plan Unit Instances:

  • Plan unit instance number
  • Client-defined plan unit instance ID
  • Plan unit instance status
  • Plan instance number
  • Plan name
  • Plan number
  • Service name
  • Service number
  • Service fulfillment status
  • Service fulfillment date

Contact Customer Service to include these details when statements are generated.

JavaScript Improvements to Rate Schedule Load Time (DEV-5994)

This improvement prevents delays and JavaScript load errors for rate schedules with plans.

Email Notification Sent to Batch Job Alert Contact and Aria Customer Support When Batch Job Fails (DEV-6075)

This feature supports sending an email notification to an assigned contact and Aria Customer Support (BCC'd) when a batch job fails for any of the following reasons:

  • Processes died before completion (Status code: 3)
  • Failed with fatal error (Status code: 4)
  • Completed, some errors (Status code: 5)
  • Did not run due to dependency failure (Status code: 6)

The email includes the following information:

  • Client ID and Client Name
  • Name of the batch job
  • Status
  • Start Time
  • End Time

The following is an example email sent for a batch job failure due to processes dying before completion.

Configure the Batch Job Alert Contact in Company Profile

Getting Here: Click Configuration > Client Settings > Company Profile

  1. In the Batch Job Alert Contact fields, enter the contact's information.
  2. Click Save.

​Cash Credit Tab User Interface Enhancements (DEV-6111)

This feature adds an easy-to-access Cash Credits tab to apply a credit that immediately reduces a customer's current outstanding balance.

Cash Credits Tab

Getting Here: Click Accounts > Select an Account > Payments & Credits > Cash Credits


Opens the Cash Credit screen to lead you through creating a cash credit.


The Credit Number link opens details for the Cash Credit, including:

  • Credit Number
  • Created By
  • Date Created
  • Amount
  • Reason
  • Comments
  • Action

The Void link allows you to void the cash credit directly from this screen. When you click Void, a confirmation window opens.

Note: Once confirmed, you cannot undo a Void.

After confirming the void, the "Actions" changes from a hyperlinked "Void" to "Voided" without a link.  

Functional Group and Collection Group Configurable When Creating an Account (DEV-6139)

The Create Account Template user interface is enhanced to specify collection account group(s) and functional account group(s) during the process of creating a customer account. When creating or editing an account template, you may enable Functional Group Configuration and/or Configure Collection Account Group for your template.

Getting Here: Click Configuration > Client Settings > Account Creation > New or Select an Existing Template

  1. Select Yes for Functional Group Configuration and/or Configure Collection Account Group.  Available groups for the account are listed.
  2. Click on the groups that you want included in the template. These groups appear in the box on the right.
  3. Click Save. These fields are included in the account creation template.

Enhanced Event Logging (DEV-4869)

Event notification logging has been transferred to a different database.  With the new database, the event log search functionality has been expanded and improved.

Note: Since the logging has been transferred to a new database, data collected before this release does not display with this current search.  To access data from before this version release (before 1/20/2016), contact

New Search Options Enabled

Getting here: Click Configuration > Audit Logs > Events

You can search Event logs using any combination of the following fields:

  • Attempt Date/Time: This is the default search field and defaults to the current date/time.
  • Account: Search for a specific account.
  • Event Class: When an event class is selected, the available event IDs for that class are made available via a dropdown.
  • Sequence Number
  • Status: The list of available statuses are as follows:
    • ​Discarded
    • Failed
    • Incomplete
    • New
    • Pending
    • Queued
    • Successful

Improved Search Results Table

After completing a search, all events within a given sequence are returned. The search results table displays the results by attempt date in descending order.

Application Fixes

  • Preview invoice button issue corrected (Ticket-8461)
  • Pro-ration option is corrected in plan unit instance removal page (Ticket-8622)
  • Contract end actions were not working for some plan statuses (Ticket-9220)
  • Deleted child plan appeared on parent plan relationships tab (Ticket-10366)
  • Tooltip was displaying when text was not long enough to truncate (Ticket-10408)
  • Usage pooling message was not correctly appearing (Ticket-10456)
  • Account ad-hoc search results screen showed archived accounts in blue instead of pink (Ticket-10458)
  • GL code was not properly displayed through UI (Ticket-10479)
  • Generic text was not populating for some surcharge rate schedules (Ticket-10643)
  • Aria was not cancelling default supplemental plans (Ticket-10675)
  • Generating invoice after changing supplemental plan status was inconsistent (Ticket-10703)
  • Event was not firing when master plan instance enters dunning (Ticket-10704)
  • Master plan status did not change to temporary plan status during account creation (Ticket-10738)
  • Unexpected error thrown when replacing master plan without same supplemental plan (Ticket-10740)
  • Internal error message was displayed in refund page (Ticket-10741)
  • Mails were not triggered when the usage count reached notification levels  (Ticket-10742)
  • Invoicing error code and error message were not displayed (Ticket-10743)
  • Child account with parent pay had wrong billing group (Ticket-10768)

API Features

Multi-language Translation of Attributes Enabled By Locale Settings (DEV-5574)

Existing APIs have been enhanced to provide translation capability to product catalog elements. See below for the product catalog modules that now have multi-language support.

Component Fields APIs
Plans Name
Rate Schedule Name
Rate Tier Description
Non-subscription Offering Name
Subunit label
Usage Types Name
Display Name
Services Service Name update_service
Surcharges Name
External Description
Rate Schedule Name
Rate Tier Description

get_surcharge_details  get_surcharges

Coupons Description
Coupon Message


Discount Rules Name
External Description


Promotions Description


Credit Card Authorization Reversal Process (DEV-5638)

This feature introduces the following APIs.

API Description


This API enables reversal of credit card authorizations.


This API returns a list of the reversible authorizations for an account.

Processing guidelines and rules for authorization reversals vary by payment processors. These APIs have been developed to be used with the following payment processors that support full authorization reversals:

  • Chase Paymentech
  • CyberSource
  • PayPal Payflow Pro
  • Vantiv (Litle)

Associated Error Messages

You receive an error message when using this API if any of the following conditions apply:

  • The requested authorization you are trying to reverse is more than 72 hours old.
  • If the given auth_no or proc_auth_id is not valid, does not exist, or has already been reversed on the account.
  • If total_reversal_amount is not greater than zero and less than original authorized amount.

Add/Update Number of Plan Unit Instances and Plan Unit Instance Fields Concurrently (DEV-5915)

This API enhancement supports updates to Plan Unit Instances and Plan Unit Instance Fields in a single API call when the “Enable Plan Unit Instances” parameter is set to “True.”  For example, a client can now add and/or update the number of Plan Unit Instances and set the associated Plan Unit Instance Fields at the same time.

To enable this enhancement, the following input parameters have been added to the create_acct_complete_m and update_acct_plan_multi_m APIs:

  • plan_unit_inst_services
  • service_no OR client_service_id
  • service_fulfillment_date
  • fulfillment_directive
  • plan_unit_inst_fields
  • field_name
  • field_value
  • plan_unit_inst_directive

Additionally, the update_acct_plan_multi_m internally supports adding this enhancement to the following APIs through the use of the plan_directive parameter:

  • assign_acct_plan_m (plan_directive = 1)
  • replace_acct_plan_m (plan_directive = 2)
  • update_acct_plan_m (plan_directive = 3)
  • cancel_acct_plan_m (plan_directive = 4)

Tokenization of Credit Card Numbers (DEV-5986)

The following APIs have been created to generate Universal Unique Identifier (UUID) for credit card numbers.

API(s) Description
These APIs use the billing sequence number as the input to generate the UUID for the credit card number.
These APIs use the account number as the input to generate the UUID for the credit card number attached to the account.
These APIs use the credit card number as the input to generate the UUID for it.

APIs Created for Cash Credit Functionality (DEV-6111)

API(s) Description
get_cash_credits_details_m This API provides the details of the invoice line details to which a given cash credit has been applied by using account or account’s specific transaction.
apply_cash_credit_m This API applies a cash credit to a specified account.

Additional Keys of Payment Method and Account Status Added to Query for get_account_details_m  API (DEV-6202)

Additional query keys for payment method and account status have been added to improve the search function.

API Fixes

  • cancel_instance_contract_m API threw unexpected error when an existing contract on the account is already cancelled (TICKET-8928)
  • get_avail_plans_for_acct_m/get_avail_plans_for_acct_all_m APIs did not honor include_full_plan_hierarchy_plans field values (TICKET-9529)
  • API response to get_client_plans_all_m reduced (TICKET-10164)
  • bulk_record_usage_m throws errors for input variables master_plan_instance_id and client_master_plan_instance_id (TICKET-10377)
  • No value was displayed in acct_balance field when account balance is zero (TICKET-10529)
  • Date format was wrongly displayed in the dunning_degrade_date in get_acct_plans_m (TICKET-10567)
  • modify_acct_universal_contract API was incorrectly setting the start date of the contract (TICKET-10570)
  • modify_acct_universal_contract API is setting the start date of the contract to even before the account retroactive start date (TICKET-10570)
  • Tilde(~) symbol was not accepted for fields in the update_contact_m and update_acct_complete_m APIs (TICKET-10621)
  • Removing account plan custom rates was not adding an entry in plan history (TICKET-10642)
  • create_acct_complete_m accepts bad parameters and returns error_cd 0 without creating an account (TICKET-10705)
  • replace_acct_plan_m API was only updating master plan instance status in plan_instance table and not in plan_instance_master table (TICKET-10709)
  • replace_acct_plan_m API was not updating the master plan instance status in some tables (TICKET-10709)
  • Value displayed against nullable attribute for client_acct_id field in get_refundable_payments_m API corrected (TICKET-10722)
  • get_plan_details_m did not correctly display multiple rate schedules (TICKET-10729)
  • update_acct_plan_status_m API issue resolved with dunning step (TICKET-10731)
  • new_invoice_no node is not added under manage_pending_invoice_m API output arguments (TICKET-10776)
  • acct_no and client_master_plan_instance_id nodes are not added under get_pending_invoice_no_m API output arguments (TICKET-10779)
  • master_plan_no and master_plan_name nodes are not added under get_invoice_history_m API output arguments (TICKET-10813)
  • cancel_acct_plan_m failed (TICKET-10815)
  • When taxable NSO items are passed to assign_acct_plan_m during master plan assignment there were no line items related to NSOs in the invoice (TICKET-10830)
  • Unexpected error when nso_bill_immediately = 1 in assign_acct_plan_m API (TICKET-10831)
  • Prorated invoice is not generated for the new assigned master plan in assign_acct_plan_m response (TICKET-10836)
  • cancel_queued_acct_plan_change_m API doesn’t cancel the queued plans (TICKET-10858)
  • get_unapplied_service_credits_m API is not returning the credits when master plan instance no is not passed (TICKET-10880)
  • Create_order_with_plan_m API is throwing unexpected error (TICKET-10883)
  • Unexpected error is thrown on giving client_acct_id instead of acct_no on void_invoice_m API (TICKET-10905)
  • Replaced plan units are not updated in the generated invoice via replace_acct_plan_m API (TICKET-10907)
  • Unexpected error occurs while submitting the update_acct_plan_unit_instance_m request without filling plan_unit_inst_no field  (TICKET-10937)

  • Was this article helpful?