CostGuard Version 21.9 Details

A new endpoint in the Balance Service API returns E-Pay account information including the token. This supports looking up E-Pay accounts with the ability to filter the list by the token value. This improves efficiency in finding a customer’s active E-Pay account when the customer has a large number of expired E-Pay accounts. See the Balance Service web API documentation in the IDI Knowledge Center for details.

As part of a larger effort to minimize duplicate Address Validation calls to CoreLogic, starting with 21.9 the system stores more data associated with address validation responses. The Special District Codes that can come back from validation requests are now stored and can be retrieved for review using a new API: /api/validationLog/{validationLogID}/specialDistricts. For details regarding this API refer to the documentation in the IDI Knowledge Center under Developer Support > Web API Documentation > Address Validation Management.

Internal changes for future support of USAePay in Customer Care.

On creating or editing a service in Customer Care, if the billing number was longer than 20 characters, all characters after the first 20 would be truncated. Users would also see a CorrelationID error. Note: Similar behavior occurred in CostGuard client; however users would not see the CorrelationID error.

To correct this, billing number logic was updated to allow numbers up to 30 characters. This is consistent with the maximum value in the database.

In Customer Care, credit checks on prospect accounts did not display account details in the credit search results. The SQL query used by the search page did not have access to prospect data.

The search now uses a different query with access to prospect account data so that account data is displayed in the search results.

CostGuard 21.2 (FR 3156) introduced child feature functionality in Orders. It requires that attributes on products within packages be defined. This created an issue where orders with more than 350 attributes would throw a JSON request too large error.

The logic has been updated to handle up to 250,000 attributes.

Testing protection plan functionality delivered in CostGuard version 21.7 (AR 8795), found that multiple protection plan products could be sold on one order. They were combined into one line item with a Make Sale quantity of 2; however, there should never be quantity > 1 because they are tied to a specific device.

Also, right-clicking the line item and selecting View Protection Plan Information when the quantity is >1 throws an Object Reference Error.

This was resolved by breaking each individual protection plan into an individual line item and the View Protection Plan Information right-click menu option no longer has an object reference error.

An issue with the Mark Expiring Credit Cards date filter where the timezone was ahead of Coordinated Universal Time (UTC + n hours) prevented notifications from being sent.

This has been resolved so that Expiring Credit Card notifications are sent out as expected.

In Address Validation Log Search, the Total Errors count was incorrect when Validation Type = CoreLogic. The returned count included successful validations and matched the Total Attempted Validations.

The Address Validation Management Log summary operation was updated to exclude CoreLogic validations that have success raw result codes (codes starting with R or A or M) when finding the number of errored validations.

In very rare cases an erroneous email is sent from OnlineBill. The email may even be sent to an address not associated to an OnlineBill account. The root cause has not been found.

To assist in troubleshooting, this PR adds detailed logging when OnlineBill sends an email to a user. There are three reasons to send an email:

CPNI information changed

Sending a registration email for a new user

Sending a forgot password email to a user

In these scenarios, the following information will be logged:

Action causing the email to be sent

IDs/keys/etc. used to find the email addresses that need to be notified

Email address(es) used as the recipient and where they are being pulled from (e.g. billing contact of customer associated with CustID X)

Sender of the email

First n characters of the email subject and body

An Internal Server Error was received when configuring triggers in the Workflow application when the workflow action on a trigger was changed. This occurred when both actions had Link Reference Type as a parameter, but the parameter type was different. An example of this was changing the action from Send Email to Create Workflow.

Workflow has been updated to prevent the error.

Clicking the clock icon to set the Requested Due Date on a Workflow instance had no effect. This was an issue anywhere the clock icon can be used to set a date/time parameter.

The Workflow application has been updated so that this no longer occurs and users can set the time using the clock icon.

Calls rated using the LATA/LATA.OCN rating method were being overridden and not rated properly.

The rate method Lata and Lata.OCN were fixed to rate as expected.

The Invoice Detail Export available from Online Bill (AR 8821, CostGuard 21.5) had an incorrect value in the Unit Price field when a charge override had been done.

CostGuard (Billing XML) has been updated to correctly set the Unit Price in the case of a price override.

Changes introduced with AR 8795 (CG 21.7) affected the Browse Tags tab when editing or creating a new billing product in the Product Catalog in CostGuard Client such that:

The Edit button was no longer visible in the lower left corner of the Browse Tags group box.

The Assignment Template drop-down no longer worked like a drop-down list but rather like a text field.

The window was no longer resizable using the middle resize window control in the upper right.

This has been corrected to resolve the above issues.

The CostGuard Client Wireless Usage details was not summing amounts correctly when there were multiple instance numbers for a specific CDR File Record Number.