Home > Aria6 User Documentation > Aria6 Release Notes > Aria6 Release 6.50
Aria6 Release 6.50
Aria6 Release 6.50
Table of contents
- Overview
- Application Features
- First Data Payeezy Payment Processor (DEV-6970)
- New Design with Precise Access Control for Creating a Role (DEV-7862)
- Updated Calculation for NETS Refunds to Display Total Amount Paid (DEV-7255)
- Aria to NetSuite Data Transfer Enhancements (DEV-7267)
- Additional Sorting and Viewing Capability (DEV-5881, DEV-5883, DEV-5885)
- Contract End Action Option Description Revised for Clarity (DEV-7449)
- Multi-Client Support for AriaRA (DEV-6760)
- Mountain Time Zone (MDT/MST) Addition (DEV-7552)
- Update Default Locale with Additional Values (DEV-7535)
- Account Overview View-only CSR Level Access Updated (DEV-7862)
- Application Fixes
- API Features
- WSDL File Locations
Release Date
12/6/2016
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
- First Data Payeezy Payment Processor (DEV-6970)
- New Design with Precise Access Control for Creating a Role (DEV-7862)
- Updated Calculation for NETS Refunds to Display Total Amount Paid (DEV-7255)
- Aria to NetSuite Data Transfer Enhancements (DEV-7267)
- Additional Sorting and Viewing Capability (DEV-5881, DEV-5883, DEV-5885)
- Contract End Action Option Description Revised for Clarity (DEV-7449)
- Multi-Client Support for AriaRA (DEV-6760)
- Mountain Time Zone (MDT/MST) Addition (DEV-7552)
- Update Default Locale with Additional Values (DEV-7535)
- Account Overview View-only CSR Level Access Updated (DEV-7862)
Application Features
First Data Payeezy Payment Processor (DEV-6970)
This feature adds First Data Payeezy as an available payment processor. Supported payment methods include:
- Credit Card
- Visa, MasterCard, American Express, Discover, JCB, Diners Club
- Tokenized Credit Card
Getting Here: Select Configuration > Payments > Payment Gateways > New > First Data Payeezy
Fields you must configure to set up this payment processor are as follows:
- JS Secret Key: JavaScript Secret Key used to identify the merchant.
- Merchant Token: The token value assigned to the merchant.
- Merchant API URL: The API URL endpoint that is used to communicate with Payeezy.
- API Secret: The API Secret is used for authorization and helps provide better security.
- API Key: A unique value that is assigned to an authorized user of this service.
New Design with Precise Access Control for Creating a Role (DEV-7862)
This feature enables precise access for roles (for example: enabling or denying read, create, or delete access to batch processes) and control of the contents in the navigation pane. The user experience has been enhanced by providing intuitive menus and simplified steps.
Note that access to a certain module may include the ability to interact with other modules to which the user has not been granted explicit access. For example, a user with only "Create Plan" access can create new services within the Plans module when creating a new plan. However, this same user does not have access to the Services module in the navigation pane, and thus cannot create services within the Services module.
Creating a Role
Getting Here: Click Configuration > Security > Roles > New
Note: Depending on the functions configured within your Aria instance, the options that appear in the following Roles screen may differ. If you have questions regarding one of these modules, refer to User Documentation for that module.
- Enter a Role Name. Be specific as this name allows you to easily identify the role. For example, Business Analyst with API Live Access.
- Enter a Client Defined Identifier. A unique ID for reference within your organization. A Client Defined Identifier is an Aria-generated ID that may be updated to meet your needs.
- Set the access for the Manage Authorization Keys setting.
- Yes: Automatically selects Read for the Configuration > Integrations > Web Service API page. The Configuration > Integrations > Web Service API page is enabled in the navigation bar and includes the ability to generate, enable or delete authorization keys.
- No: The user does not have access to enable or delete authorization keys within the Web Service API page.
Note: If Read access for Configuration > Integrations > Web Service API page is deselected, the Manage Authorization Keys setting automatically reverts to No.
- Set the access for the listed modules.
- Yes: The module appears in the navigation pane for users with this role. All functions within the module are available for the user.
- No: The module is not displayed in the navigation pane, and the user cannot access any of the functions.
- Click the drop-down arrow to view the module's access options.
For example, Analytics & Reporting presents options to grant access to various dashboards and reports. Marking the star designates the dashboard as the default.
The Access to Account Groups section displays each available Functional Account Group with a check box. Selecting a checkbox enables the role access to that Functional Account Group. If you do not have Account Groups configured, this section does not display.
For some modules, such as Configuration, specific access can be granted to individual sub-pages for the module. If no checkboxes for a sub-page are checked, the sub-page or features (for example, a create New button) of the sub-page do not display for a user with the role.
- To grant access to all of Configuration, use the top-level checkboxes for Read, Create, Edit or Delete (i.e. there is no need to expand the accordion).
- To deny access to all of Configuration, do not select any checkboxes. Once the role is saved and assigned to a user, Configuration does not display in the navigation pane for the user.
Note: In some cases, higher-level access includes lower-level access. This is denoted automatically as you select the checkboxes. For example, a user with Create, Edit or Delete access automatically has Read access.
- Click Save. The role can now be assigned to a user.
Updated Calculation for NETS Refunds to Display Total Amount Paid (DEV-7255)
Note: You must Enable NETS refunds for this functionality.
When using an API to issue an account refund to a NETS account (e.g. with the issue_refund_to_acct API), the logic used to calculate the total paid amount for an invoice has been modified. Refunds processed through NETS are now correctly applied to the total amount paid for an invoice.
Aria to NetSuite Data Transfer Enhancements (DEV-7267)
This feature adds two configuration options to the NetSuite UI that control when data is transferred from Aria to NetSuite.Getting Here: Click Setup > Company > General Preferences
Select the Custom Preferences tab.
Click the checkbox next to either of the two options to activate them. The options are as follows:
- Aria Apply Period End Filter: If this option is selected, no Aria transactions are sent to NetSuite after the last day of the oldest open NetSuite accounting period. Once that period is closed, the next period end date becomes the new filter date.
- Aria Suspend Transfer: If this option is selected, no Aria transactions are sent to NetSuite.
Additional Sorting and Viewing Capability (DEV-5881, DEV-5883, DEV-5885)
The Promotional Plan Sets, Coupons, and Discount Rules screens now provide the ability to sort each column, filter certain columns, and to show and hide columns.
The revised screens now have the following features:
- 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: You can use the search box just below each column name to find values within that column.
- Filter Columns: Certain columns allow you to filter the displayed data by the values in this column. Click the up/down arrows in the box below the column name to see the values you can use to filter the list.
- Show/hide columns: The Show/hide columns menu in the upper right corner allows you to add and remove columns from the display by checking or unchecking the column name in the menu.
Contract End Action Option Description Revised for Clarity (DEV-7449)
Previously, an option for Contract End Options was "Continue service without contract with standard rates." However, this label did not accurately or clearly describe the option. This label has been updated to "Continue service without contract with pre-contract rates."
The tooltip displayed when hovering over the option has also been updated for clarity to state: On completion of contract terms, service will stay in effect and continue to bill per normal terms. The rates that were present on the account before the contract was applied will be in effect at time of contract completion.
This option displays in various places in the user interface when configuring a contract. When the "Continue service without contract with pre-contract rates" option is selected, the service continues and the rates existing on the plan before the contract was assigned apply.
Multi-Client Support for AriaRA (DEV-6760)
This feature enhances AriaRA for users who have access to multiple client environments. Now, when you switch client environments, you can run AriaRA reports for the current client without having to close your browser and log back in.
Mountain Time Zone (MDT/MST) Addition (DEV-7552)
This feature allows Mountain Time to be set as the client's time zone. Previously, the available time zone for this region of the United States was Phoenix time, which does not use daylight savings time. Mountain time follows daylight savings time.The time zone for your company is set by Customer Support. This enhancement affects Audit Log entries, which can now show a timestamp coordinated with Mountain time.
Update Default Locale with Additional Values (DEV-7535)
This feature allows you to add additional values when specifying a locale. When adding or editing a locale within the Aria application, there are various system-defined fields that can be translated into the locale’s default language. Two fields were added to this configuration page so that they can be displayed in the appropriate language on statements and in other areas of the application.Getting Here: Click Configuration > Client Settings > Locale Settings > New or edit an existing locale
The new fields on this screen are:
- Invoice credit applied to charge lines
- Voided invoice credit applied to charge lines
Account Overview View-only CSR Level Access Updated (DEV-7862)
Previously, the View-only CSR level access allowed edit access to certain areas of the Account Overview module. The View-only CSR level has been updated to remove any edit access, and now only allows view access to the Account Overview section.
For more information about roles, refer to Security.
Application Fixes
- Various issues in Countries & States drop-down boxes (TICKET-12187)
- Internal server error was returned while saving data in Smart Rec > Options screen (TICKET-12472)
- Statement sending configurations were not honored when creating a new account (TICKET-12689)
- Events name was displaying twice for same line item (TICKET-12757)
- Two invoices were generated after closing installation (TICKET-12759)
- Billing Contact country was changing to Account Country when adding tokenized credit card in the user interface (TICKET-12910)
API Features
Support Sending CVV Only Through create_order API (DEV-7140)
For recurring transactions with a credit card payment method, the create_order API supports sending only the CVV number (without the credit card number) to the Vantiv (Litle) payment processor for collection. A new input parameter named <existing_pay_method_cvv> has been added to the create_order API to send the CVV number of an existing credit card on the account to the payment processor.
If the account’s current form of payment for recurring transactions is a credit card, the create_order API passes the <existing_pay_method_cvv> (if entered) to Aria and then Aria passes the account’s current credit card and details of the CVV to the payment processor to complete the order.
If the alt_pay_method API is used, the <existing_pay_method_cvv> input parameter is ignored and the CVV field provided in the alt_pay_method is used.
<Type_no> Description Updated for Clarity (DEV-7449)
The type_no=4 description has been updated for the following APIs:
- create_acct_multiplan_contract
- create_acct_plan_contract
- create_acct_universal_contract
- modify_acct_multiplan_contract
- modify_acct_plan_contract
- modify_acct_universal_contract
The description has been updated from "Continue service without contract w/standard rates" to "Continue service without contract with pre-contract rates." This description has been updated for clarity, and does not reflect a change to the functionality.
Dynamic Soft Descriptor for PayPal PayFlow Pro and Express Checkout (DEV-7479)
This feature adds support for entering dynamic Soft Descriptor information for the PayPal PayFlow Pro, and PayPal Express Checkout payment processors. A credit card soft descriptor is text rendered on a cardholder’s statement. It describes a particular product or service purchased by the cardholder. Descriptors are intended to help the cardholder identify the products or services purchased.
The following APIs have a new input parameter:
- create_order
- create_order_with_plans
- collect_from_account
- settle_account_balance
The new input parameter is as follows:
<soft_descriptor> - Transaction description shown on the buyer's statement.
API Fixes
- N/A
WSDL File Locations
Stage Current
| US | |
| EUR | None |
Stage Future
| US | https://secure.future.stage.ariasystems.net/api/Advanced/wsdl/6.50/complete-doc_literal_wrapped.wsdl |
| EUR |
Production
| US | https://secure.ariasystems.net/api/Advanced/wsdl/6.50/complete-doc_literal_wrapped.wsdl |
| EUR | https://secure.prod.cph.ariasystems.net/api/Advanced/wsdl/6.50/complete-doc_literal_wrapped.wsdl |
Object Query WSDL Files
Stage Current
| US | |
| EUR | None |
Stage Future
| US | |
| EUR |
Production
| US | |
| EUR |
- © Copyright 2022 Aria Developer Central