Version 6.4 Release Notes. Aria Subscription Billing Platform 6.4 Release Notes

Transcription

1 Aria Subscription Billing Platform 6.4 Release Notes

2 COPYRIGHT 2012 ARIA SYSTEMS, INC ALL RIGHTS RESERVED Aria Systems, the Aria logo, LiveRelease, DSM, and SmartRec are trademarks or registered trademarks of Aria Systems, Inc. All other trademarks shown are the property of their respective owners. The use of the names of other companies and their trademarked products are for reference purposes only. No portion of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, recording or information storage and retrieval systems, for any purpose other than the authorized person s or organization s use without express written permission from Aria Systems, Inc. This documentation is furnished for informational use only, is subject to change without notice, and should not be construed as a commitment by Aria Systems. Aria Systems assumes no responsibility or liability for any errors or inaccuracies that may appear in the informational content contained in this document. For more information: Aria Systems, Inc 600 Reed Road Suite 302 Broomall, PA Phone: E mail: [email protected] Web site:

3 Revision History Date Version Description 12/13/ Stage release. 12/21/ Added the following tickets: Ticket BUG 1006 on Page 13. Ticket DEV 2502 on Page 13. Ticket DEV 2503 on Page 13. Ticket DEV 2481 on Page 15. Ticket DEV 2487 on Page 15. Ticket DEV 2490 on Page 15. Ticket DEV 2495 on Page 16. Ticket DEV 2308 on Page 17. Ticket DEV 2391 on Page 17. Ticket DEV 2426 on Page 18. Ticket BUG 1029 on Page 19. Ticket BUG 1048 on Page 19. Ticket BUG 1062 on Page 19. Ticket BUG 1067 on Page 19. Ticket BUG 1087 on Page 19. Ticket DEV 2514 on Page 19. Ticket DEV 2370 on Page 22. Ticket DEV 2402 on Page 23. Ticket BUG 881 on Page 24. Ticket BUG 906 on Page 24. Ticket BUG 1054 on Page 24. Ticket BUG 1063 on Page 25. Ticket BUG 1075 on Page 25. Ticket BUG 1082 on Page 25. Ticket BUG 1092 on Page 25. Ticket BUG 1137 on Page 25. 3

4 Table of Contents PURPOSE OF THIS DOCUMENT... 6 ARIA SUBSCRIPTION BILLING PLATFORM 6.4 OVERVIEW... 7 RELEASE DATE... 7 WSDL FILE LOCATIONS... 7 Stage Current WSDL File Locations... 7 Stage Future WSDL File Locations... 7 Production WSDL File Locations... 7 ADMINTOOLS SYSTEM REQUIREMENTS... 8 Supported Browsers... 8 Java Settings... 8 Screen Resolution... 8 ARIA6 SYSTEM REQUIREMENTS... 8 Supported Browsers... 8 ADMINTOOLS APPLICATION... 8 ARIA WEB SERVICES API... 8 ADMINTOOLS APPLICATION NEW FEATURES... 9 Ticket DEV 2453: Standard Aria XML statement document, with new associated event and API method... 9 IMPROVEMENTS FIXES Ticket BUG 862: Cannot replace a custom rate schedule with a plan rate schedule REMOVALS KNOWN ISSUES ARIA NEW FEATURES Ticket BUG 1006: Need new usage threshold events for warning percentage Ticket DEV 2502: Create old "Client Supplemental Fields" module in NGUI as " Template Fields" Ticket DEV 2503: Ability to choose alternate rate schedules during plan changes via UI Ticket DEV 2453: Standard Aria XML statement document, with new associated event and API method Ticket DEV 2481: Add ability to queue up future plan change via UI Ticket DEV 2487: VIE In Plan Creation Ticket DEV 2490: Add option to open new copied plan when copying a plan Ticket DEV 2495: Create supplemental plan exclusion group module in NGUI IMPROVEMENTS Ticket DEV 2308: Offset Months for determining end of plan assignment Ticket DEV 2391: Ability to Remove Coupon Through UI Ticket DEV 2426: Increase Number of Significant Digits for Rate Schedules, Usage Charges, and Usage Record currency values FIXES Ticket BUG 1029: Error when trying to load the Activity Load data Ticket BUG 1048: Account Overview has Recent Transactions sorting in the wrong order Ticket BUG 1062: Cannot add a service to a plan in NGUI

