AMPS 2.23 Release

Improving reporting on invoice periods (WFAMPS-3590)

Billing clarity has been enhanced to eliminate the need for manual corrections of subscription periods on invoices generated through AMPS that were being displayed inaccurately. Previously, the start and end periods on order invoices for campaigns, final invoices, and catch-up billing were set to the invoice date, leading to reporting inaccuracies. With this update, the correct start and end dates of the subscription period are now added to the order comments for campaign, final, and catch-up invoices. This ensures that downstream systems and processes can accurately reflect subscription periods.

Invoices from AMPS now indicate the accurate subscription period dates in the Line Comments and Order Comments in the format<TYPE>|<STARTDATE>|<ENDDATE>. 

For invoices generated before this enhancement, the previous functionality remains, displaying the invoice date as both the start and end date for the subscription period. Future invoices, however, will correctly include the updated subscription periods in the Line Comments and Order Comments.

Added new parameter in DistDimpasGETDELAYInfo API’s response (WFAMPS-4794)

A new parameter has been introduced in the response of the DistDimpasGETDELAYInfo API to accommodate updated attribute changes from the DIMAPS API. The added parameter provides more detailed delay information, specifically the <delEndDate> which represents the end date of a delay period.

You will now receive an updated response that includes the <delEndDate> when using the DistDimpasGETDELAYInfo API for accounts with combo or print services providing more accurate tracking and manipulation of delay periods within the AMPS system. The new data will also be available for CIM to display, improving the transparency and usability of delay information.

Enhanced Error Handling for Same-Day Cancellation and STOP Processing in Distribution (WFAMPS-4740)

A use case in the Distribution process related to queued (future) cancellations has been updated to properly detect and report an error if a cancellation is removed on the same day that STOP information is sent to the distribution system. This prevents the erroneous processing of STOP requests after a cancellation has been removed.

Previously, if a queued cancellation was removed on the same day that the STOP information was sent to the distribution system, the STOP request would still be processed, leading to potential errors. AMPS would attempt to remove all future changes related to the cancellation, but if the STOP had already been processed, the system would report an error indicating that the subscription could not be canceled.

Enhanced Error Handling in Payment Files Processing (WFAMPS-3987)

A sub flow within Payments Processing has been updated to properly handle errors that occur during processing. You can now expect reliable error reporting and handling within the Payment files processing (BANKGIRO, FARPAY). If an error occurs, it will now trigger the appropriate error-handling mechanisms, allowing for quicker diagnosis and resolution of the problem. Previously, if an error occurred in this flow, it was not correctly captured or reported, leading to issues in downstream processes. Now, any errors encountered in the flow will be properly handled by the main flow, ensuring that issues are identified and managed promptly.

Impact of Enhanced Error Handling on fileStatus is addressed (WFAMPS-4847)

In the Payment Files processing flow, PaymManageAutogiroPayBankgirot, the valid <fileStatus> values are STARTED, FAILED, and ENDED. However, the current implementation has added and also passed SUCCESS and WARNING statuses, which led to errors due to additional error handling introduced in a previous update (WFAMPS-3987: Enhanced Error Handling in Payment Files Processing).

These errors have been resolved by mapping SUCCESS and WARNING statuses to the ENDED <fileStatus> value, ensuring alignment with the expected status values and preventing processing errors.

Correction of VAT Calculation for Accurate Refund Processing (WFAMPS-4618)

During full reverse refunds you will now see correct refund amounts including the appropriate VAT calculation, eliminating discrepancies in refund processing. Previously, the refund amount was incorrectly calculated during  REVERSE REFUND and the reversalLevel was FULL. Additionaly, the VAT amount was not properly included in the total refund, leading to inaccurate refund amounts. The updated functionality ensures that the VAT is correctly added to the refund amount in the REVERSE REFUND and the reversalLevel as FULL transactions to provide accurate totals.

Display of Inactive Plans in ProdDetails Table (WFAMPS-4584)

