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

 

Home > User Documentation > Aria6 Release Notes > Aria6 Release 6.44

Aria6 Release 6.44

Application Features

Show Plan Relationships (DEV-6348)

This feature enhances the Plans module to more easily show and modify the parent/child relationship between plans.

Getting Here: Click Products > Plans

When you select a Master Plan, and then select the Plan Relationships tab, you see a list of the associated child plans.

Master Plans show the following:

  • Child Plans
  • Plan Groups

Supplemental Plans show the following:

  • Parent Plans
  • Child Plans
  • Plan Exclusions

To add a plan relationship, you can enter a plan number in the text entry box, or you can click Browse to see a list of available plans.

To delete a plan relationship, click the red X to the right of the plan name.


New Contract Expiry Account Notification Events (DEV-6186)

This feature adds new events and email templates for when a contract ends.

The following are the contract end actions and the corresponding event:

  • Account Message Type "Contract End: Suspend Service and Billing" Requires Sending: System determination that account message type "Contract End: Suspend Service and Billing" (message class "CES") requires sending.
  • Account Message Type "Contract End: Suspend Service and Billing (Proration)" Requires Sending: System determination that account message type "Contract End: Suspend Service and Billing (Proration)" (message class "CESP") requires sending.
  • Account Message Type "Contract End: Continue Service Without Contract" Requires Sending: System determination that account message type "Contract End: Continue Service Without Contract" (message class "CECS") requires sending.
  • Account Message Type "Contract End: Continue Service (Standard Rates)"  Requires Sending: System determination that account message type "Contract End: Continue Service (Standard Rates)" (message class "CECSS") requires sending.
  • Account Message Type "Contract End: Renew Automatically" Requires Sending: System determination that account message type "Contract End: Renew Automatically" (message class "CERA") requires sending.
  • Message Type “Contract End: Suspend Service and Billing" Sent To Account Holder: Account message type "Contract End: Suspend Service and Billing" (message class "CES") was sent to account holder.
  • Message Type "Contract End: Suspend Service and Billing (Proration)" Sent To Account Holder: Account message type "Contract End: Suspend Service and Billing (Proration)" (message class "CESP") was sent to account holder.
  • Message Type "Contract End: Continue Service" Sent To Account Holder: Account message type "Contract End: Continue Service" (message class "CECS") was sent to account holder.
  • Message Type "Contract End: Continue Service (Standard Rates)" Sent To Account Holder: Account message type "Contract End: Continue Service (Standard Rates)" (message class "CECSS") was sent to account holder.
  • Message Type "Contract End: Renew Automatically" Sent To Account Holder: Account message type "Contract End: Renew Automatically" (message class "CERA") was sent to account holder.

The following email template classes have been created for each contract expiry event. The default email template for each of the following template classes is created by copying the content from the existing "Generic Contract expiry warning" template.

  • Contract End: Suspend service and billing: Notify account holders of an impending expiry of an existing service plan contract, when service and billing will be suspended.
  • Contract End: Suspend service and billing (prorate final invoice): Notify account holders of an impending expiry of an existing service plan contract, when service and billing will be suspended and the final invoice is prorated.
  • Contract End: Continue existing service without contract: Notify account holders of an impending expiry of an existing service plan contract, when service will continue without a contract.
  • Contract End: Continue existing service (standard rates): Notify account holders of an impending expiry of an existing service plan contract, when service will continue at standard rates.
  • Contract End: Renew automatically: Notify account holders of an impending expiry of an existing service plan contract, when the contract will be automatically renewed.

API Live Incorporated into Aria UI (DEV-6144)

This feature moves API Live to the Aria UI. It has been removed from Developer Central.

Getting Here: Click Configuration > Utilities > API Live

  1. From the API Live screen, click the name of the API you want to execute. The data entry screen for the API you selected opens.

 

  1. Enter the API's parameters. If a parameter has a default, the value is pre-populated in the data entry field. Because API Live is now only accessible by logging on to the Aria UI, it is no longer necessary to enter the Auth Code, as it defaults to your client code. If you have multiple Auth Code's stored, you can select one from a drop-down menu. The first Auth Code in the list is the default.
  2. Click Agree & Execute. The API executes against the environment in which you are authenticated. Note that previously, you selected the environment to execute against. The results display on the screen.

TNS Payment Gateway Added to Aria UI (DEV-6027)

This feature adds the TNS payment gateway to the Aria UI.

