CostGuard Version 23.4 Resolved Known Issues

Service addresses created and edited in Customer Care previously did not have address validation performed on them.

Customer Care/APIs have been updated to perform address validation when creating and editing a service address. This results in a tax jurisdiction being set for service addresses that pass address validation.

Note: Service Addresses will only validate using USPS (will not use CoreLogic if enabled) This is consistent with CostGuard Client Service Address Validation. TaxJurisdiction Info/TaxCounty will also be set on the Service Address if “Tax Using Service Addresses” is enabled.

A popup will display if there are any validation errors.

The Additional Information section on the Edit Customer Information page lets you set custom attributes as defined in Admin Console. This section supports setting attribute values via extended data as set up in the Workflow web module. Attributes are matched to their extended data item by assigning both items identical keys. There was an issue where, if an attribute and extended data item had identical keys differing only by case, the web service call would not match the items and consequently not set the attribute value as intended.

The web service call has been updated to ignore case sensitivity when matching extended data items with attributes so attribute values are set as intended.

This issue was found when following these steps on customer account:

• In Account Details, click Edit in Tax Information > Tax Jurisdictions.
• Check Override and perform a Tax State search.
• In Tax Jurisdictions dialog, click OK without doing anything in the dialog.
• At that point the search field is not functional.

To prevent this condition, Save on the Tax Jurisdiction dialog is disabled until changes are made. If you do nothing, your only option is to cancel.

The ability to manage directory listings in Customer Care was introduced in CostGuard version 23.3; however, this functionality was toggled off by default (control not accessible to CostGuard Users).

This functionality is now immediately available on installation.

An unnecessary check was causing the following error to occur rarely when selling a retail installment plan in CostGuard Client: Unable to generate and save installment agreement. Installment Agreement Information missing. The error was displayed even when the installment agreement was saved and the device activated successfully.

This check has been removed so the error only occurs when an agreement actually does not save.

Provisioning Priority supported in the Order Placement web service was not previously implemented in Billing System Update.

Billing System Update now copies Provisioning Priority from the web order into the billing order as other order-level fields are copied in.

When selling a retail or billing protection plan via make sale, on finishing the order, the Cancel Reason Code on the product was being set to None. Cancel Reason Code should only be set when the protection plan is canceled and not at the time of sale. This resulted in an issue with the Cancel Reason Code drop-down menu in Care. This menu has a blank entry for setting the value to Null. Setting the value to None at time of sale put a 2nd blank entry in the menu.

This was corrected by setting the Cancel Reason Code to NULL at time of sale rather than None.

Services with start dates before 1970-01-01 were skipped and not billed.

The Billing operation was updated to not skip billing charges associated to services with start dates less than 1970-01-01.

AR 8418 in CostGuard version 20.5 provided the ability to take action on declined E-Pay payments to help ensure customers do not get hotlined due to a temporary payment issue. A performance issue with the query to find declined transactions was causing the process to timeout and error when the query took more than two minutes.

The query has been updated to improve performance.

A previous PR addressed an issue where recurring E-Pay transactions would stick in Partial status. However, the intial solution had bugs that caused it to return duplicates rather than all requested records.

Related queries were fixed to return only requested records and not return any duplicates.

Device bulk import was introduced by AR 8885 in CostGuard Version 22.3. This import had performance issues where the imports would take an exceedingly long time to run. This was caused by the luhn digit not being identified and removed accordingly early in the import process.

Updates have been made to lookup from a file for a serial number or alternate serial number to find the 14 digit value first. If there is no return on a 14 digit value, the 15 digit value will be used.