AMPS 2.6 Release

Handling PRICE_ADJUST pricing plans (WFAMPS-1479)

AMPS has the ability to support price changes during a subscription period when using the price model of "PRICE-ADJUST". The process takes the price and potential future price change and calculates the charge to be applied for the customer. The calculate charge is then applied as a custom rate on the subscription. This enhancement completes the handling by going through relevant subscriptions on a regular basis and updates the custom rate on a subscription based on the latest price and price change registered on the product.

Adjustments to Aria notifications Layout (WFAMPS-2257)

On client request the custom email templates have been updated for plan change, order confirmation, cancellation, and refund notifications. The emails based on the changed email templates are sent directly from ARIA/AMPS.

Improved performance of supplemental field handling (WFAMPS-2329)

A number of AMPS API's make significant use of supplemental fields on the product and subscription. Traversing the structures returned by ARIA API calls are time consuming. This enhancement addresses this issue. Rather than traversing the structures for each supplemental field, all supplemental fields are processed and provided as a single structure. This eliminates the need to traverse the structure completely for each supplemental field. This greatly reduces the processing time.

The enhancements have primarily been carried out in "SUBS Get Eligible Offerings [SubsGetEligibleOfferings]" as this flow was impacted the most.

Duplicate <InvoiceSubscriptions> tag in invoice (WFAMPS-2009)

tags was duplicated in the AMPS Financial Documents. The issue was caused by incorrect handling of surcharges including in the invoice. This has now been resolved, and the surcharge is now included with the first subscription (as defined by ARIA).

SubsManageSubscription API error when updating payment frequency (WFAMPS-2034)

This application fix resolves an issue where calls to modify the billing frequency on an existing subscription returned an error message even though the update was completed correctly. This issue has now been resolved and no additional error message is returned.

AMPS Event does not show plan details for invoices with multiple plans (WFAMPS-2178)

This application fix resolves an issue where AMPS events related to invoices, dunning notices and credit notes included only the first subscription of the invoice. Other subscriptions invoiced on the same invoice was not included. This issue has been resolved and the AMPS events now hold details on all subscriptions invoiced on the same invoice.

Contract Cancellation for B2B customers (WFAMPS-2182)

This application fix resolves an issue where a subscription was previously cancelled using the ANNIVERSARY or SPECIFIC-DATE method, and then a new cancellation using IMMEDIATE method was attempted. In this situation old contracts and future changes applied for the cancellation was not removed when doing the IMMEDIATE cancellation. This has now been resolved so that any future changes or contracts applied to the subscription is removed as part of the IMMEDIATE cancellation.

Updates to DiscDetails Table Fields (WFAMPS-2211)

This application fix resolves an issue where the discount percentage and value were incorrectly changed to decimal attributes in the database, but not in all API responses and other AMPS structures. This has now been resolved by changing the definition back to an integer field. AMPS currently does not support decimal values in percentage or value.

SPID unmatched payments - Multiple externalID Records (WFAMPS-2236)

This application fix resolves the issue where multiple active payment requests are encountered for the same payment identification. This caused the callback process to report errors as more than one payment was found. This fix resolves this issue, by also comparing the timestamp of the request in order to find the most recent request when both agreement ID and external ID is identical

OCR file is returned with ERROR, but transactions are registered, and error log is missing (WFAMPS-2238)

This application fix resolves an issue where the OCR (BANK) payment processing completed with errors, even though no errors occurred. This has now been resolved so that the process returns the proper information based on the processing.

Name of B2C customers not on dunning (WFAMPS-2240)

This application fix on client specific processes resolves an issue where the full name (Company Name) is not included in events sent to the client systems. The issue is solved by adding checks on the company name. If the company name is empty, then a new company name is built using the first name and last name also found in the event. Note this applies only to the custom specific event format.

Wrong Write-off reason code used (WFAMPS-2244)

This application fix resolves an issue where underpayments was written off with the wrong reason code causing the ERP process to incorrectly include the write-off. This has now been resolved by using the correct underpayment write off reason code.

