Home > Aria6 User Documentation > Aria6 Release Notes > Aria6 Release 6.38

Aria6 Release 6.38

Release Date

Production

9/16/2015

Aria6 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

Aria6 Features  

Make "Default For Payment Method Removals" Configurable (DEV-5216)

This new field, Default for Payment Method Removals, enables you to specify the type of payment method that an account defaults to when its primary payment method is removed and no account-level backup payment method is specified.

Setting a Backup Payment Method

Getting Here: Click Configuration > Payments > Payment Methods > Select a payment method.

You can select the default payment method if the primary payment method is removed from the account. Use the drop-down menu to select an available payment method to use.

A new payment method is determined as follows:

  • If a backup payment method is specified on an account, that becomes the new primary payment method.
  • If no backup payment method is specified on an account, then the contact information is copied from the removed primary payment method, and the new primary payment method is created based on the value in the Default for Payment Method Removals drop-down.

EOMPymtMethod.png

Apply Surcharge to Payment Method (DEV-5249)

This feature allows you to create a surcharge that you can assign to a specific payment method.

Create a Surcharge for Payment Methods

Getting Here: Click Products > Surcharges > Create New Surcharge > Application.

The Create New Surcharge screen now has an added option in the Scope drop-down menu: Payment Method. Selecting this option makes this surcharge available when you define a payment method.

ApplySurchargeToPymtMethod1.png

Applying a Surcharge to a Payment Method

Getting Here: Click Configuration > Payments > Payment Methods > Select a payment method.

  1. From the Select Discount or Surcharge drop-down, select Surcharge.
  2. Select a surcharge from the drop-down menu. Only surcharges that have a scope of Payment Method are available.
  3. Click Save to apply the surcharge to the payment method.

ApplySurchargeToPymtMethod2.png

Ability to Restrict SSO-Enabled Users from Changing Their Password in the UI (DEV-5196)

Clients who use single sign-on with the UI can now restrict users from changing their password within the UI. Instead, when users attempt to reset their password, they see a message directing them to a client-specified URL.

This restriction is available only if the user is associated with just one client.

Restricting SSO-Enabled Users from Changing Their Password in the UI

Getting Here: Click Configuration > Security > UI Access.

UIAccess.png

Select a value from the drop-down menu:

  • No: Allow users to reset their passwords using the UI.
  • Yes: edirect users who want to reset their passwords to a client-specified URL.

When you select Yes, the Redirect URL field displays. Enter the URL that you want users to see when they try to reset their passwords in the UI.

Plans Screen Additional Sorting and Viewing Capability (DEV-5221)

The Plans screen now provides the ability to sort each column, filter certain columns, and to show and hide columns. An additional view allows you to view the master and supplemental plans as a hierarchy, displaying the relationships between the plans.

List View

The list view of plans is the default view. It has the following features:

  • Master/Supplemental Plan Icons: An M or an S in the first column identifies each plan as either a master plan or a supplemental plan.
  • Sort By Column: By clicking the up/down arrows by each column name, you can sort the display by the values in that column.
  • Search a Column: In addition to being able to search all values in all plans, you can use the search box just below each column name to find values just within that column.
  • New Columns: The following new columns are available for display:
    • Currency: The money system of the country where the plan is billed.
    • Rate Schedule Count: The number of rate schedules associated with the plan.

BPlanView1.png

  • Filter Columns: The Billing Interval, Currency, and Status columns allow you to filter the displayed plans by the values in these columns. Click the up/down arrows in the box below the column name to see the values you can use to filter the list.

BPlanView2.png

  • Show/Hide Columns: The Show/hide columns menu in the upper right corner allows you add and remove columns from the plan display by checking or unchecking the column name in the menu.

BPlanView3.png

Hierarchy View

The hierarchy view displays master plans and supplemental plans in a tiered structure, making it easy to see which supplemental plans belong to which master plans. To switch to the hierarchy view, click the icon in the header bar of the Plans screen, as shown below.

BPlanView4.png

The Plans screen then displays the hierarchy view.

PlanView5.png

You can click the arrow next to any plan name to see the master plan and supplemental plans within it.

PlanView6.png

Minimum Threshold Amount for Statement (DEV-3838)

This feature enables you to set a minimum amount that must appear on a statement before it is sent to an account. You can set this value at both the client and account levels.

Client-Level Minimum Threshold

Getting Here: Click Configuration > Billing > Currencies > Select a currency.

