Home > Aria Crescendo Documentation > Aria Crescendo Release Notes > Release 15.0

Release 15.0

Table of contents
  1. Overview
  2. Release Date
    1. Stage Future Release Date
  3. System Requirements
    1. Supported Browsers
    2. Screen Resolution
  4. Application 
    1. Features
    2. Fixes
  5. API
    1. Features
    2. Fixes
  6. Application Features 
    1. Service Period and Plan Type Identified in Rebill Statement Template (DEV-8587)
    2. Collection Amounts in JPY or INR Sent to Vantiv Correctly (DEV-8620)
    3. Vantiv (Litle) Fraud Integration (DEV-8698)
      1. Setting Up Fraud Options In Aria For Your Vantiv (Litle) Payment Gateway
    4. Support for Vantiv Insights Marketing Tools (DEV-8699)
      1. Add Vantiv (Litle) Payment Gateway
        1. Configuring Vantiv Insights Via a Collection Group
        2. Viewing an Account's Insights Data in the Aria UI
    5. New Payment Method: Merchant Specific Gift Card (DEV-8700)
      1. Add Vantiv (Litle) Payment Gateway
      2. Adding "Merchant Specific Gift Card" Pay Method
      3. Configuring Direct Post Behavior for "Merchant Specific Gift Card"
      4. Specifying "Merchant Specific Gift Card" as an Account's Pay Method
    6. Recurring Flag Sent to Braintree only after Successful Payment ​(DEV-8710​)
    7. Plan Visualization (DEV-8775)
    8. New Parameter Controls Bill Through Date of Supplemental Plans (DEV-8866)
    9. New Parameter Allows you to Collect or Skip Collection against MPIs in Dunning (DEV-8867)
    10. Application Fixes 
  7. API Features 
    1. JSON Support for PHP Dispatcher (DEV-8214)
    2. API Performance Improvements
    3. Reason Code Table Updated For Cash Credits (DEV-8640)
    4. Vantiv (Litle) Fraud Integration (DEV-8698)
    5. Vantiv Insights Marketing Tools (DEV-8699)
    6. Support For New Payment Method: Merchant Specific Gift Cards (DEV-8700)
    7. Dynamic Soft Descriptor Field For Non-Credit-Card PayPal Payments (DEV-8728)
    8. update_order_m Collects Payments Successfully (DEV-8810)
    9. Field Parameter (client_acct_id) Added to Several APIs (DEV-8819)
    10. API Fixes 
  8. WSDL File Locations
    1. Object Query WSDL Files

Application Features 

Service Period and Plan Type Identified in Rebill Statement Template (DEV-8587)

The rebill statement template can now include the service start date and service end date. In addition, the template can now identify whether a line item applies to a master plan or supplemental plan so that the applicable data for each plan can be displayed or hidden in the rebill statement. Please contact Aria Customer Support if you want to include any of this new information in your rebill statement template.


Collection Amounts in JPY or INR Sent to Vantiv Correctly (DEV-8620)

If you use Vantiv as your payment gateway and you attempt to collect a payment in JPY (Japanese yen) or INR (Indian rupee), the correct amount is now requested. No decimal point is added to the payment amount. Example: if you attempt to collect 1600 JPY, now 1600 JPY is collected instead of 160000 JPY.


Vantiv (Litle) Fraud Integration (DEV-8698)

Vantiv (Litle) has partnered with ThreatMetrix to further assist you with limiting fraudulent transactions. If you use Vantiv (Litle) as your payment gateway in Aria, you now have access to fraud scoring settings. Fraud scoring applies to card, direct debit, electronic check, and tokenized card payment methods.

To use these fraud protection features, you must first enable and configure them within Vantiv. You can then update your Vantiv Payment Gateway settings in Aria.

Setting Up Fraud Options In Aria For Your Vantiv (Litle) Payment Gateway

