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

 

Home > User Documentation > Aria6 Release Notes > Aria6 Release 10.0

Aria6 Release 10.0

Overview

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

Release Date

Stage Future Release Date

 2/2/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

API

Features

Fixes


Application Features

Applying a Discount to an Account for Extended Durations (DEV-7912)

This feature changes the the maximum number of months that a discount can be applied to an account to 999. This value is available when the user selects Months from the Duration option. Allowable values are 1 to 999.

Note: The API portion of this change was implemented as part of Applying a Discount to an Account for Extended Durations - API).

Getting Here: Click Marketing > Discount Rules > New


Expanded Range of Adjustment Dates for Adjusting Bill Dates (DEV-7146)

This feature expands the allowable range you can use to adjust a bill date. Allowable values are as follows:

Billing Status of Plan Permissible Values for adjustment_days
Plan previously billed Up to 27 days before or after the current billing date
Plan not previously billed Up to 99 days prior to the current billing date or up to 27 days after the current bill date (-99 days to +27 days)

These ranges apply whether inputting a date or specifying days in the Adjust Account Billing Dates screen. 

Adjust an Account's Billing Dates

Getting Here:  Click Accounts > search for and select an account > Account Billing Dates Tab

  1. Click Adjust Account Billing Dates.
  2. From the Date Adjustment drop-down, select one of the following:
  • Move Forward: Allows you to specify the number of days to move the billing date forward.
  • Move Backwards: Allows you to specify the number of days to move the billing date backward.
  • Set Date: Allows you to specify a new billing date.

 Note: The adjustment date cannot exceed 27 days before or after the current next billing date unless the plan hasn’t been billed previously. If the plan hasn’t been billed previously, the bill date can be set up to 27 days in the future or 99 days in the past.

  1. If you selected Set Date, enter the Adjustment Date for the new billing date.

  1. If you selected Move Forward or Move Backward, enter the number of days to adjust the current billing date.  

  1. ​​​​​In the CSR Comments field, enter any applicable comments about the billing date adjustment.
  2. Click Adjust Dates.
  3. Review your changes to the billing dates.
  4. To save your changes, click Adjust Dates. The customer is billed on the applicable dates, based on the change that you specified.

Enhanced Web Service API Audit Logs and Reports (DEV-7212)

This feature enhances the functionality of the Audit Logs and reports for Web Service APIs. The search now supports:

  • Searching for a Session ID
  • Comparing the details, input, and output parameters of up to 5 APIs
  • Exporting the results of individual API details or multiple API comparisons to a downloadable CSV file
  • Displaying all filters by default, including:
    • Request Date/Time
    • API Name
    • Account Number
    • Calling IP
    • Error Code
    • Session ID

Web Service API Audit Logs

Getting Here: Click Configuration Audit Logs Web Service API

  1. Enter information for any of the fields to search by that parameter.
  • Request Date: The date on which the API call was made to Aria.
  • API Name: The name of the API call that was made to Aria.
  • Account Number: The account number of the customer whose information was updated or retrieved by the API call.
  • Calling IP: The IP address from which the API call was made.
  • Error Code: The error code returned by the API call.
  • Session ID: An Aria-assigned unique identifier for the instance of the API call.
  1. Click Search. Information about API calls display in the following columns:
  • API Name: The name of the API call that was made to Aria.
  • Request Date: The date on which the API call was made to Aria.
  • Elapsed Seconds: The number of seconds that the API call took to complete its task.
  • Account Number: The account number of the customer whose information was updated or retrieved by the API call.
  • Receipt ID: The receipt ID that was passed into the API call (if any).
  • Error Code: The error code returned by the API call.
  • Error Message: The error message returned by the API call.
  • Calling IP: The IP address from which the API call was made.
  • Caller ID: Any additional value that you chose to pass into an API call.
  • Session ID: An Aria-assigned unique identifier for the instance of the API call.

1.png The parameters you searched for display here.
2.png Click Refine Search to update the search parameters.

3.png

The Compare APIs button. To compare 2 to 5 APIs: 

  1. Check the checkbox next to each applicable API. You can check up to 5 APIs.
  2. Click the Compare APIs button. A screen displays with tabs for Details, Input Parameters and Output Parameters.

Details

Input Parameters

Output Parameters

  1. To download the comparison as a CSV file, click Export for each tab
4.png

To view the details of a single API call, click the API name. The details display, including tabs for Details, Input Parameters and Output Parameters.

To download the API call details as a CSV file, click Export for each tab.


Implement Full-Formed URLs to Support Azure AD/SAML Integration (DEV-7967)