Supported payment methods include:

  • Credit Card
    • Visa, MasterCard, American Express
  • Tokenized credit cards

TNS supports transactions using US dollars.

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

Select TNS from the Payment Gateway drop-down menu.

You must have values for the following fields before setting up this payment gateway:

  • Merchant API URL: The URL provided by TNS to use as an endpoint.
  • API Password: To generate your API Password you must log in to TNS Merchant Administration and follow these steps. You must obtain your Merchant Administration login credentials from TNS before setting up this payment gateway.
  1. Log into Merchant Administration (MA) and navigate to Admin > Operators and create a new Operator with the May Configure Integration Settings privilege.
  2. Log in to Merchant Administration with your new Operator and select Admin from the top menu.
  3. Select API Integration Settings from the left menu.
  4. Click Edit under the API Authentication section.
  5. Select the Enable API Access via password check box for Password 1.
  6. Click Generate New for Password 1.
  7. Click Submit to save the configuration.
  • Merchant ID: Obtain your Merchant ID from TNS before setting up this payment gateway.

Fail Test Payment Gateway in Stage Future Supports Tokenized Credit Cards (DEV-6536)

This feature enhances the Stage Future Fail Test Payment Gateway so it now supports tokenized credit cards. This enhancement applies only to the Stage Future environment.


​Paymetric Payment Gateway Modified for Discover Cards (DEV-6457)

This feature enhances the Paymetric payment gateway. When using Discover cards with the Paymetric payment gateway, the TR_TRANS_RECURPMNT field will no longer be required or applied.


​Vantiv (Litle) Payment Gateway Now Supports FTP Transactions (DEV-6363)

This feature enhances the Vantiv payment gateway so it now supports submitting transactions using FTP, in addition to the currently supported API method. The following fields have been added to the Vantiv payment gateway configuration screen:

  • SFTP Account: The SFTP account ID provided by Vantiv
  • SFTP Password: The SFTP password provided by Vantiv
  • SFTP Host: The SFTP host location provided by Vantiv

Application Fixes

  • Page navigation not working under Resource Control tab (TICKET-3548)
  • Cancel button on Pending Invoices screen did not work as expected (TICKET-10330)
  • Discounts were applied incorrectly (TICKET-10690)
  • Avalara - Wrong tax code sent (TICKET-10707)
  • Internal error when accessing Resource Control page (TICKET-10788)
  • Auto collect from parent for immediate invoices of child not working (TICKET-10789)
  • Invoice usage period is not synced with new billing date (TICKET-10808)
  • Column heading missing on Account Overview screen (TICKET-10826)
  • Usage Types Page was not loading for some clients (TICKET-10828)
  • Credits were not incorporated in tax reversal calculations (TICKET-10879)
  • Unable to change the default rate schedule (TICKET-10886)
  • State/Province values incorrectly set to null (TICKET-10995)
  • Incorrect error message returned when the user tried to set the start date of the contract before the account retroactive start date (TICKET-11005)
  • Partial payment revenue recognition process used the incorrect date for the earned date (TICKET-11040)
  • Issue in NSO bundling screen (TICKET-11050)
  • Batch jobs not completing as expected in Production (TICKET-11099)
  • Accounts breadcrumb navigation missing (TICKET-11101)
  • Broken links on deprecated APIs (TICKET-11130)
  • Plan Exclusions and Plan Group sections were not supporting double quotes (TICKET-11244)
  • Usage History screen timed out when there were a large number of records (TICKET-11255)
  • Transactions cannot be viewed due to invalid JSON response (TICKET-11353)

API Features

Get_client_items_all and Get_client_items_basic Performance Enhancements (DEV-6444)

The get_client_items_all and get_client_items_basic APIs have been modified to handle additional inventory items without timing out.


Enable or Disable Usage Pooling using update_acct_complete API for Queued Plans (DEV-6460)

This feature enhances the update_acct_complete API which now can enable or disable usage pooling for queued or future date master plans and supplemental plan i.e., plans set to become active on a future date.

The following fields have been added to the update_acct_complete API:

  • <enable_usage_pooling_plan_no>
  • <disable_usage_pooling_plan_no> arrays

 API Fixes

  • Edit_plan API displayed error while passing the item number (TICKET-9632)


You must to post a comment.
Last modified
15:36, 6 Jun 2016

Tags

This page has no custom tags.

Classifications

This page has no classifications.