Getting here: Configuration > Payments > Payment Gateways > Vantiv (Litle)

  1. If you have not yet configured your Vantiv (Litle) payment gateway, 
  2. Configure the fraud fields as desired. On the Processor Details tab, add the ThreatMetrix Prefix provided to you by Vantiv when you enabled Fraud Scoring:

    gateway_processor_details.png
     
  3. On the Gateway Options tab, update the Fraud Options fields as desired: 

    gateway_options.png

    Send Fraud Scoring Request: When enabled, Aria will send a request for a fraud score to Vantiv (Litle).

    Change Status on Fraud Scoring Failure: When set to true, Aria will update the status of the if the fraud score is below the threshold, or if the Fraud Score response is unsuccessful, to the status chosen for Status on Fraud Scoring Failure.

    Status on Fraud Scoring Failure: Choose a status from this list of Statuses.

    Change Status on Fraud Scoring Review: When set to true, Aria will update the status of the if the fraud score is "Review," the status chosen for Status on Fraud Scoring Review.

    Status on Fraud Scoring Review: Choose a status from this list of Statuses.

 

Note: If you are using Direct Post and you are running a $0 authorization, then Aria will skip any steps in your configuration that involve fraud scoring.


Support for Vantiv Insights Marketing Tools (DEV-8699)

This feature adds Aria support for Vantiv Insights, which provides additional information to merchants to improve authorization approval rates and lower the total cost of payments. This additional information falls into four categories: Prepaid Indicator, Affluence Indicator, Issuer Country Indicator, and Card Type Indicator.

To use Vantiv Insights, you must have a pre-existing relationship with the Vantiv payment gateway, with Insights configured within your Vantiv instance; and, you must enable this feature in Aria.

Add Vantiv (Litle) Payment Gateway

Getting here: Configuration > Payments > Payment Gateways

  1. Click the New button
  2. Select Vantiv (Litle)
  3. Complete
  4. Enable Vantiv Insights via the new configuration field, Vantiv Insights:

    vantiv_gateway_enable_insights.png

    Enabled: New Insights data points can be viewed within the Aria Account Overview for customers whose payments will be collected via the Vantiv payment gateway, and Insights data can be retrieved via supported API calls and Direct Post.

    Disabled: Insights data will not be retrieved.
Configuring Vantiv Insights Via a Collection Group

Getting here: Configuration > Payments > Collection Groups

  1. Click the New button.
  2. Configure a
  3. Select a value from the Insight Options drop-down menu:

    vantiv_collgroup_enable_insights.png

    Use Payment Gateway Setting: Aria will follow the directive that is configured for your Vantiv (Litle) Payment Gateway.

    Enabled: Regardless of whether Vantiv Insights is enabled in your Vantiv (Litle) Payment Gateway, API calls that collect payments for accounts associated with this Collection Group will be able to retrieve Vantiv Insights data.

    Disabled: Regardless of whether Vantiv Insights is enabled in your Vantiv (Litle) Payment Gateway, no Vantiv Insights data will be retrieved via API calls.
Viewing an Account's Insights Data in the Aria UI

When an account is associated with the Vantiv (Litle) payment gateway and Insights is enabled, this icon will appear when viewing an account's card (credit card, tokenized credit card, or pre-paid card) payment method within the Payment Methods tab of the Account Overview:

insights_pay_method_tab.png

If there are Insights data associated with that card, mousing over this icon will show that data:

insights_sample.png

If there are no Insights data available, mousing over this icon will cause a message to popup, "No card type detail available."


New Payment Method: Merchant Specific Gift Card (DEV-8700)

This feature adds Aria support for a new payment method, "Merchant Specific Gift Card," for Vantiv clients only. This pay method shares data fields with credit cards, with the additional ability to request the remaining balance via supporting API calls and Direct Post configurations.

To take advantage of this feature, you must first enable this feature on the Vantiv side of your configuration. Once configured in both Vantiv and Aria, Aria sends gift-card-related data to, and receives gift-card-related data from, Vantiv via API calls.

Add Vantiv (Litle) Payment Gateway

Getting here: Configuration > Payments > Payment Gateways

  1. Click the New button
  2. Select Vantiv (Litle)
  3. Complete

Adding "Merchant Specific Gift Card" Pay Method

