CostGuard Version 23.11 Details

Workflow

FR 3551

Data lookup for invoiceinformation

A new InvoiceSummarywithCorporateRollUp data look supports the ability to leverage invoice data in Workflow and Communications templates.

E911 Management

FR 3463

Setting E911Class of Service andType of Service

The Create E911 Batch Detail Workflow Action has been updated to use values for E911ClassOfService and E911TypeOfService as set on the order rather than use defaults as set in the CostGuard Client Product Catalog.

Orders

84516

Unable to add items to an order when using Bill Payment as starting action

The ability to add bill payments to a transaction was introduced in CostGuard version 23.10. This includes setting up a starting block to use Bill Payment as a starting action or simply adding a bill payment during the assembly of any eligible transaction. When using a starting block with Starting Action = Bill Payment, and attempting to add more items to the order, the Add to Cart/Order button was unresponsive.

This was corrected so you can now add items and complete the order.

Note:

This was not an issue when simply adding a bill payment as part of another order, nor was there any problem when just making a bill payment (and not adding more items) using a Bill Payment starting block.

Paymentus Payment Processing

84486

Billing name error when using company name(no first/last name)

On attempting to connect to the Paymentus Customer Portal via SSO in OnlineBill using a company name, there was an error indicating that a customer’s first name and last name is required.

This has been fixed by parsing the company name to fill in the first and last name as required by Paymentus.

Paymentus Payment Processing

84487

Paymentus payments not posting in the CostGuardsystem

A timing issue was causing payments in the Paymentus Agent Dashboard to not display on the Balances tab on the account.

This has been fixed.

Payment Processing

84492

Recurring payments trigger notfiring

The Payment Account Transaction Modified trigger was not being fired for recurring payments created from PCI Payment Gateway Transaction Processing scheduled job.

This has been corrected.

Payment Processing

84500 & 84524

Duplicatepayments

Between the deployment of PR 84143 (version 22.11) and PR 84352 (version 23.8) there was a time when recurring transaction history records were not being written for invoices with $0. This resulted in duplicate payments against the missing invoice records.

This has been resolved by running a database upgrade script when upgrading to 23.8 or later for the first time. This script creates the missing invoice records and prevents duplicate payments charging the customer more than necessary. Note: PR 84524 makes improvements to the original script (PR 84500) to catch all scenarios where duplicate payments were occurring.

Invoice XML

84459

Styling & images are missing when custom fonts setting isdisabled

There was an issue when generating PDFs with the XML to PDF rate bill operation when custom fonts were disabled. The PDF generation was not able to find the css and image files because the file name in the html file was not being replaced with the file path.

This has been fixed.

Treatment

84490 &

84527

Treatment workbook usingout-of-datebalances

The new treatment function for Aging Bucket By Invoice Category was storing customers balance information in memory for performance; however, the balance was not being cleared. When running the workbook again the balance would not update to reflect the latest amount.

This has been corrected so the customer’s current balance will be retrieved on each run of the treatment workbook. However, removing the caching of balance information negatively impacted performance, not allowing the treatment workbook to complete. PR 84527 was added to improve the performance of the Aging Bucket By Invoice Category function to let the treatment workbook run to completion.

E911 Management

84491

Error on creating E911 record with fields greater than 32 characters

Creating an E911 batch record would result in a Correlation ID error when any field (for example, customer name) was longer than 32 characters (maximum length for E911 file format as defined by NENA).

This has been fixed by trimming characters over 32 to adhere to the NENA standard.

OnlineBill

84482

OnlineBill RegistrationIssue

OnlineBill subscribers were having issues with registration. When OnlineBill was calling into Security to generate the registration link it was not checking if any errors were thrown by the Security service and potentially generating bad links.

Additional logging is now provided for the response received from Security to help IDI associates resolve bad link issues for customers.

None for this release