Search the Aria Knowledgebase for
User Documentation, APIs, SDKs, and more!



 

Home > Aria6 User Documentation > Aria6 Release Notes > Aria6 Release 11.0

Aria6 Release 11.0

Overview

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

Release Date

Stage Future Release Date

 5/9/2017

System Requirements

Supported Browsers

  • Firefox 39
  • Chrome 44
  • Internet Explorer 9, 10, 11 

Java Settings

Java 7.0​​

Screen Resolution

1024 x 768 or higher

Application 

Features

Fixes

List of Application Fixes

API

Features

Fixes

List of API Fixes

Application Features

Purchase Power/Reserve Account Validation Removal (DEV-7921)

This feature removes validation of the Reserve Account Number and Purchase Power Number fields, to allow entry of alphanumeric strings in these fields.

Getting Here: Click Accounts > Search for and select an account > Payments & Credits > Form of Payment

When you select Purchase Power as the payment type, the Purchase Power Number field is no longer validated and can be an alphanumeric string.

When you select Reserve Account as the payment type, The Reserve Account Number field is no longer validated and can be an alphanumeric string.

A sample screen with the Purchase Power Number field is shown below. No change to the UI has been made for this enhancement.

 

Chase Paymentech Soft Descriptors (DEV-8072)

The Chase Paymentech payment gateway now supports the use of soft descriptors. Soft descriptors are an additional text field that can be specified when configuring a payment gateway. The value in this field can appear on credit card statements to replace the configured client name. This can be useful if a client has several businesses. For example, ABC Enterprises might want "ABC Hardware" to appear on their account holder statements.

The soft descriptor fields can be specified at the payment gateway and on any collection group assigned to the Chase Paymentech payment gateway. The fields are as follows:

  • Soft_descriptor: Description that appears on the account holder's statement
  • Soft_descriptor_customer_service: City or customer service phone number that appears on the account holder's statement.

Configure Soft Descriptors at the Payment Gateway

Getting Here: Click Configuration > Payments > Payment Gateways > New > Chase Paymentech

The Chase Paymentech Create New Payment Gateway screen displays with the Soft_descriptor and Soft_descriptor_customer_service fields available in the Options section.

Configure Soft Descriptors at the Collection Group

Getting Here: Click Configuration > Collection Groups > New

Any collection group assigned to the Chase Paymentech payment gateway displays with the Soft_descriptor and Soft_descriptor_customer_service fields available in the Advanced Options section.

Paymetric Payment Processor Moneris(CAD) Enhancement (DEV-7920)

The Paymetric payment gateway now supports the Moneris processing bank cartridge for Canadian currency (CAD) transactions. Note that any clients who want to configure Moneris as their cartridge must specify this when they set up their collection group for this payment gateway.

Surcharge Enhancements (DEV-8241)

This feature enhances how surcharges are created and changes how they are processed. Surcharges associated with a payment method or payment term are now calculated before taxes are applied and are then taxed with any other taxable charges. Surcharges can now be included in credit memos and rebills.

Additionally, the Create a Surcharge screens have been modified to enhance usability.

Creating a Surcharge

Getting Here: Click Products > Surcharges

  1. Upon accessing the Surcharges screen, a list of existing surcharges displays.

CreateSurchargeEOM1.png

  1. Click New. The Create New Surcharge screen displays.
 

Notes:  

1) Fields that are marked by a red asterisk are required. Be sure to enter values in all required fields on all tabs or you won't be able to save the surcharge.

2) The Translations link enables defining a translation for the field for an associated locale. Refer to Multi-language Translation for Product Elements for more information.  

 Surcharge Name Indicates the name of the surcharge.

Client Defined Identifier A unique ID for the surcharge that you can define for future reference. If you
do not enter an ID in this field, the application defaults this value as the surcharge
name with underscores.

Description Provides a description of the surcharge. This is for internal purposes and is not visible to your customers.

External Description The description of the surcharges that your customers see on their statements.

Application Scope

Defines the plans and charges to which the surcharge applies. By default, if a plan is not selected, the surcharge is applied to all plans and services.
Available options include:

  • All Charges
    ​Surcharge is calculated for all charges on the invoice, including all services, charges, and inventory items.

  • All Plan Charges, All Plans
    Surcharge is calculated for all plan charges on the invoice.

  • All Plan Charges, Specified Plans
    Surcharge is calculated for all charges that belong to specific plans as chosen in the surcharge definition.

  • ​All Plans, Specified Service Charges
    Surcharge is calculated for the services that are specified in the surcharge definition.

  • Specified Plan/Service Charges
    Surcharge is calculated for the combination of services and plans that are specified in the surcharge definition.

  • All Recurring Service Charges
    Surcharge is calculated for all the recurring services on the invoice.

  • All Usage Service Charges
    Surcharge is calculated for all usage services on the invoice.

  • All Activation Service Charges
    Surcharge is calculated for all activation services on the invoice.

  • All Item Charges
    Surcharge is calculated for all one-time item services on the invoice.

  • Specified Item Charges
    Surcharge is calculated only for the items that are specified in the surcharge configuration.

  • Payment Method
    Surcharge is available to be applied to a payment method. Note that, for this selection, the surcharge is calculated on the pre-tax total. For details, see Add a Payment Method.

  • Payment Term
    Surcharge is available to be applied to a payment term. Note that, for this selection, the surcharge is calculated on the pre-tax total. For details see Add a Payment Term.
Apply to Invoice

Allowable values are as follows:

  • Before Discounts: Surcharge amount is discounted when a discount applies to the account.
  • After Discounts: Surcharge is not discounted. Surcharge amount is applied after a discount to the account is calculated.