Getting here: Configuration > Payments > Payment Methods

  1. Click the New button.
  2. Select Merchant Specific Gift Card from the Select a Method drop-down menu.
    new_payment_method_40.png
  3. Complete

Configuring Direct Post Behavior for "Merchant Specific Gift Card"

Getting here: Configuration > Client Settings > USS Reg Configuration

  1. Click the New button.
  2. Choose "True" or "False" for the new field, Perform balance inquiry.
    USS_Reg_balance_inq.png
    True: The return from a Direct Post call will include the remaining balance for Pre-paid/Gift cards.
    False: The return from a Direct Post call will not include the remaining balance for Pre-paid/Gift cards.

Specifying "Merchant Specific Gift Card" as an Account's Pay Method

You can specify "Merchant Specific Gift Card" as an account's pay method in the following ways:

  1. Via API calls.
  2. Via the UI, on the Payment Methods tab on the Account Overview of an existing account.
  3. Via the UI, on the Collect Payment Electronically screen.
  4. Via the UI, on the Create New Account screen.

Recurring Flag Sent to Braintree only after Successful Payment ​(DEV-8710​)

Aria now sends the recurring flag (to identify a transaction associated with a subscription billing model) to the Braintree payment gateway only after a successful payment transaction. This is required to comply with Visa and MasterCard's rules that apply to Braintree.


Plan Visualization (DEV-8775)

This enhancement supports the visualization of Plan detail via the Account Hierarchy Visualization functionality introduced in Release 14.0. 

Note: An Aria user is required to be associated with a "Role" that permits Account Access at the Power CSR level. For more information, see Account Hierarchy Visualization.

 

Getting Here: Accounts > Account Search > Access Account

Click on Account Hierarchy Link.jpg

  1. Click on the Account's "View Account Hierarchy" link.

Click on Selected Accounts View Details Link.jpg

  1. The Account Hierarchy Overlay screen is displayed. Click on the selected account's "View Details" link.

Note: You can access Plan details for any account shown in the account's hierarchy by clicking on the specific account card's "View Details" link.

 

Click on Plan Instances View All Link.jpg

  1. A pop-up screen displays the account card's Account Number, Last Invoice Date, Last Invoice Amount, Service Credits, and Plan Instances. Click on the account card's Plan Instances "View All" link.

Billing Groups - Master Plans Screen.jpg

The Plan Visualization screen is displayed. This screen includes sections for A.) Billing Group, B.) Master Plan Instance, and C.) Master Plan Instances associated with the selected Billing Group.

For each Billing Group, the screen displays:

A). Billing Group

  • Aria-assigned number, and description.
  • Client-defined identifier.
  • Primary Payment description.
  • Secondary Payment description.
  • Statement Contact.
  • Notification Method. 

B.) Master Plan Instance(s) associated with a selected Billing Group.

C.) A graphical representation of the Master Pan Instance, and any Supplemental Plan Instance(s) associated with the selected Billing Group. The Plan visualization includes:

  • A colored dot indicating the Master / Supplemental Plan Instance(s) current status:
green dot.jpg Active, or Active Non-Billable
Yellow Dot.jpg

Inactive, Pending Activation, Pending Cancellation, Pending Installation, Pending Termination, Suspended, or Trial

Red Dot.jpg Terminated or Canceled
  • Plan Name
  • Plan Number
  • Number of Units purchased.
  • Rate Schedule name
  1. Click on the Master or Supplemental Plan Instance(s) "View Details" link. 

X Out of Plan Popup Details.jpg

A Plan Details popup screen displays detailing the Master or Supplemental Plan Instance's:

  • Last Bill date.
  • Bill Through date.
  • Usage Bill Through date.
  • Next Bill date.
  • Dunning State. (only for Master Plan Instances)
  1. Click on the Plan Detail's X to close the Plan Details popup.

Click on Master Plan Instance Drop-Down.jpg

  1. Click on the Master Plan Instance field's drop down arrow to view and select additional Master Plan Instances associated to the selected Billing Group for payment responsibility.