You will now see a complete and accurate list of both active and inactive plans in the ProdDetails table following any changes or deletions, ensuring better visibility and management of product plans. The reliability of the cache management process has been improved ensuring that all plans, regardless of status, are properly indexed and displayed. This update also improves the overall data integrity in the product management interface.

Previously, inactive plans were not displayed in the ProdDetails table after all plans were manually deleted and the product cache was refreshed; only active plans were shown correctly. Now, both active and inactive plans will be accurately displayed with their correct statuses after any manual deletion and subsequent cache refresh.

Enhanced Invoice Update Process and Asynchronous Event Handling (WFAMPS-4804)

The invoice update process has been improved by ensuring that, regardless of the credit type, the process does not result in an error if invoices are not found for updating. In the event of an exception, the process will now log the error and exit, avoiding disruptions to the workflow reducing the risk of workflow interruptions. The system also now triggers AMPS events in asynchronous mode enhancing overall performance with faster processing times and improved system responsiveness.

Accurate Refund Status Updates (WFAMPS-4735)

An issue resulting in refund statuses being incorrectly displayed has been corrected to display the refund as successfully processed and received, resolving the previous discrepancy where "POSTED" statuses were incorrectly shown as "ERROR" even though the refund was confirmed as received by the account holder.

Additional validation checks have been implemented to ensure refund statuses are accurately updated when you confirm receipt, ensuring reliable status reporting.

Complaints With Auto Compensation Were Not Getting Credited (WFAMPS-4851)

You can now expect accurate application of auto-compensation when raising complaints. If an object has null values, the system will correctly recognize it as null, apply compensation and credit accordingly.

Previously, in the complaint process where compensation was not being applied/credited, despite auto-compensation being enabled for the complaint code. The issue occurred in the workflow (WF) where it failed to correctly determine if an object was null despite all the fields within the object being set to null. To resolve this, the approach has been modified to use the “Is Empty” validation which checks for both null and empty values on the titleCode field, ensuring that if the value is null, the entire object is treated as null.

Incorrect Invoice Periods in Credit and Reissue Functionality (WFAMPS-4784)

The Credit and Reissue functionality issue regarding incorrect invoice periods has been corrected. Previously, after performing a Credit and Reissue operation, newly generated invoices would exhibit overlapping or incorrect periods compared to the original invoices. The issue was addressed to ensure that new invoices created post Credit and Reissue contain accurate invoice period dates and align correctly with the intended billing periods.

Incorrect Calculation in Discount on Subscription using Units (WFAMPS-4848)

The OIOUBL calculation logic has been fixed to ensure that the correct discount per unit is applied. Previously, in OIOUBL documents the discount on subscription items using units resulted in an incorrect calculation of the discount per unit on certain invoices. Moving forward, unit discounts will be accurately reflected in OIOUBL documents, consistent with the expected discount percentage.

TaxPercentage Value in AMPS xml (WFAMPS-4637)

For credit memos, the TaxPercentage is now correctly formatted to match the format used in invoices. When processing invoices with service credits applied on line items, the TaxPercentage values within the AMPS XML have been corrected to ensure consistency across different document types. 

VAT Amount Shown Incorrectly in OIOUBL and AMPS Financial Document (WFAMPS-4724)

The calculation logic for VAT amounts has been corrected to ensure accuracy and to remedy a previous issue resulting in the incorrect calculation and display of the VAT amount in both the OIOUBL and AMPS financial documents. This ensures that all future invoices and financial documents will reflect the correct VAT amount, preventing any discrepancies in financial reporting and compliance with tax regulations.

Review AMPS Events Creation Process (WFAMPS-4803)

The current process for AMPS event creation operates in a synchronous mode, which can lead to performance bottlenecks and delays in processing, especially under high load conditions. To improve system performance and scalability, All AMPS event creation processes have been updated to run asynchronously. This change allows the system to queue and process events independently, significantly improving overall performance and responsiveness.

