Release 32

Master Plan Instance and Supplemental Plan Instance Payload Information Added to Active Orchestration (DEV-7040)

 

Aria Billing Cloud now provides additional unit instance payload data for the following events (under Configuration > Notification > Events > Accounts and Master Plan Instances Event Group):

• Account Fulfillment Based Service Plan Assignment
• Account Service Plan Unit Queued for Fulfillment
• Account Service Plan Unit Fulfillment Complete
   

The following payload field data has been added:

Master Plan Instance (MPI) unit instance data:

01 <mpi_unit_instance_data> 02     <plan_unit_inst_no> 03     <client_plan_unit_inst_id> 04     <plan_unit_inst_status> 05     <pi_unit_inst_plan_services_data> 06         <service_no> 07         <client_service_id> 08         <service_name> 09         <fulfillment_date> 10         <fulfillment_status> 11     </pi_unit_inst_plan_services_data> 12     <pi_unit_inst_supp_fields_data> 13         <field_name> 14         <field_value> 15     </pi_unit_inst_supp_fields_data> 16 </mpi_unit_instance_data>

Supplemental Plan Instance (SPI) unit instance data:

01 <spi_unit_instance_data> 02     <plan_unit_inst_no> 03     <client_plan_unit_inst_id> 04     <plan_unit_inst_status> 05     <pi_unit_inst_plan_services_data> 06         <service_no> 07         <client_service_id> 08         <service_name> 09         <fulfillment_date> 10         <fulfillment_status> 11     </pi_unit_inst_plan_services_data> 12     <pi_unit_inst_supp_fields_data> 13         <field_name> 14         <field_value> 15     </pi_unit_inst_supp_fields_data> 16 </spi_unit_instance_data>

These fields can be obtained by subscribing to your chosen event and selecting any method, including XML, name-value pair format, and Email message format payloads.

Provisioning Settings must also be configured as follows (from Configuration > Notifications > Provisioning Settings):

Event	Setting
Provisioning Request Creation Status	True
Provisioning Request Processing Status	Active

In addition, the client parameter value for the PROV_ACCOUNT_MPI_CLASS_VERSION_M client setting must be 3.0. Please contact Aria Customer Support to enable this setting.

---

 

Invoice Batch Job Enhancement (DEV-9528)

 

This feature improves the performance of the Invoicer batch job for accounts with a large number of Master Plan Instances (MPIs) and Supplemental Plan Instances (SPIs).

---

 

Reactivating an MPI after suspension (DEV-9970)

 

This feature updates Aria behavior when taking an MPI out of suspension and moving it out of dunning. Rather than assigning an 'Active' status to the MPI, Aria now assigns the status it had before it was suspended.

---

 

New Fields Available for Payment Reminder and Dunning Email Templates (DEV-9973)

 

The fields listed below are now available for you to include in your payment reminder and dunning email templates. Please contact Aria Customer Support if you want to include this information in the email templates mentioned above:

• insertGLTotalDue: amount due on an invoice
• insertGLDueDate: payment due date
• insertOverdueStmtAmountOwed: statement amount overdue
• insertAcctStmtDaysPastDue: number of days by which the statement amount is overdue
• insertSuppField1RawPrettyVal: account field value 1
• insertSuppField2RawPrettyVal: account field value 2
• insertSuppField3RawPrettyVal: account field value 3

---

 

New Input Fields <bank_name> and <bank_city> Fields Added To Support Direct Debit On Create Account UI Screen (DEV-9978)

 

This feature adds the input fields “bank name” and “bank city” for the Direct Debit payment method on the Create Account screen in the Aria UI.

---

 

Daily/Weekly Billing Phase 6 (DEV-9987)

 

This enhancement includes another iteration of Aria's Daily/Weekly Billing, which will be released in phases. In this phase, Aria added the key features listed below. Please see the documentation linked to below for more details:

1. You can now specify the Pro-ration End Date when you replace a daily or weekly master or supplemental plan. The Pro-ration End Date sets the date that proration should go up to and determines the start date of the next full invoice.
2. On the Replace Plan screen, the Rate Schedule section has been moved higher on the screen to a location above the Assignment Scope section.

---

 

New Data Streaming Objects: Plan Relationships, Usage Types, Usage Unit Types (DEV-9989)

 

The latest iteration of the Aria Data Streaming Web Service introduces the Plan Relationship, Usage Types, and Usage Unit Types objects in the Aria Data Stream. View the Data Streaming Logical Object Model for details.

---

 

Increased Character Length For Custom Dashboard URL (DEV-9994)

 

This feature increases the length of the Custom Dashboard URL field to 1000 characters in the Aria UI on the Configuration > Client Settings > Company Profile screen.

---

 

Chase Paymentech Support for 3D Secure Authentication (DEV-10003)

 

Aria's integration with the Chase Paymentech payment gateway has been enhanced with support for 3D Secure (3DS) Authentication 2.0. The 3DS authentication feature provides additional fraud prevention when transactions are processed. This is supported for the Visa and MasterCard card types.

Click here to access the Chase Paymentech payment processor page for detailed instructions.

Additional Field Enhancements

Also, as part of this feature, the following URL fields have been expanded to 200 characters for the following payment processors:

Processor	Impacted URL Field
Adyen	3DS Termination URL
Cybersource	3DS Client JS Library URL
Ingenico	3DS Termination URL
Worldpay	Challenge Posting URL DDC Posting URL 3DS Termination URL

---

 

Order Fulfilled Date Can Be in the Past (DEV-10012)

 

When you create or update an order, you can now provide an Order Fulfilled Date that is in the past.

 

Note: Currently, setting the Order Fulfilled Date makes that data available for informational purposes only. Setting the Order Fulfilled Date does not result in changes to an order or account.

 

---

 

Rate Schedule Bill Frequency Label Updates (DEV-10032)

 

This feature modifies the Products > Plans > [specific plan] > Rates tab > [click Rate Schedule icon] screen in the Aria UI: The fields Billing Interval and Usage Interval have been updated to Recurring Billing Interval and Usage Billing Interval respectively.

More information on Rate Settings can be accessed from here.

---

 

Application Fixes 

 

• When searching for Customer Support Representative (CSR) Activity (Analytics and Reporting >  Reports > CSR Activity), the Customer Support Representative (CSR) Internet Protocol (IP) Address is now masked with the word “Internal” if an address is found as part of the search results. (TICKET-18068)

• When you are creating a Discount Rule in the Aria application under Marketing > Discount Rules, Aria now validates the value for Max Applicable Months, Weeks, and Days. Previously, you could enter zero (0), which resulted in an error. (TICKET-18101)
• With this update Aria is allowing negative line items into refund_tax_detail. This ensures the sum of credit values in refund_tax_detail is equal to credit value in tax record refund_detail. (TICKET-18110)

---

 

Enhanced Order Qualifier Support for create_order_m, update_order_m, and get_order_m APIs (DEV-9882)

 

The API calls create_order_m and update_order_m have been updated to create “order qualifiers” based on the inputs received from the existing <optional_transaction_qualifiers> input. The get_order_m API has been updated to include the <order_qualifiers> array output fields.

An order qualifier provides an additional level of detail concerning an item on an order. For example, an order item can be a router. In the order qualifier field/qualifier value array, you can pass information such as the router manufacturer, serial number, or connection speed (such as 5GHz). This eliminates the need to create individual order items for every possible combination of a particular item.

• To generate order qualifiers using the create_order_m API, enter the following pre-existing input values:

Field Name	Value
<bill_immediately>	0, 1, 2
<do_write>	True

Enter the details in the existing fields of the <optional_transaction_qualifiers> input array and run the API.

• To update existing order qualifiers using the update_order_m API, enter the following pre-existing input values:

Field Name	Value
<bill_immediately>	0, 1, 2
<do_write>	True