Note: As shown in the above example, any Child accounts' Master Plan Instance(s) having Parent Pay responsibility by the selected account's Billing Group are displayed with information including the Master Plan Instance Number, Plan Name, and Child Account Number.

  1. Click on any of the Master Plan Instances in the drop-down to refresh the screen's plan display.

Selecting a Different Master Plan Instance for Billing Group.jpg

  1. Click on the Plan(s) "View Details" link to view specific billing information for the Master/Supplemental Plan instance(s) as described in Step 4.
  2. Click on the Billing Group field's drop-down arrow to view, and select other Billing Groups associated to this account.

Additional Billing Groups.jpg

  1. Click on any additional "Billing Groups" associated to this account.

Note: As shown in the above example, any Parent accounts' Master Plan Instance(s)/Billing Group's having Parent Pay responsibility for any of the selected account's Master Plan Instances is displayed. The Parent Account's Billing Group is displayed with information including the Master Plan Instance Number responsible for payment, it's associated Billing Group, and the ParentAccount Number.

 

Back to Account View.jpg

  1. Click on the "Back to Account View" link to return to the Account Hierarchy Overlay screen.

New Parameter Controls Bill Through Date of Supplemental Plans (DEV-8866)

The new parameter Override Bill Thru Date Supp Plan Behavior allows you to specify the behavior of the bill through date of supplemental plans (mandatory or intentionally selected) when you assign them at the same time as their master plan. You can select either of these options for the parameter:

  • Align supplemental plans to next monthly bill day: The bill through date of any supplemental plan assigned at the same time as its master plan will be adjusted to match the next possible billing date based on the bill day of the master plan (regardless of the supplemental plan's recurring billing interval).
  • Align supplemental plans by backtracking from master plan renewal date: The bill through date of any supplemental plan assigned at the same time as its master plan will be backtracked from the master plan’s bill through date so that the supplemental plan and master plan will be renewed at the same time.

To set the parameter, click Configuration > Billing > Invoice Settings.

Examples:

If you call the assign_acct_plan_m or update_acct_plan_multi_m API on 4/6/2018 to assign a quarterly supplemental plan and an annual master plan and you pass in an override_bill_thru_date of 3/28/2019:

If…

Then…

the parameter was set to Align supplemental plans to next monthly bill day

the bill through date of the supplemental plan will be 4/28/2018 (based on the bill day of the master plan).

the parameter was set to Align supplemental plans by backtracking from master plan renewal date

the bill through date of the supplemental plan will be 6/28/2018, backtracked 9 months from 3/28/2019 (the renewal date of the master plan).


New Parameter Allows you to Collect or Skip Collection against MPIs in Dunning (DEV-8867)

The new parameter Skip Invoices with MPI In Dunning During Batch Collections allows you to specify whether to exclude master plan instances (MPIs) that are in a dunning state from Aria's daily batch collection job. If you set the parameter to True, Aria will not attempt collection against MPIs in a dunning state during the batch job. If you set the parameter to False, Aria will attempt collection against MPIs in a dunning state during the batch job for any MPI that has a new, unpaid invoice.

Example: You may choose to set the parameter to True if you want action to be taken on a delinquent account based on your specified dunning process instead of having Aria attempt another collection.

To set the parameter, click Configuration > Billing > Invoice Settings. (You may need to go to the second page of parameters to find Skip Invoices with MPI In Dunning During Batch Collections.)

Note: When the parameter mentioned above is set to True, Aria will not attempt collection against an invoice during the batch job:

  • If multiple MPIs are billed on the same invoice and at least one of the MPIs is in a dunning state; or
  • If any supplemental plan on the invoice is associated with an MPI that is in a dunning state.

Application Fixes 

  • Searching by the following fields in the Account Search module now works as expected: Credit Card (last 4 digits); Checking Account (last 4 digits); Administrative Contact Name; Billing Contact name; Company Name; Account Status. (TICKET-5768) 
  • If you enter the country code in lowercase in the account contact details then, as expected, the country code is displayed in lowercase instead of uppercase on the account holder's statements. (TICKET-11141) 
  • For tokenized credit cards, you can now delete the payment method name and description while retaining the expiration date. (TICKET-13777) 
  • Taxes charged for Recurring Arrears services are now included in proration credit calculations for cancelling those services. (TICKET-15680) 
  • When you cancel or replace a plan, any prorated credits applied for taxes on the previous plan are now calculated correctly. (TICKET-15919)
  • When a PayPal payment method on an account is replaced with a new payment method, collections are now attempted against the new payment method. (TICKET-16006)
  • "insertCCType", and "insertMaskedCCNumber" replacement strings are now correctly displaying credit card information onto a statement template when the statement is produced for an order. (TICKET-16074)

API Features 

JSON Support for PHP Dispatcher (DEV-8214)

The Core APIs have been enhanced to support JSON input format. For more information about JSON and Aria's API, see Forming JSON API Calls.


API Performance Improvements

Aria is improving our API/SDK offering on the latest version of our platform, Crescendo. Improvements include:

  • performance enhancements of core APIs to improve response time, and
  • the addition of OpenAPI Specification (formerly Swagger Specification) to extend Aria’s core APIs to a wider set of programming languages. This will allow Aria customers to generate SDKs in over 40 languages, including the most popular ones such as Java, .Net, Perl, Ruby, PHP, JavaScript, C#, Python, and Go. The full list can be found here.

The following API calls have been improved in Release 15.0:

  • advance_virtual_datetime_m
  • authenticate_caller_m
  • clear_reg_uss_params_m
  • client_has_event_class_m
  • delete_reg_uss_params_m
  • gen_random_string_m
  • get_acct_balance_m
  • get_acct_coupon_details_m
  • get_acct_credits_m
  • get_acct_dunning_group_details_m
  • get_acct_groups_by_client_m
  • get_acct_nso_inclusion_list_m
  • get_acct_payment_history_m
  • get_acct_payment_methods_and_terms_m
  • get_acct_payment_methods_m
  • get_acct_plan_history_m
  • get_acct_statement_history_m
  • get_acct_tax_exempt_status_m
  • get_acct_trans_history_m
  • get_all_acct_contracts_m
  • get_cash_credits_details_m
  • get_client_countries_m
  • get_client_currencies_m
  • get_client_item_classes_m
  • get_client_item_images_m
  • get_client_plan_service_rates_m
  • get_cm_details_m
  • get_country_from_ip_m
  • get_credit_details_m
  • get_current_system_version_m
  • get_daily_batch_status_m
  • get_email_templates_m
  • get_instance_contract_m
  • get_invoice_details_m
  • get_invoice_history_m
  • get_order_items_m
  • get_order_m
  • get_plans_by_promo_code_m
  • get_statement_content_m
  • get_top_level_item_class_m
  • get_userid_has_ordered_sku_m
  • get_virtual_datetime_m
  • get_web_replacement_vals_m
  • kill_session_m
  • set_prov_engine_m
  • set_session_m
  • validate_session_m

Note: See Aria Crescendo APIs (Core API) for information on several updated API error returns.


Reason Code Table Updated For Cash Credits (DEV-8640)

On the Account's Payments & Credits screen, the Reason Code table for Cash Credits has been updated to more accurately describe the reason for the cash credit. 


Vantiv (Litle) Fraud Integration (DEV-8698)

One API was updated to support Vantiv (Litle) Fraud Integration:

API Updates
validate_acct_fraud_scoring_m
  • Added 6 new input fields:
    session_id: Value used with ThreatMetrix to identify Fraud Scoring Session.
    cust_field_1, cust_field_2, cust_field_3, cust_field_4, cust_field_5: Configurable values to be used with ThreatMetrix.
  • Added 1 new output field:
    proc_faud_score_result: Fraud score response provided by the payment processor. Used when automatically configured at payment processor to return pass, fail, or verify/suspect/unknown.

Vantiv Insights Marketing Tools (DEV-8699)

Several APIs were updated to support requests for card-related marketing information, per the below table:

API Updates
update_payment_method_m
  • Added new input field perform_marketing_insights_inquiry. Returns marketing information if your payment processor supports it and it is configured in Aria.
  • Added new output fields:
    proc_prepaid_indicator: Additional information passed back from processor identifying this card as a prepaid card (if available).
    proc_prepaid_available_balance: Additional information passed back from processor for available balance on prepaid card (if available).
    proc_prepaid_reloadable: Additional information passed back from processor identifying whether or not the prepaid card is reloadable (if available).
    proc_prepaid_card_type: Additional information passed back from processor to categorize the type of prepaid card (if available).
    Proc_affluence_indicator: Additional information passed back from processor indicating if card is affluent.
    Proc_issuing_country: Additional information passed back from processor indicating issuing country for the card.
    Proc_card_product_type: Additional information passed back from processor indicating whether the submitted card is a commercial or consumer card, providing you with additional data useful when analyzing sales patterns and/or planning marketing campaigns.
authorize_electronic_payment_m
validate_payment_information_m 
set_reg_uss_config_params_m Added new input field perform_marketing_insights_inquiry. Returns marketing information if your payment processor supports it and it is configured in Aria.

Support For New Payment Method: Merchant Specific Gift Cards (DEV-8700)

Several APIs were updated to support the new payment method, "Merchant Specific Gift Card" (Pay Method 40), per the below table:

API Updates
create_acct_complete_m New Allowable Value added for input field pay_method: 40 (Merchant Specific Gift Card).
update_acct_complete_m New Allowable Value added for input field pay_method: 40 (Merchant Specific Gift Card). 
update_payment_method_m New Allowable Value added for input field pay_method: 40 (Merchant Specific Gift Card). 
create_acct_billing_group_m New Allowable Value added for input field pay_method: 40 (Merchant Specific Gift Card). 
update_acct_billing_group_m New Allowable Value added for input field pay_method: 40 (Merchant Specific Gift Card). 
authorize_electronic_payment_m
  • Added new input field perform_balance_inquiry. When supported, this will provide a balance inquiry that reflects the current balance for prepaid cards and gift cards. 
  • Added new output field proc_gift_card_available_balance. This output field indicates the available balance on a gift card if available.
validate_payment_information_m
  • Added new input field perform_balance_inquiry. When supported, this will provide a balance inquiry that reflects the current balance for prepaid cards and gift cards. 
  • Added new output field proc_gift_card_available_balance. This output field indicates the available balance on a gift card if available.
set_reg_uss_config_params_m Added new input field perform_balance_inquiry. When supported, this will provide a balance inquiry that reflects the current balance for prepaid cards and gift cards. 

In addition, the following API calls support the ability to collect against an account's specified alternative payment method, and will honor that directive when "Merchant Specific Gift Card" has been specified as such:


Dynamic Soft Descriptor Field For Non-Credit-Card PayPal Payments (DEV-8728)

This feature enables the following API calls to pass dynamic data in the soft_descriptor field that will be associated with PayPal non-credit-card payment transactions and displayed to customers on their PayPal statements:

  • create_order_m
  • create_order_with_plan_m
  • collect_from_account_m
  • settle_account_balance_m

Note: This is in addition to the already supported feature when the PayPal Express Checkout end user is using a credit card as their "PayPal Method of Payment" (external/unknown to Aria).


update_order_m Collects Payments Successfully (DEV-8810)

When you attempt to collect a payment as part of the update_order_m API call, the payment is now successfully collected.


Field Parameter (client_acct_id) Added to Several APIs (DEV-8819)

The field parameter (client_acct_id) has been added to several APIs. This is an alt field for the acct_no, and the user_id parameters. The preference of this parameter will be:

  1. acct_no
  2. user_id
  3. client_acct_id

If only (2) inputs, then the order of preference is:

  1. acct_no
  2. client_acct_id

If inputs are given in more than (1) field then the first not NULL parameter will be taking preference. If the parameters are NULL, then the error "One of the following parameters is required" is displayed. The list of APIs include:

get_account_balance_m                        get_acct_comments_m                        

get_acct_contacts_m                             get_acct_details_all_m

get_acct_hierarchy_details_m               get_acct_open_charges_m                                

get_acct_plan_balance_m                     get_acct_plans_all_m

get_acct_plans_m                                  get_acct_universal_contract_m

get_aria_xml_statement_m                    get_queued_acct_plans_m

bulk_record_usage_m                            create_acct_billing_group_m

create_acct_dunning_group_m              record_external_payment_m                 

record_usage_m                                     void_transaction_m                                 

update_order_m                                      update_acct_status_m            

update_acct_plan_status_m


API Fixes 

  • When you use the update_acct_plan_multi_m API to: a) replace a plan with another plan that has a rollover then, as expected, the rollover happens and b) update the number of units of a plan that has a rollover then, as expected, the rollover happens and the account is assigned the same number of units of the rollover plan that were assigned to the previous plan. (TICKET-13853)
  • Correct error message is now displayed when passing an invalid surcharge_no in delete_surcharge_m. (TICKET-15159)
  • The delete_bundle_m API is now executing as expected when a valid bundle_nos input parameter is passed in the call. (TICKET-15506)
  • The "unexpected error" message is no longer returned when you use the update_acct_plan_multi_m API to assign a supplemental plan to a child account whose parent account is responsible for payment. (TICKET-15830)
  • When calling assign_acct_plan_m and update_acct_plan_multi_m with Master Plans that include mandatory Supplemental Plans, and specifying a value for override_bill_thru_date, supplemental plans with the same billing interval will now be prorated up to that override_bill_thru_date. The behavior for mandatory Supplemental Plans with different billing intervals will remain the same. (TICKET-16171)