Present the surcharge as a separate invoice line Indicates how the surcharge is displayed on the invoice. A surcharge can be included with the original line item, or it can be added to the invoice as a separate surcharge line item.

8.png

Tax Group

 Defines the tax group used for calculating taxes against the surcharge. This field only displays if Present the surcharge as a separate invoice line is checked. Surcharges are always applied on pre-tax amounts unless the price is tax-inclusive. In this case, you must ensure that the surcharge applies only to tax-exclusive items, or double taxation occurs.
Revenue Account GL Code Indicates the revenue account general ledger code for the surcharge. This field only displays if Present the surcharge as a separate invoice line is checked.
Account Receivable GL Code Indicates the account receivable general ledger code for the surcharge.
Rate Calculation Method Indicates whether the surcharge fee is a fixed amount or a percentage of the invoice charges. The fee is calculated as the net line item total for the selected services.

Rate Schedule Name

Enter a name for the rate schedule.

Currency Enter the currency type (e.g. USD, CAD...etc.)

Minimum Surcharge to Apply Specify the minimum surcharge to apply. This amount is charged if the rate tier calculation is lower than this amount.

Rate Tiers

Provide the information for the rate tier. If the Description field does not display, set the Use Rate Tier Descriptions parameter to True (Configuration > Client Settings > Miscellaneous Settings).

Click the Add Rate Schedule button to have multiple rate schedules.

Include zero in rate tier If Yes is selected, zero value is considered in the rate tier. If No is selected, zero value is excluded from the rate tier.

Upon defining the surcharge, click Save. The surcharge is created and displays in the list view on the Surcharges screen.

Application Fixes

  • Rate Schedule interval was not displaying correctly on plan selection page (TICKET-14441
  • Write-off data was incorrect when the invoice had a coupon (TICKET-13693)
  • Taking usage units to negative or zero balance did not fire the "under" event (TICKET-14159)
  • 'All Service Rates' tab was still highlighted and selected when changing pages (TICKET-14228)
  • Microstrategy failed to login if username is email (TICKET-14242)
  • "Void this Invoice and Discard Usage" was appearing twice (TICKET-14420)
  • Was unable to set the same 'Days Until Due' value on Payment Method and Collection Account Group  (TICKET-14521)
  • Corrected billing reset issues (TICKET-14594)

API Features

Chase Paymentech Soft Descriptors - API (DEV-8072)

The Chase Paymentech payment gateway now supports the use of soft descriptors. Soft descriptors are an additional text field that can be specified when configuring a payment gateway. The value in this field can appear on credit card statements to replace the configured client name. This can be useful if a client has several businesses. For example, ABC Enterprises might want "ABC Hardware" to appear on their account holder statements.

The soft descriptor fields can be specified at the payment gateway and on any collection group assigned to the Chase Paymentech payment gateway. The fields are as follows:

  • <Soft_descriptor>: Transaction description shown on the buyer's statement that displays a Merchant Name or Item Description typically. This field is ignored if not supported/certified by the payment processor.
  • <Soft_descriptor_customer_service>: Transaction description shown on the buyer’s statement that displays a city for card-present transactions or a phone number for card-not-present transactions.  This field is ignored if not supported/certified by the payment processor.

The <soft_descriptor> field is an existing input field on several APIs. The <soft_descriptor_customer_service> field is a new input on the same set of APIs. Specifying either of these fields on an API overrides the value specified at the payment gateway or collection group. You can specify a value in either of these fields for accounts assigned to either the Chase Paymentech payment gateway, or any other payment gateway that supports soft descriptors.

Field Name Field Type Max Length Description
soft_descriptor_customer_service String 13 Transaction description shown on the buyer’s statement that displays a city for card-present transactions or a phone number for card-not-present transactions.  This field is ignored if not supported/certified by the payment processor.

APIs that use the <soft_descriptor> and <soft_descriptor_customer_service> fields are as follows:

Purchase Power/Reserve Account Validation Removal - API (DEV-7921)

This feature adds two new fields to update_payment_method that are used with the Purchase Power and Reserve Account payment methods. The <bill_agreement_id> field stores either the Purchase Power Number, the Reserve Account Number, or the token number of a tokenized credit card. The <cc_id> field provides consistency with other payment-related API calls. Details of the fields are as follows:

Field Name Field Type Max Length Description
bill_agreement_id string 32 Unique ID of the bill agreement (also referred to as a token)
cc_id long 2 A numeric code indicating the type of credit card

Get_all_client_receipt_ids Updated to Include Receipts from Usage APIs - DEV-8055

The get_all_client_receipt_ids API now includes the client-level receipt IDs created for multiple accounts using the bulk_record_usage  API and account-level receipt IDs created for an account using the record_usage API.

API Fixes

  • The set_company_profile API was not performing correctly (TICKET-13732)
  • Typo in description for "Auto-Void Order On Electronic Collection Failure" client parameter (TICKET-14172)
  • Error was generated when existing <client_service_id> was mapped with supplemental plan (TICKET-14346)
  • The create_acct_complete API was not saving collection account group (TICKET-14361)
  • In API Live, the get_payments_on_invoice was missing mandatory field designation (TICKET-14389)
  • Updated query improvements in AdminTools_Role_Nav (TICKET-14391)
  • The get_catalog_hierarchy_m API was timing out (TICKET-14421)
  • Product fields were not displaying for read-only user roles (TICKET-14472)
  • Typo corrected in issue_refund_to_acct (TICKET-14603)
  • Updated create_order API (TICKET-14604)
  • Update_coupon was throwing error (TICKET-14660)
  • ObjectQuery API was failing due to redundant code (TICKET-14668)
  • Passing locale name in API call was returning an error (TICKET-14672)
Last modified

Tags

This page has no custom tags.

Classifications

This page has no classifications.
Powered by MindTouch ®