Enter the details in the existing fields of the <optional_transaction_qualifiers> input array and run the API.

 

Note: If order qualifiers are created using create_order_m and update_order_m is run for that order with no new order qualifiers, the order qualifiers generated using create_order_m will be retained.

 

• Retrieve the <order_no> with the order qualifiers and run the get_order_m API. The following new output array is generated with order qualifier details as shown (these are copied to transaction qualifiers when the order is billed on the anniversary):

Start of <order_qualifiers> output array
Field Name	Description
<qualifier_name>	Name of the field you want to associate with this API call.
<qualifier_value>	Corresponding value of the field you want to associate with this API call.
End of <order_qualifiers> output array

---

 

Get Invoice History of Multiple MPIs (DEV-9935)

 

You can now use the get_invoice_history_m API to retrieve the invoice history of all master plan instances (MPIs) or your specified set of MPIs for an account. To do so:

1. Pass -1 into the <master_plan_instance_id> input field to get the invoice history of all MPIs for an account; or
2. Pass your chosen set of MPI identifiers into the new <filter_master_plan_instance> input array to get the invoice history of those MPIs for an account.

---

 

Error message will display if API call references unmapped usage type, or when the MPI is inactive (DEV-9982)

 

This feature updates Aria logic so when the client parameter REJECT_USAGE_WHEN_USAGE_TYPE_NOT_ON_PLAN is set as "true," the APIs record_usage_m and bulk_record_usage_m will now return "Error 20006 Usage code, or type not on active plan" when those API calls reference a usage type that is not mapped to the given plan instance, or when the plan instance is inactive.

---

 

Daily/Weekly Billing Phase 6 (DEV-9987)

 

This enhancement includes another iteration of Aria's Daily/Weekly Billing, which will be released in phases. In this phase, Aria added this feature: you can now use the edit_acct_plan_queued_changes_m API to complete daily/weekly plan updates and billing date resets with any <queue_edit_directive> or <assignment_directive>.

---

 

Chase Paymentech Support for 3D Secure Authentication (DEV-10003)

 

Aria's integration with the Chase Paymentech payment gateway has been enhanced with support for 3D Secure (3DS) authentication 2.0. The 3DS authentication feature provides additional fraud prevention when transactions are processed. This is supported for the Visa and MasterCard card types.

The following output field is new for this feature (for the <proc_3dsecure_data/ proc_3d_secure_auth_data> array):

Field Name	Description	Affected APIs
<pa_3ds_from_content>	If the issuer’s Access Control Server (ACS) supports this feature, this field will receive content to populate the client’s form page to enable 3DS authentication. If the issuer’s ACS does not support this feature, no information for authentication will be returned to this field.	authorize_3dsecure_m authorize_electronic_payment _m update_payment_method_m validate_acct_fraud_scoring_m

Click here to access the Chase Paymentech payment processor page for detailed instructions.

---

 

Order Fulfilled Date Can Be in the Past (DEV-10012)

 

• When you create or update an order using the create_order_m/update_order_m APIs, you can now provide a <fulfilled_date> that is in the past.

 

Note: Currently, setting the <fulfilled_date> makes that data available for informational purposes only. Setting the <fulfilled_date> does not result in changes to an order or account.

 

• In addition, the get_order_m and get_order_details_m APIs now return the order fulfilled date in the new <fulfilled_date> output.

---

 

API Fixes 

 

• When you call the get_acct_plans_all_m API and there is a service location associated with the account, an unexpected error no longer occurs. (TICKET-17669)

• The discard_usage_m API now discards usage when there is only one active (neither discarded nor invoiced) usage record for the given client record ID; previously, an error message was generated. A spelling mistake in the error message has also been corrected. (TICKET-18093)

• Invoices will no longer be generated when updating test accounts with the API update_acct_plan_multi_m. (TICKET-18161)

• When you have an account with a negative account balance, you can now successfully settle a dispute or void a credit memo (using the void_credit_memo_m API)  associated with that account. (TICKET-18184)