5 Ticket BUG 1067: Allow substituting in plan description in to mail templates Ticket BUG 1087: UI does not validate if the queued plan has an effective date in the past or is the current date (related to DEV 2455) Ticket DEV 2466: Template Plan Input Fields Not Inserting Correctly In IE Ticket DEV 2514: Activity Loader Module does not escape characters REMOVALS KNOWN ISSUES ARIA WEB SERVICES API NEW FEATURES Ticket DEV 2453: Standard Aria XML statement document, with new associated event and API method IMPROVEMENTS Ticket DEV 2308: Offset Months for determining end of plan assignment Ticket DEV 2370: Event Notification Provisioning enhanced to add Client Defined Object Supplemental Fields Ticket DEV 2402: Improved presentation of tax on statements FIXES Ticket BUG 749: Account collected balance due on an unexpected day Ticket BUG 881: Event 505 is generated multiple times when invoice is generated by batch Ticket BUG 906: Proration logic does not populate START_DATE and END_DATE when creating invoice with negative amount to account for reverse charges Ticket BUG 1003: get_statement_for_invoice API errors when more than 1 payment applied to invoice Ticket BUG 1054: External description of coupon/discount rule is not used on a prorated invoice Ticket BUG 1055: get_client_plan_service_rates API returns ORA error Ticket BUG 1063: Statement Stub does not honor Client Parm for Suppressing $0 line items for Child Items on Parent Child Statement Ticket BUG 1075: Direct Post no_invoice_promotion = 0 failure when invoice_no does not exist Ticket BUG 1082: Discount Rule Frequencies are not being considered when pro rated when creating account or assigning a supplemental plan Ticket BUG 1092: DEV 2455 related issues Ticket BUG 1137: Object Query API get_invoice_details does not return tax information REMOVALS KNOWN ISSUES ARIA WEB SERVICES API 6.4 SUITE CHANGES

6 Purpose of this Document This release notes document provides you with information about the following: New features: Additions to the functionality available in the platform. Improvements: Changes that enhance existing functionality in the platform. Fixes: Resolutions for bugs reported by our clients and Aria Systems staff. Removals: Features removed from the platform. Known Issues: Known bugs in the platform. Aria Web Service API suite changes: An identification of the API suites that contain changed or new API calls. 6

7 Aria Subscription Billing Platform 6.4 Overview Release Date 1/23/13 WSDL File Locations Stage Current WSDL File Locations The WSDL files for the Web Services API in the stage current environment are located here: US: doc_literal_wrapped.wsdl EUR: None Stage Future WSDL File Locations The WSDL files for the Web Services API in the stage future environment are located here: US: doc_literal_wrapped.wsdl EUR: doc_literal_wrapped.wsdl Production WSDL File Locations The WSDL files for the Web Services API in the production environment are located here: US: doc_literal_wrapped.wsdl EUR: doc_literal_wrapped.wsdl 7

8 AdminTools System Requirements Supported Browsers Internet Explorer 7 to 9 Firefox 3 to 8 Java Settings Java 1.5 Screen Resolution 1024 x 768 or higher Aria6 System Requirements Supported Browsers Internet Explorer 9 Firefox 9 AdminTools Application AdminTools is a web based application that you and Aria Systems staff can use to: Select options for managing your implementation of Aria. Maintain your customers accounts. View dashboards summarizing data such as revenue and account holder activity. Manage plans, coupons, promotions, and inventory Items. View, schedule, print, and download reports. Aria Web Services API The Aria Web Services API (application programming interface) provides you with API calls that you can use to: Develop your own applications for creating and modifying your customers accounts. Integrate Aria with your company s ERP and finance systems. Deliver real time sales information to your company s portals. Populate critical business systems with customer information. 8