WSDL File Locations

Stage Current

US https://secure.current.stage.ariasystems.net/api/Advanced/wsdl/15.0/complete_m-doc_literal_wrapped.wsdl
EUR None
AUS https://secure.current.stage.aus.ariasystems.net/api/Advanced/wsdl/15.0/complete_m-doc_literal_wrapped.wsdl

Stage Future

US https://secure.future.stage.ariasystems.net/api/Advanced/wsdl/15.0/complete_m-doc_literal_wrapped.wsdl
EUR https://secure.future.stage.cph.ariasystems.net/api/Advanced/wsdl/15.0/complete_m-doc_literal_wrapped.wsdl
AUS https://secure.future.stage.aus.ariasystems.net/api/Advanced/wsdl/15.0/complete_m-doc_literal_wrapped.wsdl

Production

US https://secure.ariasystems.net/api/Advanced/wsdl/15.0/complete_m-doc_literal_wrapped.wsdl
EUR https://secure.prod.cph.ariasystems.net/api/Advanced/wsdl/15.0/complete_m-doc_literal_wrapped.wsdl
AUS https://secure.prod.aus.ariasystems.net/api/Advanced/wsdl/15.0/complete_m-doc_literal_wrapped.wsdl

Object Query WSDL Files

Stage Current

US https://secure.current.stage.ariasystems.net/api/AriaQuery/wsdl/15.0/integration_services_m-doc_literal_wrapped.wsdl
EUR None
AUS https://secure.current.stage.aus.ariasystems.net/api/AriaQuery/wsdl/15.0/integration_services_m-doc_literal_wrapped.wsdl

Stage Future

US https://secure.future.stage.ariasystems.net/api/AriaQuery/wsdl/15.0/integration_services_m-doc_literal_wrapped.wsdl
EUR https://secure.future.stage.cph.ariasystems.net/api/AriaQuery/wsdl/15.0/integration_services_m-doc_literal_wrapped.wsdl
AUS https://secure.future.stage.aus.ariasystems.net/api/AriaQuery/wsdl/15.0/integration_services_m-doc_literal_wrapped.wsdl

Production

US https://secure.ariasystems.net/api/AriaQuery/wsdl/15.0/integration_services_m-doc_literal_wrapped.wsdl
EUR https://secure.prod.cph.ariasystems.net/api/AriaQuery/wsdl/15.0/integration_services_m-doc_literal_wrapped.wsdl
AUS https://secure.prod.aus.ariasystems.net/api/AriaQuery/wsdl/15.0/integration_services_m-doc_literal_wrapped.wsdl
Last modified

Tags

This page has no custom tags.

Classifications

This page has no classifications.