This feature introduces a new parameter that the client can pass to connect with the Aria UI to allow logins to occur from Azure environments. The parameter, <forceentityid>, can contain a fully-formed URL that points to the Aria UI. If this parameter is present, the Aria UI prioritizes it and allows a login to occur with this passed entity ID rather than the default.

Previously, clients using single sign on from within their UIs could only direct users to the Aria UI using entity ID values that did not use fully-formed IDs. This was not supported with Azure AD/SAML integrations.

 

Improvement to TNS Payment Processor (DEV-8048)

This enhancement makes the credit card type (Visa, MasterCard, etc.) available for display for clients using the TNS payment processor. The credit card type can now appear on the account overview page, statements and invoices, and on reports configured by Aria Customer Support.



Modified Credit Calculation for Tax Inclusive Services (DEV-7857)

This feature enhances credit calculation due to plan cancelation to ensure that taxes are credited on the invoice if the service was tax-inclusive.


Print Invoice Button Not Displaying in Chrome (DEV-8018)

This feature modifies the Aria UI so the Print button displays properly when printing invoices using the Chrome browser.

Getting here: Click Accounts > Search for and select an account > Statements & Invoices > Invoices >
Select an invoice > View and Print


Updated Payment Gateway Names (DEV-6479)

The names of the payment gateways have been updated to ensure names match current company standards, appropriate capitalization and to display in alphabetical order. No changes to functionality have been made. 


Prorated Taxes for Service Credits Applied Based on Client Parameter (DEV-4425)

This feature enables the application of prorated tax service credits when the Proportional Allocation of Service Credits client parameter is enabled. Previously, the Proportional Allocation of Service Credits parameter prevented the application of tax-only service credits.

Note: Refer to Change an Invoice Setting to enable the Proportional Allocation of Service Credits parameter.

Service credits that apply to services other than tax-only services continue to apply prior to tax calculations when the Proportional Allocation of Service Credits client parameter is enabled.


Enhancement of View-only CSR level and Page Restrictions in the Account Access Module (DEV-8019)

The available configurations for controlling access to the user interface have been expanded on the Account Access > Pages tab for each module. The Pages tab sections have been updated to include all pages and action links (for example, a link to Change Master Service Plan) within Accounts. 

Note: Account Access assigns a CSR-level to pages and links in the interface. The CSR-level then must be assigned to a role. Refer to Security for more information about configuring Account Access, creating and assigning roles to users.  

In addition, the View-only CSR level has been updated to remove any edit access from any section and to only allow view access for the following sections: 

  • Plans & Services
  • Payments & Credits
  • Statements and Invoices
  • Usage

Note: If View-only CSR level user access is given access to an action link, the View-only CSR user can use the action link. For example, if access is given to the Change Master Service Plan link, the user can remove a plan from the account. 

Examples for Controlling Display of Pages and Action Links by CSR Levels

CSRs can see pages or action links assigned to their level or any CSR level below. For example, if the user is a Basic CSR and the action link has a View-only CSR level, then the link or page is visible for the Basic CSR user. However, if a link has a Basic CSR level, the link is not visible for a View-only User.

For example, a Basic CSR is assigned access to the Change Master Service Plan link:

A user with the View-only CSR level does not see the Change Master Service Plan link, but a Basic CSR or higher level does. Note that the Assign New Rates link is assigned to a View-only CSR level, so this link displays for the Basic CSR and for the View-only CSR. 

Basic CSR or Higher CSR Level

View-Only CSR

Configure Account Access

Getting Here: Click Configuration > Security > Account Access > choose a section > Pages tab

Note: In this example, the Plans & Services section has been selected. 

  • Each page has a Minimum CSR Level drop-down to assign access. This grants access for the selected CSR level and those with higher levels of access to view the pages and/or action link.
  • The available Viewable links in this section have been expanded to include all options for each page.  

  1. Select the appropriate Minimum CSR Level access for each option. For example, if Basic CSR is chosen for the Future Plan Changes Page, any level above and including Basic CSR can also view the page.  
  2. Click Save. The Account Access has been updated for each option. 

Application Fixes

  • Print Invoice Button Not Displaying in Chrome (DEV-8018)
  • Error message was displayed while importing configuration (TICKET-5285)
  • Copy Configuation was not including service-level Revenue Recognition settings (TICKET-13092)
  • Network error occurred when changing password in the UI (TICKET-7074)
  • Litle collection account group was not saving SFTP Account parameter (TICKET-13353)
  • Configuration imports were failing for some service locations (TICKET-13462)
  • Event 346 was not triggered (TICKET-13239)
  • Unable to void parent balance transfer (TICKET-13292)
  • Unable to Access "Adjust Billing Dates" in the UI (TICKET-13791)
  • Generate Invoice link of Invoices tab for clients was pointing to the wrong process (TICKET-13890)

