Skip to main content
Aria Knowledge Central

AMPS 2.11 Release

Overview

 
Enhancements and fixes to Aria Media Publishing Suite (AMPS) for this release are described below.

Release Date

8 October 2021

Release 2.11 Contents

  1. New and Improved Functionality
    1. Making Trials and Rollovers available (WFAMPS-81)
    2. Enable Cancellation Reason in Member Cancellation events (WFAMPS-1887)
    3. Generate AMPS events for subsManageDiscount actions (WFAMPS-1895)
    4. Unable to distinguish split addresses in AMPS events (WFAMPS-2452)
    5. Change FARPAY file integration from FTP to API (WFAMPS-2455)
  2. Application Fixes
    1. Updates to Dunning Email Notifications processes in AMPS (WFAMPS-2450)
    2. InvoiceTaxSpecification not set correctly (WFAMPS-2454)
    3. Manage Title Calendar API does not allow to delete publishing date (WFAMPS-2471)
    4. Aria event processing fails to create AMPS event (WFAMPS-2509)
    5. Update of plan units from 1 to 2 with IMMEDIATE change method does not generate new charges (WFAMPS-2546)
    6. Failing 906 Events (WFAMPS-2581)
    7. Subscriptions is set to INACTIVE though they should be ACTIVE (WFAMPS-2598)
    8. List Subscription should not be returning SPECIAL subscription (WFAMPS-2599)
    9. List Subscription to return additional info in response (WFAMPS-2600)
    10. Processing credit notes does not correctly determine if original invoice has been paid (WFAMPS-2601)
    11. Unable to raise credit note on invoice with an underpayment write-off (WFAMPS-2602)
    12. ERPProcessID not set when handling Refunds (WFAMPS-2608)
    13. Replace Starts new delivery at wrong address no (WFAMPS-2610)
    14. AMPS Migration - invoicing_option value not being honored (WFAMPS-2611)
    15. Standard AMPS Invoice XML to include customer type value defined on the account (WFAMPS-2613)
    16. Retrieve Invites API does not return invite for Member Account if MPI is not provided in the input (WFAMPS-2620)
    17. Different Title Code values required in 'CustomerSystem' and 'Product' in file to DI (WFAMPS-2621)
    18. Payment Callback not updating GatewayPaymentID (WFAMPS-2629)
    19. Incorrect Header Validation on TK01 records for incoming collection file from BGC (WFAMPS-2630)
    20. Subscription member sharing is not set to inactive when main user is inactive (WFAMPS-2633)
    21. Update dimension for Customer ERP XML (WFAMPS-2635)
    22. Migration does not set client_payment_method_id (WFAMPS-2637)
    23. When updating account using AriaAccountID error is returned (WFAMPS-2538)
    24. Account GDPR Delete account event error due to account being deleted (WFAMPS-2639)
    25. ERP not setting correct fee dimensions for Credit Notes (WFAMPS-2641)
    26. Stops are wrongly created on MPI's with replacement (WFAMPS-2700)

 

New and Improved Functionality

This section covers the release notes related to new functionality and capabilities added to AMPS. For this release the following functionality have been made available:

  • Making Trials and Rollovers available (WFAMPS-81)
  • Enable Cancellation Reason in Member Cancellation events (WFAMPS-1887)
  • Generate AMPS events for subsManageDiscount actions (WFAMPS-1895)
  • Unable to distinguish split addresses in AMPS events (WFAMPS-2452)
  • Change FARPAY file integration from FTP to API (WFAMPS-2455)

Each of the above enhancements are described in further below

Making Trials and Rollovers available (WFAMPS-81)

This enhancement introduces the ability to return details on trials and rollovers as defined in the ARIA Product catalog. The information returned can be used in other API calls, for example when adding contracts or other actions. The enhancement will also see details being returned on daily and weekly billing in order to prepare for that functionality being added to AMPS.

