AMPS 3.1 Release

Monitoring Dashboard for Scheduled Jobs and API Performance (WFAMPS-)

In the previous setup for scheduled jobs and API performance monitoring, failures in jobs and API executions often went unnoticed because of a lack of real-time visibility for the processes. This delayed issue detection and resolution has been addressed by introducing a comprehensive Monitoring Dashboard. The dashboard actively tracks the health and performance of scheduled jobs, APIs, and database storage, based on predefined rules and thresholds.

Key features of the monitoring dashboard include:

• Scheduled Jobs Report: Displays the status of all scheduled jobs, including any delays or failures.
• API Statistics Report: Provides detailed insights into API run times and highlights any failed executions.
• Database Storage Report: Monitors storage usage and generates alerts when thresholds are breached.

The dashboard uses a color-coded alert system:

• Red: Immediate action required (critical issue).
• Amber: Warning state (attention needed soon).
• Green: Healthy/OK status.

This proactive monitoring approach ensures that issues are identified and addressed promptly, minimizing downtime and ensuring smoother business operations.

Missing Gateway IDs in Walley Refunds [Hotfix] (JSA-1028) (AP-350) (WFAMPS-5141)

Refund transactions for Walley payments were previously missing critical gateway identifiers — specifically, gatewayAgreementID and gatewayPaymentID were being sent as null in the refund request to the external gateway. The refund request generation process has been updated to correctly populate all relevant gateway IDs, including gatewayAgreementID, gatewayPaymentID, and gatewayExternalID.

Use Case:

• A recurring invoice is created to initiate a payment request.
• Status is changed to “Pending Confirmation”.
• Callback is executed via PaymGWCallbackStatus using the payment request ID.

A refund is then added and approved, successfully passing all gateway IDs to the external service.

ERP is produced incorrectly for invoices and write-offs [Hotfix] (JSA-1123) (WFAMPS-5140)

The placement of the invoice inclusion condition has been corrected, ensuring that invoice selection now respects the specified account context and added validation to ensure write-offs without explicit account numbers are still processed appropriately and not skipped.

Previously, the following issues were affecting the generation of ERP files:

1. Invoice Inclusion Check: The logic that determines whether invoices should be included in the ERP output was incorrectly placed. As a result, all invoices were included by default, regardless of filter settings — impacting troubleshooting and targeted ERP generation.
2. Write-Off Account Validation: Write-off entries without an associated account number were defaulting to 0, leading to the exclusion of valid write-offs from all ERP files.

Replaced get_all_invoice_information_m with Optimized Core API get_invoice_history_m [Hotfix] (WFAMPS-5290)

The use of the legacy get_all_invoice_information_m API was causing significant performance bottlenecks while retrieving invoice data for a given <master_plan_instance_id>. To enhance system performance and reduce load, the get_all_invoice_information_m API has been replaced with the core get_invoice_history_m API. In addition:

• The system now first queries the <DocmInvoiceDetails> table for matching <acctNo> and <PINo> (partial match).
• Only if no results are found, the get_invoice_history_m API is invoked.

This change minimizes unnecessary API calls, significantly improving query response times and overall system efficiency

Rounding Difference in Tax Calculation for Tax-Inclusive Services Issue (WFAMPS-5214)

A rounding discrepancy of 0.01 was identified in tax calculation between UnitPriceVAT and UnitPriceInclVAT during invoice generation for tax-inclusive services. The rounding logic has been adjusted to ensure consistent calculation across tax-inclusive fields to ensures precise tax calculations, enhancing invoice integrity and compliance with tax standards.

Incorrect VAT Display on Service Credit in Invoice XML Issue (WFAMPS-5253)

The AmountVAT on service credits was not correctly displayed in the generated invoice XML, leading to inconsistencies in VAT reporting.The invoice XML logic has been updated to accurately calculate and reflect VAT values on service credits, ensuring correct VAT representation in invoices.

Incorrect Mapping of Payment Reference in FARPAY Processing Issue (WFAMPS-5409)

PaymFarpayPayment_ValidateRecs flow has been modified to map PaymentExternalID to PaymentReference during entry creation in PaymStagingPayments, ensuring accurate payment mapping and processing. This fix enhances payment tracking and reconciliation in FARPAY processing.

Balance Transfer Produces Incomplete Transactions Issue (JSA-1254) (WFAMPS-5327)

The PaymManagePayment_MovePayment flow has been enhanced to correctly validate and return non-zero error codes from the get_invoice_details_m API when failures occur. This fix ensures accurate result codes and proper transaction completion, preventing incomplete balance transfers.

Subscription Modification Fails When numberOfUnits is Null (WFAMPS-5239)

When setting up subscription changes (e.g., future terminations), a null value for <numberOfUnits> caused the update_acct_plan_multi_m API to fail due to input validation errors. This issue prevented automated status changes from being executed. The logic has been updated to skip modifying <numberOfUnits> if the field is null or empty, instead preserving the existing value from the active subscription plan.

Incorrect Data Type for Discount Fields (WFAMPS-5270)

In the LOCALCONNECTION_Query_RetrieveDiscountDetails structure, discount fields (<disc_percentage> and <disc_value>) were incorrectly defined as Int32, which led to loss of decimal precision and inaccurate discount representations. The query has been re-run and saved, to automatically update these fields to Decimal type, ensuring accurate financial calculations during discount evaluations.

Term-Based Campaigns Failing to Create Stop Events (WFAMPS-5441)

When MPIs on term campaigns terminate after the initial period without a previous status change to inactive, no stop is triggered. To resolve the issue, SubsProcessStatusChg was modified to recognize plan instance status code -3 as valid for processing stop events. Now stops are correctly generated for direct Active → Termination transitions.

Credit Memo Validation Enhanced (WFAMPS-5005)

Credit memos were being created even when their value was 0. After applying resolution the system now checks that the credit memo value is greater than 0 before creation, ensuring data integrity. The logic has been updated in DocmGenStatement_GetInvoiceData to correct this issue.

Prevent Dunning Process Configuration with Invalid Email IDs (WFAMPS-5316)

Previously, users were able to configure a dunning process with an invalid email address. The system allowed the configuration to proceed without validating the email field. A validation check has now been implemented to ensure that only syntactically valid email addresses are accepted when configuring a dunning process. This prevents silent misconfigurations and ensures notifications are sent correctly.