Unmatched Payment in Staging Payments as Failed Payment (WFAMPS-4775)

In FarPay processing, all unmatched payments now display in Staging Payments as "unmatched payments", preventing them from being incorrectly classified as "failed payments". Previously, as a result of an inconsistency in unmatched payments processing via FarPay, some payments ended up in Staging Payments as "failed payments", while others were processed successfully.

Remove Usage of Truthtables in AcctCreateAccount (WFAMPS-4594)

When creating an account, the <MapLocaleCode> and <MapPaymentTerm> are no longer required in the AcctCreateAccount process. Validation is now performed against the configuration data stored and the below changes have been made. These changes ensure the validation process is aligned with the new configuration data structures and that the system accurately reflects these updates.
 

Balance Transfer Not Working Correctly (WFAMPS-4387)

To address incorrect payment allocations caused by typos during balance transfers, leading to inaccurate balances and invoices, the following changes were made to the PaymManagePayment process:

Unapplying Payment from Source Account:

• Before recording an outgoing payment, the get_payment_application_dtls_m API is used to identify all invoice lines where the payment was allocated.
• If no invoice lines are found (Error 1008), no further action is needed.
• An <unapply_list> array is prepared to deallocate the payment from these invoices.

Invoice Status Update:

• After deallocating the payment, the Invoice Details table is updated to indicate that the invoice is no longer paid.
• The PaymManagePayment API ensures the system accurately reflects the updated payment status.

Handling on Destination Account:

• After recording the payment on the destination account, the PaymManagePayment API verifies that the payment is correctly allocated.

Extend Request Manager Data Retention Period (WFAMPS-4810)

Development work has been done to increase the Request Manager data retention period up to to 14 days while eliminating performance related issues.

CIM/ACM Update the list Complaints sort order, in ascending order, on the Complaints Tab UI (WFAMPS-4819)

You can now see the complaint codes in ascending order within the complaint codes tab of the Configuration Manager.

CIM/ACM CR B2B Sales Tracking (WFAMPS-4814)

You are now able to track the B2B sales. Sales representative email will be provided at the time of subscription creation. There are updates within the Role tab of User Management and rights to read, update, and create can be defined accordingly.

CIM/ACM Adding new address with an AFLO (WFAMPS-4817)

The 'Free Text' check box is now removed once the AFLO code is selected as X0 i.e. 10, 20 while adding a new address with AFLO code.

CIM/ACM Change of delay-view when creating a complaint (WFAMPS-4839)

A change has been made in the delay view when creating a complaint. The new fields are all a part of the data from the DelayLookUp (in same order) “Udkomstdato”, “AbonnementsId”, “Årsagskode”, “Information”, “Leveringsdato”, “Leveringstid”, “Leveres”, “Usikker lev.”, “Annulleret”. to view parameter <DelEndDate>. 

CIM/ACM CIM Invoice number in overview for Credit memos (WFAMPS-4840)

You are now able to successfully see the invoice numbers in the credit memo widget on the Invoice and Payment tab.

CIM/ACM Update the search page field order to make more usable for customer service (WFAMPS-4831)

The search page has been updated to facilitate quicker and easier use when entering the search criteria.

CIM/ACM: RM_014 Change the order/view of address-fields in the result when searching for an order (WFAMPS-4835)

The order and view of address fields in the result when searching for an order has been updated.

CIM/ACM:  RM_012 Update the order in which the address fields are displayed (WFAMPS-4834)

The order of the address fields has been changed. This includes the search results page, overview page (where addresses appear), address details tab, update delivery address, and the subscription view when selecting existing addresses.

CIM/ACM: RM_013 On the update address UI, Update the order in which the address fields are displayed and optimize what is displayed for addresses used previously (WFAMPS-4837)

