CostGuard Version 21.7 Details

The Invoice page has a new service summary view that displays invoice sub-totals by service including recurring charges, non-recurring charges, usage, and discounts. It also provides tax sub-totals, when available. This new view is available for all invoices.

This solution enables IDI platform users to log in to  Client and Admin Console with the IDI web security login used for web applications such as Customer Care and Workflow. This provides a consistent login experience and lets users take advantage of features such as OAuth login and password reset self-care. Authorized users can turn this functionality on and off.

This is part of a larger effort that spans multiple releases and impacts several functional areas of the system. The enhancements provided in this release include:

• Adding custom options to the Actions menu on the Protection Plan Detail view in Customer Care. This is similar to a Switch Query, You can configure custom actions to query a 3rd party protection plan provider (e.g. Apple) to verify information. Custom actions are configured via the Protection Plan Profile Detail screen (Product Catalog Web App > Manage > Protection Plan Profiles). This can be done by IDI or IDI platform users.
• Selling protection plans through Orders web module. This includes the ability to configure and verify Protection Plans during a sale.
• Selling or disconnecting a protection plan via POS in the Client. This includes the ability to configure and verify Protection Plans during a sale.
• Delaying enrollment until fulfillment.

Web services were preventing users from applying credits to inactive E-Pay accounts.

The Customer and Balance web services were enhanced to allow updates on refund transactions for inactive (end date expired) E-Pay accounts.

Note: PR 83607 (CostGuard version 21.1) enhanced the Customer and Balance web services with respect to creating E-Pay transactions. PR 83701 extends this enhancement to modifying E-Pay transactions (e.g. applying a credit).

Running E-Pay could result in a large number of errors for certain flows that could lead to setting the RootEpayTransactionID and/or the RetryIndicator to NULL. This NULL value resulted in the error message that was reported.

Logic has been added to handle the NULL scenarios to prevent the error.

The PCI Payment Gateway Processing scheduled job was encountering an error when attempting to credit an E-Pay transaction with an OriginalNetworkTransactionID set but the E-Pay account being used did not have an OriginalNetworkTransactionID.

This was fixed by adding a Null reference check.

Warnings were received during Billing for expired tax jurisdictions. The errors were all for features that had been disconnected in the past and were not relevant to the current billing run. Billing has been updated so that validation is not done for historical features that are no longer billing.

When running Billing, there was an issue validating XML when enabling the setting Separate Taxes into Mandatory/Non-Mandatory Sections. The issue was due to a missing tag for the setting, and was only experienced when this setting was enabled. The CostGuard ifx.dtd file has been updated to define the missing element for this setting.

The Address Validation Management web service documentation has been updated to change fipsCode to taxFips in the response to the Validate Address Post operation. Additionally, the rawResultCode has been documented. There was no code change related to this. The issue was simply due to a documentation bug.

An Object reference error was occurring when provisioning to Metaswitch in some scenarios. This was due to not properly handling when a response from MetaSwitch lacked ExtendedSubResults.

A NULL check was added to the ExtendedSubResults field so that when responses do not contain the results, an error will not occur.

In Workflow Provisioning, the List drop downs were limiting the avalable values to the

first page of 20 values. Users could use the type ahead functionality to locate the desired

value; however, when trying to scroll through the list values, only the first 20 were

displayed.

This has been corrected so that users can scroll through entire sets of values in the list.

Adding an element to a user-defined list, removing the item by clicking X, and then saving resulted in an Internal Server Error.

The Manage Lists page has been updated so that adding a new item to the list and then removing it will not cause the Internal Server error upon saving.

Duplicate adjustments batch files were uploaded in error and attempting to void the duplicate records resulted in an error. This occurred as a result of loading batchfiles and creating multiple BCMRequest entries with a BCMRequestTypeId = 1. Void logic for payments and adjustments deletes the duplicated records in that batch by looking up those records based on the BatchFileID. When there is more than one BCMRequest for the same BatchFileID the query to identify those records presented an error. The logic for creating the BCMRequest was updated to only happen when there are no BCMRequest created for the current file.

Note: While this PR will fix this functionality going forward, contact IDI Support if you are receiving critical error messages when attempting to void batch files.