CostGuard Version 21.12 Details

Customer Care lets you view and compare invoices on a customer’s account, including Prebill invoices. Prior to this release, Prebill invoices could only be generated by the IDI billing team or by submitting a request from E-Support

This new functionality lets you generate prebill invoices directly from Customer Care. Also, the term Prebill in Customer Care has been updated to Preview.

Before this change, the IDI Web Login form was presented using an Internet Explorer web browser. With this change, the Web Login form can now be presented using a Microsoft Edge-based web browser. To take advantage of this new behavior, Microsoft WebView2 Runtime — a free, separately installed component — must be installed on each machine that will be running IDI Desktop Client. The Web Login form will safely fall back to using Internet Explorer if the WebView2 Runtime is not installed.

The AppleCare Processor was updated to allow nulls for MRC value. If the value is not specified, do not send a value, otherwise send Y (Yes) or N (No).

CostGuard version 20.6 provided a manual account-level Disallow Checks/ACH setting in CostGuard Client and Customer Care to prevent the account from making payments via check and creating/using ACH E-Pay accounts. CostGuard version 21.4 (AR 8828) built on this by providing the ability to automatically set Disallow Checks/ACH when creating a new account based on the account type. This automated functionality is controlled by the Disable ACH/Checks setting available via MANAGE > Settings in Customer Care.

Two issues were found related to these settings:

When Disallow Checks/ACH is set (either manually or automatically) an alert should be added to the account to let users know why they cannot perform check/ACH transactions. This occurs correctly when Disallow Checks/ACH is set manually; however, alerts were not being applied when it was set automatically by Disable ACH/Checks based on account type.

Also, when accounts were created through the Customer Care web module, and Disallow Checks/ACH was set on the account, the setting was not being saved. This occurred whether it was set manually or automatically. As a result the alert was not added to the account, and account was allowed to make ACH payments and create/use ACH E-Pay accounts.

This solution resolves both issues:

The alert is now correctly displayed on accounts where Disallow Checks/ACH is automatically set using Disable ACH/Checks.

When you add an account via Customer Care and Disallow Checks/ACH is set, the account behaves accordingly.

Note: With this solution, you can also automatically turn off Disallow ACH/Checks and the corresponding alert using the Modify Customer trigger. This can be used if the system is configured to not allow ACH/checks when a prepaid account is created, and the account type is subsequently changed to a type where this should not apply.

Several PRs have been deployed to improve performance when loading billing orders on the Order History page in Customer Care. PR 83538 addressed the view for customers on SQL 2017 in CostGuard version 20.9, while PRs 83589 in CostGuard version 21.01 and 83667 in CostGuard version 21.6 addressed the view for customers on SQL 2014.

PR 83824 provides additional optimizations to reduce timeouts for customers on SQL Server Management Studio (SSMS) 2014.

When using workflow splitters to add a parent/child service, if the child service was added first, the add child order resulted in adding a parent service. Subsequently when the parent service order ran, a second parent was added.

To prevent this, the parent service is now marked as processed in the first order so it is skipped in the second one.

Errors were reported (cart remained in a submitted status) when attempting disconnects through the Treatment workbook. This occurred when the system was handling a higher than average amount of processing.

To avoid this Order Placement logic was updated to process these requests in a more efficient manner.

Object reference errors were thrown on services where the MIN was in Reserved or Aging state. The logic was not checking to see if the objInvServiceNumber value was null before checking if the item was already in use.

This was resolved by applying similar logic for MINs in Reserved or Aging state that currently applies for MINs in Not Available state.

When modifying a billing contact in CostGuard Client by double-clicking on the Edit Contact menu, the contact modified trigger was not firing.

This issue has been corrected.

Testing Notes:

In workflow create a contact modified trigger to pick up your edit

In CostGuard Client, go to the Contact tab and double click on the billing contact This opens a generic edit contact screen.

Make a change and save.

Confirm the trigger fires.

An issue was preventing a county level tax marked as primary from being skipped in certain conditions when a city level tax was configured to skip the county tax.

The tax engine has been fixed to skip the county level taxes in this condition.

In some cases, CPNI PIN notifications were sent using the wrong notification template. This could only occur when a CPNI PIN notification was sent as a result of user activity from the Customer Care web application and a custom template was configured for the CPNI PIN notification. Note that CPNI PIN notifications sent as a result of user activity from CostGuard client are correctly sent using the custom template if a custom template exists.

This issue occurred when the custom CPNI PIN notification template was saved in the database with mixed case in the key name (CPNI.Pin versus CPNI.PIN)

Customer Care has been updated to correctly use a custom template for CPNI PIN notifications.

The formula for Contract Asset Value coded in AR8760 (released in CostGuard 21.05) was not correct and was miscalculating these values.

The formula was updated as follows:

Contract Asset Value = (C*D*M) / (C*M +S) where
M = MRC of plan
S = Total Stand Alone Price of Qualifying Retail Items
D = Total of Qualifying Discounts
C = Contract Duration