The enhancement has changes to the following AMPS API calls:

  • Retrieve Product [ProdRetrieveProduct] - an existing API that on return will contain details on trials, rollovers, contract rollovers and billing frequencies for the products
  • Get Eligible Offerings [SubsGetEligibleOfferings] – an existing API that on return will contain details on trials, rollovers, contract rollovers and billing frequencies for the offerings
  • Retrieve Subscription [SubsRetrieveSubscription] - an existing API that on return will contain details on trials, rollovers, contract rollovers and billing frequencies for the subscriptions assigned to an account.

Enable Cancellation Reason in Member Cancellation events (WFAMPS-1887)

This enhancement sees the addition of cancellation reason to the Member Cancelled (SUBSCRIPTION/0012) event. The cancellation reason provided is the cancellation reason used when cancelling the actual subscription and will be identical to the cancellation reason found in the Subscription Cancelled events.

Generate AMPS events for subsManageDiscount actions (WFAMPS-1895)

This enhancement sees the introduction of AMPS events when adding, modifying, or removing discounts from a given subscription using the "Manage Discount [SubsManageDiscount]" API. The API itself is not updated. The following events are triggered by AMPS:

  • SUBSCRIPTION/0017 - Discount Added - triggered when a new discount is added to a subscription
  • SUBSCRIPTION/0018 - Discount Modified - triggered when an existing discount is modified for a given subscription.
  • SUBSCRIPTION/0019 - Discount Removed - triggered when an existing discount is removed from a given subscription.

Unable to distinguish split addresses in AMPS events (WFAMPS-2452)

This enhancement sees the ability to produce AMPS events where split address updates are combined into a single event, rather than the current separate events. Currently making an address change covering split address will cause two or more "Distribution Changed [DISTRIBUTION/0001", "Distribution Stopped [DISTRIBUTION/0002]" or "Distribution Started [DISTRIBUTION/0003]" events for the single address change. With this enhancement it is now possible to combine the change into a single event.

Whether to use the current functionality or the new combined is controlled by an AMPS parameter called "Distribution Address Change Event [DISTAddrChgEvent]". Producing separate events are the default option. The parameter can be changed using the "Manage Parameter Configuration [SolmManageParamConfig]" API call. The following options exist:

  • SINGLE - If this parameter is set as default, DIST change address API will generate separate event for each address change is registered.
  • COMBINE - If this parameter is set as default, DIST change address API will generate combined events for address changes for each MPI found in request.

Change FARPAY file integration from FTP to API (WFAMPS-2455)

This enhancement sees the enablement of API integration with FARPAY in addition to the current batch file interface. The enhancement implements the ability to send invoices, credit notes, and dunning notices to FARPAY via their published API. The API is invoked when a financial document is produced by AMPS, and AMPS will with regular interval check the status of the document and update appropriate tables with the outcome.

To enable the functionality for FARPAY the relevant document destination must be changed in the "Title Payment Option Document Destination [TitlePayOptionDocDest]" table. The following details must be updated:

  • "Payment Option Document Destination Type [TitlePayOptionDocDestType]" - must be changed to "REST". It is currently set to "SFTP".
  • "Payment Option Document Destination Location [TitlePayOptionDocDestLocation]" - must be changed to the URL provided by FARPAY in order to reach the API.

Application Fixes

This version sees the following application fixes deployed:

Updates to Dunning Email Notifications processes in AMPS (WFAMPS-2450)

This issue is related to the a customer's specific dunning emails sent to customers from workflow. The existing implementation sent only a single format to customers, but this has now been changed to use different formats for different payment options and dunning steps.

InvoiceTaxSpecification not set correctly (WFAMPS-2454)

This issue is related to the "AMPS Financial Document" XML files holding incorrect tax specifications in some situations. This has been resolved by ensuring that each charge/credit line item is correctly processed for taxes.

Manage Title Calendar API does not allow to delete publishing date (WFAMPS-2471)

This issue is related to the "Manage Title Calendar [TitleManageCalendar]" API which did not allow callers to delete specific publishing days in the calendar. This issue has been resolved, by allowing REMOVE actions to correctly remove publishing days and also update any pending address changes to cater for this change.

Aria event processing fails to create AMPS event (WFAMPS-2509)

This issue is a problem where additional payments was created in AMPS even though the payment actually failed. The problem occurs only for payments collected via an ARIA managed payment gateway. This issue has now been resolved.