9 AdminTools Application 6.4 New Features Ticket DEV 2453: Standard Aria XML statement document, with new associated event and API method You can now have Aria generate statements for your customers as XML documents. If you want to be informed when XML statements for your customers have been generated, you can subscribe to a new event called Account Message Type "XML Statement" Requires Sending (Event ID 442). Please note: If you want to subscribe to this new event, you will need to use version 3.1 of the account notifications event group. Please contact Aria Systems Customer Support get access to this version and the applicable XSD and DTD files. To have Aria generate statements for your customers as XML documents: In AdminTools, click Control Panel > click System Settings > click Notifications > click XML Statement Distillation Option > select your desired Value to specify how you want Aria to generate XML statements. Please note: If you select Aria XML Statements WITH Usage Detail, that may result in very large XML documents. Aria will generate XML statements for customers with only the following notification methods: 1: HTML , 2: Text , 3: Text w/link to HTML, 6: Printable & Text , 7: Printable & HTML w/surcharge, 9: PDF (Printing required, no ), 10: PDF (delivered by ), 11: PDF (Printing req & )w/surcharge, 12: PDF (Printing req, no )w/surcharge, 13: XML Master File, and 14: PDF Master File. You can use the update_acct_notify_method, create_acct_complete, or update_acct_complete API call to set a customer s notification method. Please see the Account API documentation in Parature for more information about the API calls listed above. To subscribe to the Account Message Type "XML Statement" Requires Sending event: In AdminTools, click Control Panel > click Event Notification > click Manage > click Accounts Message > click Edit > select Account Message Type "XML Statement" Requires Sending. Please see Ticket DEV 2453 on Page 21 for information about a new API call that you can use to retrieve XML statements. 9

10 Improvements There are no improvements in this release of the AdminTools application. 10

11 Fixes Ticket BUG 862: Cannot replace a custom rate schedule with a plan rate schedule You can now successfully replace an account s custom rate schedule with a plan rate schedule. 11

12 Removals There are no removals in this release of the AdminTools application. Known Issues There are no known issues in this release of the AdminTools application. 12

13 Aria6 New Features Ticket BUG 1006: Need new usage threshold events for warning percentage You can now subscribe to the following new event notifications to monitor your customer s unbilled usage balances based on the unbilled usage balance thresholds that you set for your customers and your specified Unbilled Usage Threshold Adjustment Percentage: 507: Account's unbilled usage value is now OVER OR EQUAL TO client defined MTD threshold percentage. 508: Account's unbilled usage value has crossed UNDER client defined MTD threshold percentage. 509: Account's unbilled usage value is now OVER OR EQUAL TO client defined PTD threshold percentage. 510: Account's unbilled usage value has crossed UNDER client defined PTD threshold percentage. Example: You set the unbilled usage balance threshold for a customer to $100, you set the Unbilled Usage Threshold Adjustment Percentage to 80, and you subscribed to event 507. You will receive an event notification when that customer s unbilled usage balance reaches or goes above $80. To subscribe to these events: In Aria6, click Configuration > click Notifications > click Events > click Usage Monitoring > select the desired events.please note: If you want to subscribe to the new event listed above, you will need to use version 3.1 of the usage monitoring event group. Please contact Aria Systems Customer Support to get access to this version and the applicable XSD and DTD files. The following events will continue to be based only on the unbilled usage balance thresholds that you set for your customers: 501, 502, 503, and 504. Please see the Aria6 Usage Guide for more information about usage monitoring. Please see the Aria6 Event Notification User Guide for more information about setting up event notification. Ticket DEV 2502: Create old "Client Supplemental Fields" module in NGUI as " Template Fields" You can now create template fields if there is additional information that you want to include in your statement templates and templates. template fields were known as client supplemental fields in AdminTools. Example: You can create an template field for a VAT ID. To create template fields: In Aria6, click Configuration > click Notifications > click Template Fields > click Create New. Please contact Aria Systems Customer Support to enable the Template Fields module in Aria6 and to specify which template fields you want to include in your statement templates and templates. 13

