CostGuard Version 21.1 Resolved Known Issues

Logic for private line tax allocation functionality in Customer Care did not match CostGuard Client logic for managing private line taxes. When tax exempt flags were set on a private line tax allocation (Federal, State, County, City, Regional), only the main tax was marked as exempt. The USF and Surcharge flags should also have been set for the type of tax(es) selected.

The tax exempt flags have been updated to appropriately set all flags in the category, not just main tax one.

PR 83538 (CostGuard version 20.9) addressed poor performance when loading billing orders on the Order History page in Customer Care; however, the improvements only applied for systems on versions of SQL 2017 or newer.

With PR 83589 improved performance is available for systems with SQL 2014 as well.

Communications in Tickets and Customer Care sometimes listed messages out of order by date. This occurred when outgoing messages were stuck in a Pending state.

Now when Send Date is null, message sorting uses the Create Date instead.

When revalidating a contact (primary or not) if the address was unchanged the AddressValidationTaxJurisdictionLink entry was being removed.

The web service has been updated to set the Tax Jurisdiction information when there is a new validation record – even if the address is unchanged.

A ModifyFeature request in the Customer Service API is considered invalid if the specific type of FeatureDetail is not specified. Prior to this release, the API check for missing feature subtype occurred late in the process and resulted in an object reference error.

The API has been updated to perform this check earlier in the process so it stops before throwing the error. The API documentation has been updated accordingly.

For customers using Direct Invoicing functionality, the Order Checkout Overview was incorrectly treating tax buckets with identical amounts as the same value. For example, if there were multiple tax lines with the amount $4.88, all would be listed on the Tax & Totals tab but only one was included in the total. This caused the total amount to look less then the actual amount due. The total was correctly calculated on the invoice PDF.

This was fixed such that when gathering total amounts (subtotals and tax amounts), the calculation now includes all like tax amounts in the total.

A customer was able to complete the first step of the registration process, but was unable to proceed with the remaining steps. The customer received an error that said One or more required fields are not filled in correctly. Please check your inputs and try again. This happened because the confirm account number page (Step 2) of the registration was expecting only numeric account numbers. In this instance the account number was alphanumeric and triggered the error.

The registration process has been updated to allow alphanumeric account numbers.

When AR 8662 was released in CostGuard 20.11, the InvoiceAddressTaxJurisdictionDetail table was not included in replicated data.

A primary key was added to the InvoiceAddressTaxJurisdictionDetail table in the core database so that it will be included in replicated data.

Updated RateBill Maintenance Operation seed data in Core.RequestOperation table that could be incorrect based on the customer’s upgrade path.

When an E-Pay transaction is refunded and the system tries to update the core database through the Customer web service, the logic prevented creation of a transaction if the E-Pay account was inactive. This presented a problem for refunds.

This PR updates both the Customer and Balance web services to allow creation of refund transactions on inactive E-Pay accounts.

The Circuit Charge Detail optional invoice XML omitted services that had charges on the current invoice when the service was disconnected prior to the bill period.

The XML has been updated to include any service with charges on the invoice, regardless of the end date of the service.