New parameters have been added in the Update Address UI with the address fields displayed in an updated order. The new parameters include: <Dist_Addr_No>, <Dist_co_addr> (additional name), <Dist_Delivery_days>, and the latest from and to date. Additionally, the headline “Yderligere information” has been changed to “Label”. 

CIM/ACM:  RM_016 To date shouldn’t appear in case of split-address (WFAMPS-4838)

When creating a split address there is no longer a required default 'to date'.

CIM/ACM: RM_008 Update the list Complaints fields displayed on the Complaints Tab UI (WFAMPS-4815)

New columns have been added in the list of complaints fields on Complaint tab within the UI. The new columns are Comp Complaint Date, Comp Code, Comp Complaint Headline, Comp Compensation Amount, Comp Complaint Status, Comp Complaint Update Date. Additionally, some existing columns have been removed from the Complaint tab.

BEM 072 Replace the host we are currently using to communicate with User Service (WFAMPS-4854)

The host currently being used to communicate with User Service has been replaced.

CIM/ACM CR: BEM SSO (WFAMPS-4841)

One Login SAML implementation has been carried to the front-end and the back-end of the UI. Key Areas include one login Tile Integration, SSO Access, Access via direct URL, one login authentication, Welcome Email configuration, access control, addition of CIM users, and Integration with AD username.

SSP: Development of New Retention flow (WFAMPS-4823)

The new retention offer process has been implemented. Key areas include sending feedback and details to the slack channel, definition of multi level cancellation reason codes, sending out technical issues feedback to the customer service.

CIM: JSA-994 | (AP-53) : CIM to use AccountsearchAccountV2 instead of API AcctSearchAccount-Object Query (WFAMPS-4798)

This enhancement has been implemented to ensure you get a better search experience. Improved performance can be achieved by calling the new API AccountsearchAccountV2. This will resolve the search inconsistences.

CIM/ACM DEV: (AP-253): (JSA-965) Walley - New Process to support external iframe for entry of third party (i.e. Walley) payment Information (WFAMPS-4745)

When you click on Change Method in SSP, instead of opening the Adyn drop in component you will be redirected to the new URL. In SSP selected Subscription ID will be provided in the URL. Once the user is re-directed via URL the rest of the process flow is managed by the business.

SBF CIM/ACM: The search restriction on page load as one (WFAMPS-4795)

Date filters were introduced in the orders tab of operations management. There is now no search available without the application of filters. Now you can select From and To Date. Please note that the time frame for the From and To Date is restricted to one week.

New API adresses Evry (Dev Ops 9529) (AP-251) (JSA-972)

The URL provided has been changed. This change occurred in SSP and CIM.

Change Payment Method changes in SSP (WFAMPS-4793)

A change was made in the Change Method URL. The URL now passes User Subscription ID instead of Account ID to make up the Change Payment Method URL. The corrected URL format is as follows:

https://[title]/mina-sidor/prenumation/uppdatera?subsId=[subscriptionId]

AW-18 - Add ariaInvoiceNo to the resultInfo response for OrderManageOrder (WFAMPS-4781)

The Aria Invoice number has been added to the resulting Info response of Manage Order.

SSO adding backend updates (JSA-1003) (WFAMPS-4830)

Aria AMPS has integrated Active Directory (AD) into the CIM and TM applications independently of the JFM network.

This integration will function seamlessly even if you are not connected to the JFM network or Wi-Fi.

PE Task: Ensure correct Zephr solution (JSA-908)

This change occurred in SSP and Websales.

The initial enhancement request was to do the changes on the Site ID to ensure that as part of the new autologin feature we call the Zephr public API directly via JFM each title APIs.

PE: Campaigns and quarterly payments for regular subscriptions displayed in TM application (WFAMPS-4791)

The Campaign option and Quarterly Payment option for regular Subscriptions is now shown in the TM application.

CR: Ensure correct Zephr solution (WFAMPS-4816)

Changes have been made to support auto-login solution. Feedback sessions have been planned with for the end of August.