14 Ticket DEV 2503: Ability to choose alternate rate schedules during plan changes via UI When you change a customer s master plan or assign or replace a supplemental plan, you can now change the rate schedule. To assign a custom rate schedule during a plan change: In Aria6, click Accounts > click Search > select a search option > search for an account > click on an account number > click Plans & Services > do either of the following: Click on the Master Service Plan tab > click Change Master Service Plan > select an existing rate schedule or choose Custom Rates to enter a special discounted rate schedule for the customer. OR Click on the Supplemental Plans tab. > click Replace or Assign > select an existing rate schedule or choose Custom Rates to enter a special discounted rate schedule for the customer. Ticket DEV 2453: Standard Aria XML statement document, with new associated event and API method You can now have Aria generate statements for your customers as XML documents. If you want to be informed when XML statements for your customers have been generated, you can subscribe to a new event called Account Message Type "XML Statement" Requires Sending (Event ID 442). Please note: If you want to subscribe to this new event, you will need to use version 3.1 of the account notifications event group. Please contact Aria Systems Customer Support to get access to this version and the applicable XSD and DTD files. To have Aria generate statements for your customers as XML documents: Click Configuration > click Notifications > click Notification Settings > click XML Statement Distillation Option (you may have to go to the next page of notification settings to see this option) > select your desired Value to specify how you want Aria to generate XML statements. Please note: If you select Aria XML Statements WITH Usage Detail, that may result in very large XML documents. Aria will generate XML statements for customers with only the following notification methods: 1: HTML , 2: Text , 3: Text w/link to HTML, 6: Printable & Text , 7: Printable & HTML w/surcharge, 9: PDF (Printing required, no ), 10: PDF (delivered by ), 11: PDF (Printing req & )w/surcharge, 12: PDF (Printing req, no )w/surcharge, 13: XML Master File, and 14: PDF Master File. Please see the Aria6 Account Management Guide in Parature or on Developer Central for information about changing a customer s notification method using Aria6. You can use the update_acct_notify_method, create_acct_complete, or update_acct_complete API call to set a customer s notification method. Please see the Account API documentation in Parature for more information about the API calls listed above. 14

15 To subscribe to the Account Message Type "XML Statement" Requires Sending event: In Aria6, click Configuration > click Notifications > click Events > click Account Notifications > select Account Message Type "XML Statement" Requires Sending. Please see Ticket DEV 2453 on Page 21 for information about a new API call that you can use to retrieve XML statements. Please see the Aria6 Event Notification User Guide for more information about setting up event notification. Ticket DEV 2481: Add ability to queue up future plan change via UI You can now use Aria6 to schedule a plan change for a future date. To use this feature: In Aria6, click Accounts > click Search > select a search option > search for an account > click on an account number > click Plans & Services > do either of the following: Click on the Master Service Plan tab > click Change Master Service Plan or click Change Num. Plan Units > select Assign in Future. OR Click on the Supplemental Plans tab. > click Remove, Replace, or Assign, or click Plan Units> select Assign in Future. To see or modify plan changes that were scheduled for a future date using Aria6 or API calls: In Aria6, click Accounts > click Search > select a search option > search for an account > click on an account number > click Plans & Services > click Future Plan Changes. Please see the Aria6 Account Management Guide on Developer Central or in Parature for more information about changing a customer s plan assignment. Ticket DEV 2487: VIE In Plan Creation If you have VIE (Virtual Inventory Engine) set up in your Aria implementation and you sell virtual inventory, you can now add resource types to your plans. Please note: If you want to add resource types to a plan, you must first add at least one recurring service to the plan. To add resource types to your plans: Click Products > click Plans > create or edit a plan > click Virtual Inventory > select Yes > select the resource type(s) that you want to add to the plan. Please see the Aria6 Product Management and Marketing Guide for more information. 15