OIOUBL: No Digital Subscription values (WFAMPS-2256)

This client specific application fix resolves an issue where OIOUBL attributes were set incorrectly. Due to missing values the data was output as ",," which caused confusion. This has now been resolved so that a "-" is inserted where the information is missing.

Update future changes table when modifying TitleCalendar (WFAMPS-2258)

This application fix resolves an issue where delivery stops was not handled correctly if the title calendar had been changed. When changing the title calendar for a given publishing date, the date when changes are sent to the distribution partner is also modified. However, for delivery starts/stops already registered this change was not applied. This has now been resolved so changing the title calendar will also modify any future delivery starts/stops.

Unable to cancel a subscription that has an activation date in the future (WFAMPS-2262)

This application fix resolves an issue where it was not possible to cancel a subscription that had not yet been activated, i.e. the status of the subscription was "INACTIVE". This issue has been resolved by returning an error to the caller if a change method other than IMMEDIATE is used. For subscriptions that have not yet been activated, it is not possible to schedule the cancellation on anniversary or on a specific date in the future.

Check Digit creation process issue (WFAMPS-2265)

When calculating the check digit appended to customer invoice references a problem was encountered with inconsistent calculation. In some situations the number was correct, while in others it was not. To overcome this issue the check digit calculation has been modified to use another method, and this eliminates the issue.

Payment Process unable to find relevant invoice for eFaktura (WFAMPS-2266)

This application fix resolves an issue with the payment process, where processing of eFaktura payments was unable to find the relevant invoice for which payment was collected. The process has been updated to use the additional billing group references (1 and 2) found on the invoice in AMPS. Using the additional billing group references, the appropriate customer invoice reference ID can then be found. If no invoice is found, the payment will be created as an unmatched payment for later manual handling.

REISSUE INVOICE creates two invoices when original invoice includes a surcharge (WFAMPS-2270)

This application fix resolves an issue where the "DOCM Manage Document [DocmManageDocument]" incorrectly created two invoices when reversing and reissuing the invoices. The problem was caused by incorrect handling of surcharges. This issue has now been resolved and the reissue of invoices now produce the correct charges.

Incorrect amount used when creating postings for credit notes (WFAMPS-2274)

This application fix resolves an issue where the wrong amount was used when creating revenue recognition postings in the ERP file. This issue has now been resolved.

Wrong ariaAccountNo used when processing immediately paid invoices (WFAMPS-2277)

This application fix resolves an issue where the ERP process used the wrong account number when retrieving invoice and other relevant details for processing. This was caused by running the process without account number as parameter, and in this case the process used the wrong value. This has now been resolved.

Cancellation issues – Maximum Credit Amount Exceeded (WFAMPS-2280)

This application fix resolves an issue where the cancellation process returned any error indicating that the maximum credit amount was exceeded when an attempt to create a credit note was made. The issue was caused by incorrect handling of service credits created due to update/downgrade of products, i.e. where the service credit was immediately consumed on a new invoice. The issue has been resolved and the service credits are correctly handled by the cancellation process.

AMPS Events Failures (WFAMPS-2285)

This application fix resolves an issue where AMPS events was not generated correctly when attempting to assign a new client defined ID to the account. The AMPS event processing expected the account ID, and though this is available when generating the event it now contains the new client defined ID. This issue has been resolved by changing the process to use the account number instead.

TitleManageCalendar API unable to update Publishing Date for Title Codes (WFAMPS-2298)

This application fix resolves an issue with the "TITLE Manage Calendar [TitleManageCalendar]" API where an error was returned when attempting to modify an existing calendar entry. This issue has been resolved by using the ID of the calendar entry, rather than the calendar date.

ERP process producing XML files with wrong TitleCode (WFAMPS-2346)

This application fix resolves an issue where ERP XML files was generated with the wrong title code information. This was caused by the configuration of the product where multiple title codes are defined in product field "TitleCode". The ARIA API used to retrieve the title code information does not always return the title codes in the right sequence. This issue has now been resolved, by changing the call to another ARIA API which returns the information in the right sequence.