---
title: "CostGuard Version 20.10 Details"
slug: "costguard-version-20-10-details"
updated: 2026-05-09T18:20:14Z
published: 2026-05-19T16:54:26Z
canonical: "help.idibilling.com/costguard-version-20-10-details"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.idibilling.com/llms.txt
> Use this file to discover all available pages before exploring further.

# CostGuard Version 20.10 Details

#### [CostGuard Version 20.10 Core Bulletin](https://cdn.us.document360.io/3f7f8ade-bcb1-4ec8-af25-0c0ad8601afb/Images/Documentation/CostGuard-20.10-Core-Release-Bulletin(1).pdf?sv=2026-02-06&spr=https&st=2026-11-14T11%3A12%3A03Z&se=2026-11-14T12%3A12%3A03Z&sr=c&sp=r&sig=yn%2FWCakwakORJZt%2Fd1E7xf%2FqnwFWSihUYv3plHq1ZoU%3D)

#### Change Orders

| **Functional Area** | **AR/FR** | **Description** |
| --- | --- | --- |
| Customer Care | FR 3316 | **Removed obsolete Customer Care setting:** **Manage > Settings – E-Pay Transactions – *Payment Invoice Application*** has been removed because the associated functionality is no longer supported. |
| Customer Care | FR 3304 | **Retail History Pageenhancements**: - Removed *Quantity* field from Bill Payments and Deposits (quantity is always **1**) - Added *Service Number* field for displayed details of a retail discount/price adjustment - *QuantityPurchased* and *QuantityReturned* fields are now combined into *Quantity* which will have a negative value if the item is a return |
| Orders | FR 3301 | **Port out requests** – Port out request information has been added to the Orders module to support automatic status updates to service number inventory and reduce the need for manual intervention. Users can now mark the disconnected service as a port out, and specify the carrier to which the service number is being ported to. |
| CostGuard Client Journal/Follow-up | AR 8700 | **Limiting Journal/Follow-up Status selection by Type –** > [!NOTE] > **Note:** > > This functionality applies only when adding/editing Journals/Follow-ups in the Client. Prior to this release, on adding a Journal or Follow-up, you were able to limit Type and Status selection by User Group through configuration in Admin Console Data Management. Now you can also limit Status based on Type. |
| RateBill | AR 8719 | **Update Location Catalog Group Charges Report** – The Location Catalog Group Charges optional report has been updated to include extended tax products in the service breakout section. > [!NOTE] > **Notes**: > > The existing *National Fees* item in the account section has been renamed to *Extended Tax Products*. The SKU description (Regulatory Recovery Fee in this case) will be included in the XML for presentation on the invoice. |
| Workflow | FR 3261 | **Export Workflow Definitions** – Added ability to export the grid contents on the Configure > Definitions page in Workflow. |
| Workflow | FR 3267 | **Multi-select capability on Task and Workflow Search** – This enhancement lets you select up to 10 items in these fields: - Task Search: Status, Group and User fields - Workflow Search: Status and Coordinator fields |
| Payment Gateway Application | FR 3310 | **Sensitive information scrubbed from PGA-related error message in Customer Care** – Previously in Customer Care, if you created a new credit card E-Pay account, and then mistakenly selected ACH in the iframe, an error would occur that displayed sensitive information. The error condition is correct since you can’t select a different payment type in the iframe than you previously selected in Customer Care; however, the error message should not contain sensitive information. This has been resolved by updating the PGA to no longer pass the sensitive information to display in the error message. |

#### Resolved Known Issues