16 Ticket DEV 2490: Add option to open new copied plan when copying a plan When you copy a plan, you now have access to a button that will open the new plan as soon as it has been created. To use this feature: Click Products > click Plans > click on the plan that you want to copy > click Copy This Plan > click Copy > click Open New Plan. Ticket DEV 2495: Create supplemental plan exclusion group module in NGUI You can now use Aria6 to create plan groups (plan exclusions) for supplemental plans to prevent customers from subscribing to more than one supplemental plan in the same plan group at the same time. In Aria, you cannot assign a customer a new supplemental plan that is in the same plan group as the customer s current supplemental plan without first canceling the customer s current supplemental plan. However, you can assign a supplemental plan that is in a different plan group from the customer s current supplemental plan. Example: You have a customer who is subscribed to the 500 Monthly Minutes master plan that is associated with the supplemental plans listed below. Then you create the following supplemental plan groups: Supplemental plan group 1 containing: Supplemental plan A: 500 Texts a Month Supplemental plan B: 1000 Texts a Month Supplemental plan C: Unlimited Texting Supplemental plan group 2 containing: Supplemental plan D: 2 GB Data a Month Supplemental plan E: 10 GB Data a Month Supplemental plan F: Unlimited Data A customer who is subscribed to Plan A can also subscribe to Plan D, E, or F. However, that customer cannot subscribe to plan B or C without canceling plan A first. Please note: All of the supplemental plans in the same plan group have to be associated with the same master plan or you will not be able to assign any of the plans in the group to a customer. To create a plan group: In Aria6, click Products > click Plan Exclusions > click New. Please see the Aria6 Product Management and Marketing Guide for more information. 16

17 Improvements Ticket DEV 2308: Offset Months for determining end of plan assignment When you make changes to a customer s master or supplemental plan assignment and you select the option On Anniversary, you can now set an Offset Interval to specify the additional number of billing intervals after the anniversary day on which you want the plan change to go into effect. Example: You have a customer whose anniversary day is on the 15th of every month and who is subscribed to an annual master plan that will be canceled on 12/15/13. On 3/10/13, you assign the customer a quarterly supplemental plan. You want the supplemental plan to be canceled on the same day as the master plan. If you remove the supplemental plan on 6/10/13 and you set the Offset Interval to 2, then that supplemental plan will be canceled on 12/15/13. To use this feature: In Aria6, click Accounts > click Search > select a search option > search for an account > click on an account number > click Plans & Services > do either of the following: Click on the Master Service Plan tab > click Change Master Service Plan or click Change Num. Plan Units > select Assign on Anniversary > type in the desired number of billing intervals in the Offset Interval box. OR Click on the Supplemental Plans tab. > click Remove, Replace, or Assign, or click Plan Units> select Assign on Anniversary or De assign on Anniversary> type in the desired number of billing intervals in the Offset Interval box. Ticket DEV 2391: Ability to Remove Coupon Through UI You can now cancel any coupon that has been assigned to a customer. Cancelling a coupon will remove all of the unconsumed credits generated by the coupon. To cancel a coupon: In Aria6, click Accounts > click Search > select a search option > search for an account > click on an account number > click Payments & Credits > click on the Coupons tab > click Cancel next to any coupon that you want to cancel. 17

18 Ticket DEV 2426: Increase Number of Significant Digits for Rate Schedules, Usage Charges, and Usage Record currency values Aria now supports currency amounts that contain up to nine decimal places. This means that you can now upload usage records into Aria with currency amounts containing up to nine decimal places and you can enter currency amounts containing up to nine decimal places in your rate schedules. Please note: Aria will calculate invoice totals using the number of decimal places specified in your pricing and the currency amounts assigned to your usage records. However, due to payment gateway requirements, the total amounts for which Aria will bill your customers will be rounded to two decimal places. 18

