CostGuard Version 23.10 Core Bulletin
Change Orders
Functional Area | AR/FR | Description |
|---|---|---|
Orders – Web Sales | FR 3412 | Web Sales – Bill payments, returns &voids Web Sales is an ongoing development effort to provide a complete web-based solution for managing the full scope of front office transactions including billing orders, tendered retail sales and direct invoice transactions. Functional milestones will be deployed over a series of IDI platform software releases where each subsequent release builds on the prior one. This release provides enhancements for:
For details regarding the overall objectives and planned future deliverables for web sales, refer to the IDI Knowledge Center > IDI Updates > Product Roadmap presentation. |
Customer Care | FR 3516 | Incentivizing PaperlessBilling Providers are moving away from paper billing to leverage the efficiency and cost benefit of electronic invoice delivery. Processing paper invoices is costly, uses valuable staff time and is prone to human error. Electronic delivery is faster, more efficient, and providers get paid sooner. Prior to this release, the CostGuard system had the capability to track whether an account should get a paper bill. This feature adds the ability to incentivize subscribers by providing a discount when paperless billing is chosen (or apply a charge when subscribers opt out). |
Payment Processing – Paymentus | FR 3539 | Enhancements for AdvancePay Automatic Renewal AdvancePay in Paymentus Integration was originally released with CostGuard version 23.9. Version 23.10 provides the ability to filter the list of available services when adding automatic renewal services to a wallet in Customer Care. |
E911 Management – Web Orders & CostGuard Client | FR 3463 | Enhancements for E911management Support for E911 management in web modules was originally provided in CostGuard version 23.7, and some enhancements were provided with CostGuard version 23.8. Version 23.10 provides the following enhancements:
|
Orders | AR 9248 | Ability to edit service name in weborders Customer Care and CostGuard Client orders provide the ability to enter a name or other information on a service; however, that capability did not exist when adding or editing a service in the Orders web module. This release adds a field to enter such information on the transaction details screen when adding or editing a service in web orders. |
CostGuard Database | AR 9155 | Last Modified Date enhancements Improvements to storing last modified date in CostGuard database tables make it easier for data engineers to analyze and troubleshoot issues where problems may occur during data transmission. |
Workflow | AR 9263 | Access to service level attributes in Workflow data lookups This adds a ServiceInformationItemID to the BillingOrderDetail OData in the Order Placement Web Service, and creates four new Data Lookups: BillingOrderDetailByServiceInformationItem, CartItemExtendedInformationItem, OrderExtendedInformationItem, and ServiceInformationItemExtendedInformationItem. These enhancements let you build a workflow that passes extended information, for example, values on a service based on the ServiceInformationItemID provided. See the applicable API documentation in the IDI Knowledge Center for details. |
Database Services | FR 3439 | Prevent overflow of general ledger journal entry tableIDs Changes were made to prevent GL Journal Entry tables from overflowing their identity columns, which could potentially cause an outage for a customer. |
Resolved Known Issues
Functional Area | PR | Description |
|---|---|---|
Payment Processing – Paymentus | 84462 | No access to payment information in Paymentus CustomerPortal When administrators attempted to impersonate an OnlineBill user to access their payment information the Paymentus Customer Portal I-frame would throw an error. This has been corrected. |
Payment Processing – Paymentus | 84470 | Paymentus notifications not received in CostGuardsystem When a payment is created in Paymentus, the resulting notification to IDI was not firing the Payment Created trigger. This has been corrected. |
Customer Care | 84449 | Allocation override on new payment not loadinginvoices In some instances, when trying to allocate a payment across multiple invoices and/or invoice categories in Customer Care, the allocation did not complete or hung. This occurred when the payment was being allocated on an account that had more than 100 invoices. The allocation process has been updated to handle this scenario. |
Customer Care | 84469 | Service address validation errors and issues When creating a service address on the global service address management page in Customer Care the screen would show unvalidated even if USPS and MSAG validation was successful. This has been fixed so the correct validation status is displayed. |
Service Agreements | 84477 | HTML error when attempting to view service agreement PDF The terms & conditions editor in CostGuard Client Product Management > Manage Service Agreements saves the text as HTML so it can be used to generate PDFs. The HTML was inadvertently being modified when editing terms & conditions with bulleted or numbered text. This did not impact the text; however, it did result in an HTML validation error when attempting to view the service agreement in Customer Care. This has been corrected such that when editing terms & conditions with a bulleted or numbered list, the HTML saves correctly and the agreement can be viewed in Customer Care without causing an error. |
Treatment | 84481 | Treatment workbook not supporting optional parameters The solution for PR 84410 was delivered in CostGuard version 23.9 to improve the performance of treatment workbooks for hotline, suspend, restore actions. This caused the HotlineRedirectAccountOrder treatment workbook function to not support optional parameters. This has been corrected. |
Provisioning | 84453 | New service numbers with 10 x’s pulling in PODproperties When adding a new temporary service number, Provisioning POD properties in Orders were defaulted to values from previously provisioned orders. This was due to the Provisioning system finding a match on the service number. The Orders will now only show the default POD Properties, not previously provisioned values, for temporary service numbers. |
Platform System Deployment Updates:
Module | Target Deployment Updates |
|---|---|
None for this release |