CIM/ACM: JSA-973 'contact name' does not default to the account contact when adding subscription (WFAMPS-4765)

When updating address and changing to a new one, existing name will be there as default for [Contact Name]. This field will be editable, but with the existing name already filled in.

JSA-969 Problems with address lookup in CIM depending on which Publication is first in the Subscription field (WFAMPS-4746)

The address look-up in the Address detail tab will work and show results accordingly depending on the publication selected in the subscription field. 

SBF CIM/ACM: Duplicated credit memos (WFAMPS-4808)

Duplicate credit memos that previously happened when double clicking during the cancellation and update subscription process has been addressed.

CIM/ACM RM_010 Prefixed blank character in the free text field (WFAMPS-4818)

The issue of one pre-existing character in the free text field while adding new address has been resolved. Now no prefixed blank character appears on text field in Add new address on codes with AFLO code of xO.

CIM/ACM: (RM_011): Correct the search page field "Navne Street” and "House Number” (WFAMPS-4832)

A correction was made in the search page field labels Navne Street and House number.

CIM/ACM: Change of word, that is translated to Danish - fine tuning in general (WFAMPS-4836)

A correction was made in the on-search fields and in Address overview the field label was corrected to Leveringsdage.

SBF CIM/ACM: (AP-255) Duplicated credit memos (CAS-227158-K1B8Y6) (WFAMPS-4800)

Unintended duplicate credit memos that happened upon double clicking during the cancellation and update subscription process has been addressed.

Not able to remove the temporary hold and clicking the pencil icon results in white screen (JSA-993) (WFAMPS-4797)

You are now able to successfully update temporary holds. Furthermore, the issue of the screen blanking white while clicking the trash icon has been fixed.

CIM/ACM: (AP-239) Make it possible to remove social security number in CIM (JSA-951) (WFAMPS-4792)

You can now remove a social security number from CIM. Previously, an error occurred while saving after removing the social security number. This has also been fixed.

SBF CIM/ACM: 1/1 Comments not pulling through on Prod for manual payments in ACM (WFAMPS-4782)

Comments with regards to the manual payments in ACM will be visible in the Transactions webpart in CIM.

(AP-258) Refunds get status "Failed", Refund status reason 555 (CAS-227159-L1G1G1) (JSA-979)

A change was reverted back from UAT and Dev On the CIM side. The issue was on the AMPS side. The Refund Failures were coming because the API that was used was “ issue_account_to_refund “

The API has been reverted to “record_outgoing_payment_m” under WFAMPS-4593: JSA-921 | Stampen (AP-212) :AMPS Refund Issue - Customers Refunded by Bank Transfer AND Electronic Refund in Core (dev Ops 9415)Done (This is for Bank and Cheque option).

Further more a report logs are run “paymrefundtrans table” from 27 June onwards till July 4 to check for the refund failure, & there was no failure of refund after WFAMPS-4593: JSA-921 | Stampen (AP-212) :AMPS Refund Issue - Customers Refunded by Bank Transfer AND Electronic Refund in Core (dev Ops 9415)Done deployment to prod under AMPSv2.22.

Websales/campaigns: check out flow is not as expected (WFAMPS-4806)

The websales and campaign flows issues are resolved in the checkout flow.

(Arias-910) P2: Campaign sites failing, checkout not possible for JydskeVestkysten (WFAMPS-4855)

With the fix the access to check out flow was made possible for jydskeVestkysten.

SBF WS/SSP: Wrong URL on Websales for terms and conditions (WFAMPS-4769)

A front-end change allows you to now redirected to the correct Terms and conditions page.

SBF CIM/ ACM: Duplicated credit memos (WFAMPS-4809)

Duplicate credit memos that occurred when double clicking during the cancellation and update subscription process has been addressed.

CIM/ACM: Dimaps calls are not logging in request manager for CIM/WS in request type of Dimaps (WFAMPS-4779)

You will be able to see the Dimaps logs in the request manager.