19 Fixes Ticket BUG 1029: Error when trying to load the Activity Load data You no longer encounter a JSON error when you go to the Activity Loader screen under Configuration > Integrations. Ticket BUG 1048: Account Overview has Recent Transactions sorting in the wrong order On the Account Overview screen, each customer s recent transactions are now displayed correctly in reverse chronological order (newest to oldest). Ticket BUG 1062: Cannot add a service to a plan in NGUI You can now save a new service that you added to a plan that has already been assigned to a customer even if the service rates are in a European currency, you are using or European currency format mask, or the rates contain three decimal places. Ticket BUG 1067: Allow substituting in plan description in to mail templates When you add the [insertplanlongdesc] input to an template, that input is now successfully replaced with the plan description in the corresponding messages sent to your customers. Ticket BUG 1087: UI does not validate if the queued plan has an effective date in the past or is the current date (related to DEV 2455) When you change the effective date for a scheduled plan change, you can now enter only a date that is in the future. Ticket DEV 2466: Template Plan Input Fields Not Inserting Correctly In IE9 If you are using Internet Explorer 9, when you add plan inputs to an template, the inputs are now displayed in the message body instead of at the top of the page. Ticket DEV 2514: Activity Loader Module does not escape characters If there are special characters such as quotes in your Universal Activity Loader data file name, a JSON error is no longer displayed on the Activity Loader screen. 19

20 Removals There are no removals in this release of Aria6. Known Issues There are no known issues in this release of Aria6. 20

21 Aria Web Services API 6.4 New Features Ticket DEV 2453: Standard Aria XML statement document, with new associated event and API method After you receive event notifications about generated XML statements, you can retrieve those statements using a new API call named get_aria_xml_statement. Each event notification will contain an xml_statement_no that you can pass into the get_aria_xml_statement API call. After retrieving the statements, you may choose to format them based on your business needs for presentation to your customers or transfer them to your financial systems. Please see Ticket DEV 2453 on Page 9 for more information about working with XML statements in AdminTools. Please see Ticket DEV 2453 on Page 14 for more information about working with XML statements in Aria6. Please see the Aria6 Event Notification User Guide for more information about setting up event notification. Please see the Transaction API documentation for more information about using the get_aria_xml_statement API call. 21

22 Improvements Ticket DEV 2308: Offset Months for determining end of plan assignment When you use the API calls listed below to change a customer s master or supplemental plan assignment and you use assignment directive 1, you can now pass in a new input parameter called offset_interval to specify the additional number of billing intervals after the anniversary day on which you want the plan change to go into effect. Example: You have a customer whose anniversary day is on the 15th of every month and who is subscribed to an annual master plan that will be canceled on 12/15/13. On 3/10/13, you assign the customer a quarterly supplemental plan. You want the supplemental plan to be canceled on the same day as the master plan. If you remove the supplemental plan on 6/10/13, you can pass 2 into the set the offset_interval field, then that supplemental plan will be canceled on 12/15/13. offset_interval has been added to the inputs of the API calls listed below: update_master_plan update_acct_complete assign_supp_plan assign_supp_plan_multi replace_supp_plan modify_supp_plan cancel_supp_plan Please see the Account API documentation in Parature for more information. Ticket DEV 2370: Event Notification Provisioning enhanced to add Client Defined Object Supplemental Fields Event notifications in the Accounts group now contain product field names and values for any master or supplemental plans included in an event notification. (Product fields were formerly known as supplemental object fields.) Please note: If you want to receive product field information in your account based event notifications, you will need to use version 3.1 of the Accounts event group. Please contact Aria Systems Customer Support get access to this version and the applicable XSD and DTD files. Please see the Aria6 Event Notification User Guide for more information about setting up event notification. 22

23 Ticket DEV 2402: Improved presentation of tax on statements Aria can now display charges and taxes on you customers statements in the following ways: Display the charge without tax. Display the charge with tax on the same line. Display the taxes in separate tax summary table. Display the tax rate percentage applied to each charge. Please contact Aria Systems Customer Support to specify how you want taxes and charges to be displayed on your customers statements. 23

