CostGuard Version 21.11 Details

The system now checks the reconnect threshold for account and service reconnect orders in the Orders web module and Order Placement API. If the threshold has not passed, the reconnect will continue. If the threshold has passed, a configured error message is displayed and the reconnect is not allowed. If there is no configured error message, a default message is displayed.

In Security on the Users search page, two new fields – Last Log In: From and Last Log In: To – replace the Last Log In Prior To date filter. This lets you search for user log-in instances within a more precise date range.

The ability to request a new Experian or TransUnion credit report for an existing  customer has been added to the Customer Management Web Service. Refer to the Customer Management Web API documentation in the IDI Knowledge Center.

The document tray (displayed when you click the paper clip icon in Customer Care) did not respect the Add Document and Manage Document permissions.

Now users with the correct permissions can add documents to Document Storage.

The Workflow Create Ticket action has a parameter called Wait for Ticket Close that, when set to Yes, should keep the step In Progress until the associated ticket is closed. This is to ensure the workflow does not progress until the ticket is closed.

There were cases where the ticket closed but the Workflow step & task still showed as In Progress. When the Journal Management Close ticket API was created, the functionality for journals to close a workflow when the associated ticket was closed was not carried forward.

A check was added to Journal management to see if there is a workflow assigned to the ticket and close it if the Workflow is still active when the ticket is closed.

In CostGuard 21.8 PR 83760 corrected an issue where a Service Number was active in both PREPAID and POSTPAID services. This resulted in an issue where the logic that checks if a number is in use due to inventory constraints checked for the existence of any inventory history record, and prevent the reconnect if one was found.

The logic has been corrected to check if the latest inventory history record indicates the number can be used (either currently available or is aging and assigned to the current customer), and in this case allow the reconnect

When a user requests an invoice, the invoice (XML) is created successfully even when there are no invoice details available. This is expected behavior; however, this case was causing an error.

The Service Catalog Group Charge Detail optional XML report was updated to prevent the error from occurring when running the report on a customer without any invoice details.

If two users are looking at the Manage Recurring Transactions window at the same time, both users could kick off the Create All Transactions function. Doing so would create duplicate E-Pay transactions and result in over charging.

This process no longer allows multiple users to kick off the Create All Transactions process on the same bill cycle simultaneously. When one user kicks off the Create All Transactions process, the Balance webservice that is creating the transactions will issue a GUID. Then if other users try to run the process the Balance webservice will check for a GUID and will return a notice that its already in progress.

Audit logging has been updated to capture additional information for voided payment transactions to facilitate troubleshooting instances where a transaction was not sent when one was expected..

With CostGuard version 21.10, AR 8751 to bypass serial number restrictions on retail device sales, added new fields on the Product Catalog Retail Product form to enter Equipment Type and Inventory. However, attempting to modify the Inventory value on an existing a retail product failed to save the Inventory value. Note: This was not an issue when configuring a new retail product.

This was fixed so the system commits this information when modifying a retail product, as it does when creating a new one.

Extra spacing in the SIM Import defined properties caused the import processor to not find the values for those properties when performing a SIM Import in Bulk Data.

The import has been changed to ignore the extra spacing.