| Functional Area | PR | Description |
| --- | --- | --- |
| Customer Care | 83486 | **Cannot credit back contract penalty inCustomer Care** This was previously unavailable in the click-to-credit function in Customer Care. The ability to credit back a contract penalty is now available in Care. |
| Communications | 83539 | **Fix processing errors that occurred due to missing and unnamed attachments in inboundmessages** Logic in Communications has been updated to properly handle inbound messages with: multiple attachments with the same file name all attachments with no name Also messages can now be deleted even if they have missing attachments. |
| RateBill | 83536 | **Auto-create recurring E-Pay transactions – Transactions created unexpectedly andpartial status on bill periods** This addresses two issues with creating recurring E-Pay transactions for invoice payments. The *Auto Create Recurring E-Pay Transactions* scheduled job delivered in 20.4 was marking a bill period status as *Partial* on the Manage Recurring Transactions page when no transactions were created for the bill period. The logic has been corrected to set the status correctly for a bill period. The status will remain *Not Created* when no transactions are created. Customers with a pending bill cycle change were charged before their current invoice due date. This occurred for both manual and auto-creation of E-Pay transactions (since 20.4). The logic has been updated to only create transactions for customers in the same bill cycle as the period be exported (when the *Total Amount Due* option is selected). Bill cycle change customers will not get charged until they bill and the invoice is due in the new bill period. |
| RateBill | 83560 | **Contract Summary Optional Reports Includes Non-BillableContracts** Contract Summary Optional XML should *not* include non-billing contracts.. Contract Summary Optional XML has been updated to *exclude* non-billing contracts.. |
| Workflow | 83494 | **Assignment setissue** When a task in an assignment set was reassigned to a new group and a new user, and then that task was completed from the *My Tasks* page, the new user was not getting saved due to a race condition. This has been fixed by changing the order of the calls that the Workflow application makes in this case, so that the assignment set is changed first, and then the task is completed. |
| Workflow | 83497 | **Splitter step is being marked complete before all children arecomplete** When a splitter step split and one of the child workflows generated had 0 tasks, the splitter continued on despite the other children not being complete. The workflow event processor was updated to ensure a Splitter Step does not complete prior to completion of all the step’s subworkflows. |
| Workflow | 83500 | **Send Date on inbound communication messagesmissing** Inbound messages with no send date in the message header were displaying the send status as *pending*. With this release, the display logic in Workflow has been updated to set the send date to today when there is no send date in the message header. > [!NOTE] > **Note:** > > This PR was originally included in the 20.8 release for Customer Care, Tickets and Communications. With 20.9, it now covers Workflow as well. |
| Workflow | 83508 | **Incorrect display of task status on *My Tasks* page for cancelledworkflow** On cancelling a workflow, there was an incorrect display of the task status on the My Tasks page in the Workflow application. The Task Search page correctly displayed the task status as *Cancelled*, but the My Tasks page displayed the task status as *In Progress*. > [!NOTE] > **Note**: > > This issue cannot be consistently replicated and is related to the timing of the task going to *In Progress* and the workflow being cancelled. Workflow has been updated to correctly display the task status on the My Tasks page in this scenario. |
| Workflow | 83509 | **Workflow conditional step errorhandling** For no apparent reason, a workflow stopped at a specific step in the Workflow and did not continue. This was caused by an unhandled exception on a Conditional step. Error handling logic was added so when a Conditional step encounters an unhandled exception, the step and the workflow are put into *In Error* status and the error message is added to the workflow activity history. |
| Workflow | 83544 | **Workflow error received: Error Activating SubworkflowStep** An error was received due to a duplicate key for *System.CurrentDateTime* in the extended data collection for a workflow instance. Workflow has been updated to no longer store *System.CurrentDateTime* as extended data. |
| Workflow | 83547 | **Cancelling subworkflow while parent is on hold does not properly notifyparent** When a subworkflow was cancelled while its parent workflow was on hold, the subworkflow status did not propagate to the parent step. When the parent was taken off hold, the workflow would not go beyond the sub-workflow step that was cancelled. Workflow has been updated to correctly propagate a subworkflow cancellation to the parent when the parent is on hold. |
| Workflow | 83554 | **Account-level features can be added as a grouping member to more than onegroup** When splitting by Service Processing Action, users were able to add the Account-level features multiple times to a single group and to more than one group. The Splitter Configuration page has been updated to prevent users from adding account-level features as a grouping member to more than one group. |
| Bulk Data Import | 83507 | **Bulk Data — Customer Import performing slower thanexpected** Customer Import slow performance was due to using a customer lookup API called *Customer Summary* to verify the customer account number. The slow performing API has been replaced with the *Customer Management Account Search* which performs much better. |
| Bulk Data Import | 83534 | **Feature Import: Bulk Dataerror message** When a large number of features were added to the same service within a single file, the following errors were received: *[LoggingNumber=500108] Cannot specify the same ServiceID (##) as another ServiceInformationItem (##).;* *[LoggingNumber=500025] The ServiceInformationItem could not be found using ServiceInformationItemID ‘-1’.* Batching logic in the Feature Import was adjusted to prevent this. |
| Address Validation | 83499 | **Addr Val 2.X – prevent exception when an address validates in CoreLogic but not USPSzip+4** The system was not correctly handling situations where an address was in CoreLogic but did not have USPS validation ZIP+4 information. This caused a failure when trying to use the USPS result. The logic has been corrected to properly handle the above scenario. > [!NOTE] > **Note:** > > This was originally deployed for the 20.8 release, and has been updated for 20.10. |

#### Platform System Deployment Updates:

| **Module** | **Target Deployment Updates** |
| --- | --- |
| Workflow | 10/06/2020 |
| Payment Gateway Application | 10/07/2020 |