Update of plan units from 1 to 2 with IMMEDIATE change method does not generate new charges (WFAMPS-2546)

This issue is a problem related to the REPLACE action in "Manage Subscription [SubsManageSubscription]" where an update of units did not trigger additional prorated charges. This has now been resolved. Also a problem existed where the delivery address was not set correctly when changing the plan from a digital product to a print

Failing 906 Events (WFAMPS-2581)

This issue is a problem where AMPS was configured to receive and process ARIA events 905 and 906. These events do not drive any functionality in AMPS and should not be processed. The events cause additional payment transactions to be created in AMPS, even though the payment was actually failing to collect.

Subscriptions is set to INACTIVE though they should be ACTIVE (WFAMPS-2598)

This issue is a problem where the status of a subscription is changed to INACTIVE when it is taken out of dunning. This issue has now been resolved.

List Subscription should not be returning SPECIAL subscription (WFAMPS-2599)

This issue is a problem where the new API "List Subscription [SubsListSubscription]" returned information on the "SPECIAL" subscription (internal subscription used only by AMPS). This subscription should not be returned in the result set. This issue has now been resolved and only "PRINT", "DIGITAL", "COMBO", and "BUNDLE" product types are returned.

List Subscription to return additional info in response (WFAMPS-2600)

This issue is a problem with "List Subscription [SubsListSubscription]" where the translations for product name and product description was not included in the result set. This has now been solved, and translations are shown for product name and description

Processing credit notes does not correctly determine if original invoice has been paid (WFAMPS-2601)

This issue is related to the STAMPEN ERP processing where processing of credit notes could not determine if the original invoice had been paid or not. This has now been resolved by updating the query retrieving paid invoices.

Unable to raise credit note on invoice with an underpayment write-off (WFAMPS-2602)

This issue is a problem related to the creation of credit notes when cancelling or replacing subscriptions. During cancellation or replace action, the prorated service credit created by ARIA is automatically cancelled and converted into a credit note. However, if the invoice being credited was written off due to an underpayment, the creation of the credit note failed.

This issue has been resolved by removing the underpayment write-off from AMPS, and then issuing the correct credit note. From an AMPS perspective the underpayment is still handled correctly and the invoice can be credited with the credit note.

ERPProcessID not set when handling Refunds (WFAMPS-2608)

This issue is related to the STAMPEN ERP process where when handling refunds, the ERP Process ID was not set in the staging table. This caused refunds to be omitted from the XML sent to the client. This has now been resolved in order to ensure that the process ID is always present.

Replace Starts new delivery at wrong address no (WFAMPS-2610)

This issue is related to "Manage Subscription [SubsManageSubscription]" when using the REPLACE option. When changing to a PRINT or COMBO product, the address applied for distribution was set to the incorrect address.

This has now been resolved so that when replacing a print/combo subscription with another print/combo subscription, AMPS is able to find the correct address based on the effective replace date.

AMPS Migration - invoicing_option value not being honored (WFAMPS-2611)

This issue is a problem with regards to the migration of accounts into AMPS. Due to recent changes in the API handling in workflow, the specification of the invoicing option was not correctly set to indicate that it was present. This has now been resolved and the invoicing option is correctly set.

Standard AMPS Invoice XML to include customer type value defined on the account (WFAMPS-2613)

This issue is a problem where the standard AMPS Financial Document XML did not include the customer type defined on the account. This has been resolved by adding "customerType" to the "CustomerDetails" structure in the XML schema. The following fields was added at the same time:

  • ChannelCode
  • ConsentCode
  • ConsentCodeDate
  • ReservationCode
  • ReservationCodeDate
  • SourceCode

Retrieve Invites API does not return invite for Member Account if MPI is not provided in the input (WFAMPS-2620)

This issue is related to "Retrieve Invites [SubsRetrieveInvites]" where in some cases details on the member accounts was not correctly returned. The invites that were not returned did not have an ARIA identification assigned causing them to be missed in the result set. This has now been resolved.

Different Title Code values required in 'CustomerSystem' and 'Product' in file to DI (WFAMPS-2621)