By default, there is no minimum statement amount specified for a client. To specify one, use the following fields:

  • Do not send statements when the balance due is less than a specified amount: Click this checkbox if you want to specify a minimum amount for a statement.
  • Minimum Statement Threshold: Enter the lowest amount that causes a statement to be produced. This must be less than the amount in the Minimum Dunning Threshold field.
  • Maximum Number of Statements to Defer: After the number of statement cycles you specify here, a statement is sent even if the amount does not meet the minimum statement threshold.
  • Apply to Anniversary Statements Only: Check this box if you want these values to apply only to regularly generated statements on the account's anniversary date, and not to manually generated statements.

 MinStatementThreshold1.png

Account-Level Minimum Threshold

You can set a minimum statement threshold at the account level.

Getting Here: Accounts > Select an account > Statement Template > Edit

MinStatementThreshold3.png

This feature includes a new Statement Details screen. The Statements view, along with the Statement Detail screen below, displays Date Sent and Status. Users can click Send Statement to either send the statement initially or resend it if necessary.

MinStatementThreshold2.png

Usage Pooling and Usage Unit Thresholds Can Be Set on Plans In Active and Pending Status (DEV-4656)

Usage thresholding, based on plan units, can be assigned at the plan/service level unless you are using Usage Pooling, when the threshold must be set at the account level. When a mid-period plan change is made, the plan that is being added to an account is put into an Active Pending status until the designated date. (Next Anniversary Bill Date or Future Date). You can now specify usage pool and threshold information on active pending plans to accommodate a mid-period plan change.

Getting Here: Click Accounts > Select an account > Plans and Services > Usage Pooling

UsagePooling.png

For each plan, you can do the following:

Select a Usage Pooling value from the drop-down list:

  • Enabled: Usage pooling applies to this plan.
  • Disabled: Usage pooling does not apply to this plan.

Select a Unit-Based Usage Thresholds value from the drop-down list:

  • Set at the usage pool level: Thresholds are set based on usage pool.
  • Set individually by usage type: Thresholds are set by usage type.

Configuration Setting for Accounts Moving from Non-Billable to Billable Status (DEV-5296)

A new configuration setting allows you to specify what charges appear on an invoice when an account moves from non-billable to billable status.

Getting Here: Click Configuration > Billing > Invoice Settings > Invoice Behavior for Accounts Moving from Non-Billable to Billable Status

Select one of the following options from the drop-down menu.

  • Recurring charges only: Only recurring charges appear on the first invoice after the account becomes billable. Usage charges appear on subsequent invoices.
  • Recurring and usage charges: Both recurring and usage charges appear on the first invoice after the account becomes billable.

InvoiceSetting2.png

Statement Sending Settings Combined on New Page (DEV-4665)

This feature consolidates the settings used to configure when a statement is sent. The new page contains configuration options for existing client parameters and also allows configuration of each of the transaction types that can be viewed on a statement.

Getting Here: Click Configuration > Notification > Statement Sending.

StatementSending.png

 Aria6 Fixes   

  • Account-Level Supplemental Fields Could Not Contain "#" in their Names (TICKET-7965)
  • ​Unapplied Service Credit Value Was Not Displayed in Credit Section (TICKET-8018)
  • Could Not Change the Tax-Inclusive Rate on an In-Use Supplemental Plan (TICKET-8772)
  • Dunning Process Lost Payment Method Assignment When Plan Was Copied (TICKET-8919)
  • BillSoft Tax Logging Only Included the Most Recent Request (TICKET-8999)
  • Unexpired Service Credits Were Canceled During Batch Processing (TICKET-9059)
  • Paymentech Account Updater Was Not Sending Batch Jobs (TICKET-9164)
  • Imported Client Data Contained Unexpected Special Characters (TICKET-7129)
  • Source Information For Client Write-offs Displayed Incorrectly (TICKET-7449)
  • Net Proration Appeared on Invoice Instead of Prorated New Charge (TICKET-8098)
  • Create Account Template Did Not Allow <Alt_Bill_Start_Date> and <Alt_Bill_Day> (TICKET-9038)
  • Supplemental Plan Lost Rates When Plan Status Was Updated (TICKET-9190)
  • Direct Post Did Not Honor <Alt_Caller_Id> (TICKET-9449)
Last modified

Tags

This page has no custom tags.

Classifications

This page has no classifications.