API Features

Applying a Discount to an Account for Extended Durations - API (DEV-7912)

This feature enhances the create_discount_rule API by changing the the maximum number of months that a discount can be applied to an account to 999, and by changing the maximum length of the field to 3 characters.

Updated Field

Req Field Name Field Type Max Length Description
No max_applicable_months int 3 Specifies the duration of the discount in months. Allowable values are from 1 to 999.

Bulk Collection Support (DEV-7405)

This feature allows you to collect from multiple accounts using one API call.

A new API, settle_account_balance_bulk, implements this feature. This API allows for the batch submission of up to 5,000 accounts to a payment processor for collection attempts on each account. The maximum number of records permitted in this API call is determined by the client parameter MAXIMUM_RECORDS_ALLOWED_IN_A_BULK_SETTLE_API_CALL and is set by Aria Customer Support.

This API does not update accounts in real time. The supplied accounts are added to a flat file that is submitted to the payment processor. After the required collection attempts, a response file is sent back to Aria and the associated accounts are updated.

This API is only supported by Vantiv. This API does not function with other payment processors.

Inputs for this API are as follows:

Field Name Required Field Type Length Description
<client_no> Y long 22 Aria-assigned unique identifier indicating the Aria client providing service to this account.
<auth_key> Y string 32 Aria-assigned unique key to be passed with each method call for authenticating the validity of the requestor.
<account_info> N array   Array that allows for multiple account submissions for account balance settlement.
<acct_no>
or
<client_acct_id>
N long
or
string
22 Aria-assigned account identifier. This value is unique across all Aria-managed accounts.
Client-assigned identifier for the account.

Outputs for this API are as follows:

Field Name Field Type Description
<error_code> long Aria-assigned error identifier. "0" indicates no error has occurred.
<error_msg> string Description of any error that occurred. If no error occurred, the returned message is "OK".

Updated Returns for collect_from_account and manage_pending_invoice APIs When No Collection is Attempted (DEV-7543)

Two APIs have been updated to improve support for accounts where no collections are attempted when the API runs. The new <collection_errors> hash allows for backward compatibility with existing <error_code> and <error_msg> outputs for these APIs, which are unchanged.

The affected APIs are:

The new <collection_errors> hash is populated when the API successfully runs, returning an error_code of 0, but no collection occurs. The values in the hash are as follows:

<collection_error_code> <collection_error_msg>
4033 Current form of payment is non-electronic. No collections were attempted.
4034 Collection Amount less than Currency Threshold. No collections were attempted.
4035 Collection Amount is zero. No collections were attempted.
8010 Collection attempted, email address not valid or missing.

Expanded Range for Adjustment Date for adjust_billing_dates API (DEV-7146)

This feature expands the range of permissible values for the adjustment_days and the adjustment_date input of the adjust_billing_dates API. Permissible values are as follows:

Billing Status of Plan Permissible Values for adjustment_days or adjustment_date
Plan previously billed Up to 27 days before or after the current billing date
Plan not previously billed Up to 99 days prior to the current billing date or up to 27 days after the current bill date (-99 days to +27 days)

Note: The input of adjustment_date or adjustment_days is set by the action_directive input of the API.

If the date or number of days specified in the adjustment_days or adjustment_date input is outside of the permissible range, an error message displays. 


API Fixes

  • Issue_refund_to_acct API  with do_write = 'False' was creating an account comment that a refund was issued (TICKET-12985)
  • Configuring tax settings in UI was preventing saving a start date (TICKET-12920)
  • Client_no displayed an extra time in get_order_details API response (TICKET-8303)
  • Update_usage_type API incorrectly returned the Exception Class object with the response (TICKET-13032)
  • Promotional Plan Set API return type mismatched with Developer Central (TICKET-13395)
  • Assign_supp_plan_multi was applying discounts incorrectly (TICKET-13279)
  • Accounts created with a retroactive start date were unable to generate invoices (TICKET-13621)
  • Invalid rate structure was created when tier details were not passed for a recurring service (TICKET-13705)
  • get_plan_service_details API generated an improper error message (TICKET-13670)

You must to post a comment.
Last modified
15:15, 22 Feb 2017

Tags

This page has no custom tags.

Classifications

This page has no classifications.