24 Fixes Ticket BUG 749: Account collected balance due on an unexpected day For customers with electronic payment methods, Aria will now collect payments on the applicable billing date even if invoices are generated on a day other than the billing date. Ticket BUG 881: Event 505 is generated multiple times when invoice is generated by batch You no longer receive a separate instance of event notification 505 (Account's unbilled usage value is now OVER OR EQUAL TO remaining unapplied service credit balance) for each service credit. Instead, you now receive one instance of event notification 505 based on the total unapplied service credit balance for all service credits that apply to an account. Ticket BUG 906: Proration logic does not populate START_DATE and END_DATE when creating invoice with negative amount to account for reverse charges. The start and end dates for invoice line items are now displayed on invoices that contain negative currency amounts. Ticket BUG 1003: get_statement_for_invoice API errors when more than 1 payment applied to invoice If you call the get_statement_for_invoice API method and there is more than one payment applied to the specified invoice, you no longer encounter an ORA error. Ticket BUG 1054: External description of coupon/discount rule is not used on a prorated invoice Discount rule descriptions are now displayed in your prorated invoices. Ticket BUG 1055: get_client_plan_service_rates API returns ORA error. When you call the get_client_plan_service_rates API method, you no longer encounter an ORA error. 24

25 Ticket BUG 1063: Statement Stub does not honor Client Parm for Suppressing $0 line items for Child Items on Parent Child Statement If you have the option in your Aria implementation set to suppress $0 line items for child items on parent child statements, when a $0 invoice is generated for a child account, child invoice information is no longer included in the parent statement. Ticket BUG 1075: Direct Post no_invoice_promotion = 0 failure when invoice_no does not exist When you use Direct Post and you have set the no_invoice_promotion parameter to 0, if an error occurs, Direct Post no longer fails. Instead, Direct Post completes whatever error handling steps you specified in your registration or user self service application. Ticket BUG 1082: Discount Rule Frequencies are not being considered when pro rated when creating account or assigning a supplemental plan The maximum number of applications per account is now honored when you create an account and generate a prorated invoice or you assign a supplemental plan to an account. Ticket BUG 1092: DEV 2455 related issues The issues listed below been resolved. When you use API calls to schedule plan changes for a future date: The correct expected fees are now returned based on the specified number of plan units. If you pass false into the do_write parameter, the following error code is now returned: (Invalid do_write and assignment directive combination for queuing plan). If you pass in an effective_date that is not in the future and you use assignment directive 7 to 11, the following error code is now returned: (The Effective Date must be in the future, "YYYY MM DD" format, and a valid date). Any assigned custom rates are now reflected in the output parameters. When you use the update_master_plan API call to change a master plan, the master plan that you specified is now assigned to the customer. When you call the assign_supp_plan_multi API method and leave the do_write field blank (causing it to default to true), the specified plan assignment is now completed. Any applicable proration results will not be returned. However, when the plan change is completed on your specified future date, the applicable proration results will be applied to the account and you will see the returned proration results on the Future Plan Changes screen for the corresponding account. Ticket BUG 1137: Object Query API get_invoice_details does not return tax information When you call the get_invoice_details API method, tax information is now returned. 25

26 Removals There are no removals in this release of the Aria Web Services API. Known Issues There are no known issues in this release of the Aria Web Services API. 26

27 Aria Web Services API 6.4 Suite Changes The table below identifies the API suites that contain changed or new API calls. Please see to the API documentation in Parature for more information about the changes/additions in the API suites. API Suite Account API ARC Maintenance API ARC Transaction API Object Query API Registration/USS (User Self Service) Application Parameter Registry API System Services API Transaction API USS (User Self Service) SSO (Single Sign On) Services API Virtual Inventory Engine (VIE) Transaction API Changes Made? Yes No No No No No Yes No No 27