This issue is a problem where the interface with DI were using the wrong codes for "CustomerSystem" and "Product". The current implementation sets the two attributes to the same value based on the "Distribution Title Code [TitleDistTitleCode]" maintained for the title.

To fix the issue a new parameter has been added to the "AMPS Parameter Definition" functionality. The parameter "Distribution Title Code Setting [DISTTitleCodeSetting]" is used to control the processing with regards to the title code in the distribution file. The parameter can be managed using the "Manage Parameter Configuration [SolmManageParamConfig]" API. The following values can be used for this parameter:

  • "SAME" - when set the "CustomerSystem" and "Product" is set to the same value based on the value found in the "Distribution Title Code [TitleDistTitleCode]" maintained for the title. This is the default value.
  • "SPLIT" - when set the "CustomerSystem" is set to the value of "Additional Info 1 [TitleAddInfo1]" while "Product" is set to the value found in the "Distribution Title Code [TitleDistTitleCode]" with both fields defined on the title itself.

When generating the file for DI, the above setting is used to determine the proper setting of "CustomerSystem" and "Product".

Payment Callback not updating GatewayPaymentID (WFAMPS-2629)

This issue is related to the "Gateway Callback Status [PaymGWCallbackStatus]" API where the gateway payment ID was not always updated correctly. Also issues with the exception handling was found. These issues have now been resolved, making the solution more robust.

Incorrect Header Validation on TK01 records for incoming collection file from BGC (WFAMPS-2630)

This issue is related to the validation of TK01 records received from Bankgirot in Sweden. This issue has now been resolved by updating the record layout for TK01 to the correct version. For some reason the older format was implemented in AMPS.

Subscription member sharing is not set to inactive when main user is inactive (WFAMPS-2633)

This issue is related to cancellation or suspension of master subscriptions with one or more member subscriptions in existence. In some scenarios the member subscriptions were not cancelled or suspended when the master subscription was, allow members to continue to use the service even though the master subscription was closed. This has now been resolved so that member subscriptions are always cancelled if the master subscription is cancelled.

Update dimension for Customer ERP XML (WFAMPS-2635)

This issue is a problem with regards to the dimensions sent to the STAMPEN ERP system. The current solution uses "Dimension #2 through #4", however the customer was expecting to see the information in "Dimension #1 through #3". This issue has now been resolved. Note that the Excel spreadsheet still shows dimension #2 through #4 being used. The change is only in the XML documents.

Migration does not set client_payment_method_id (WFAMPS-2637)

This issue is related to the AMPS Migration process where the client defined payment method identification was not set correctly. This caused issues downstream when working with the billing group and payment methods. The problem is related only to credit cards managed via an AMPS Managed Payment Gateway. This has now been resolved by generating a unique payment method ID as part of the migration process.

When updating account using AriaAccountID error is returned (WFAMPS-2538)

This issue is a problem with the "Manage Account [AcctManageAccount]" API where the audit trail was not being updated correctly due to the ARIA account number not being set as expected. This issue has now been resolved.

Account GDPR Delete account event error due to account being deleted (WFAMPS-2639)

This issue is related to deletes of accounts due to GDPR requests. Unfortunately the AMPS event informing of the deletion was triggered after the account was anonymized in ARIA. When anonymization occurs, the account basically no longer exists and cannot be retrieved with API calls. This has been resolved by moving the event generation to before the delete actually takes place.

ERP not setting correct fee dimensions for Credit Notes (WFAMPS-2641)

This issue is related to setting of dimensions for fees in the customer ERP integration. When handling credit notes the dimensions for fees was not set correctly. This has now been resolved and dimensions for fees in credit notes now follow the same rules as invoices.

Stops are wrongly created on MPI's with replacement (WFAMPS-2700)

This issue is related to ANNIVERSARY subscription replacement, when the subscription was being replaced on anniversary the stop was getting sent on the next earliest publishing date. To fix this issue, a hotfix in SubsManageSubscription has been modified to use next_bill_date for the plan instance being replaced to do the delivery stop.

  • Was this article helpful?