IDI Platform Version 23.5 Core Bulletin
Change Orders
Functional Area | AR/FR | Description |
|---|---|---|
Orders | FR 3397 | Enhanced customer search For orders that require selecting a customer account, the Basic Information section on the New Transaction page provides an option to search on service number or social security number. |
Provisioning | AR 9135 | Metaswitch provisioning actions This completes the functionality for AR 9135. This release provides two new actions:
See the Metaswitch Provisioning specification in the IDI Knowledge Center for details. |
Inventory Communications Document Storage | N/A | Internal maintenance updates |
Resolved Known Issues
Functional Area | PR | Description |
|---|---|---|
Customer Care | FR 3463 | Updates forMaster Street Address Guide (MSAG) Validation MSAG validation was originally added to Customer Care in CostGuard version 23.3. This release (23.5) provides updates to an error dialog and resolves an issue related to creating a new service address. |
Customer Care | 84335 | Unvalidated entries on Service Address page causing errors On the Service Addresses page (Services > Service Addresses) the Street Number To/From fields had no limitations on number of characters. This was causing errors when an entry exceeded string length restrictions in the database. These fields have been updated to have number of character limitations that match their corresponding database fields. |
Payment Processing – Paymentus | 84361 | Resolved issues in earlier release This release fixes two issues related to Paymentus:
|
Customer Management – Service Address Validation | 84359 | Set service address validation date to current date & time A previous change to the Customer web service inadvertently made the Validation Date required when creating a new Service Address. This has been fixed so the Validation Date is optional. |
Installment Plans | 84324 | Installment plan charges incorrectly reversed by reverseservice The Reverse Service Penalties action was reversing penalties on installments for contracts and installment plans that were not reconnected with the service. The action was updated to not reverse the charges if the installment and/or contract was not reconnected. |
CostGuard Client – POS Make Sale | 84348 | Performance issues Large accounts with many transactions were experiencing performance issues where it would take too long to open and navigate related views. Related logic has been optimized to improve performance. |
CostGuard Client – Customer Management | 84320 | Security logging error on using Customer window Actions menu Since CostGuard 22.11, a critical error would be generated when invoking an action from the CostGuard Client Customer window Actions menu. The error was due to a null reference generated when selecting any action from this menu. On clicking Close to dismiss the error message, the action would complete successfully. This has been fixed (no false errors on using an action from this menu). |
CostGuard Client – Customer Management | 84371 | Error on attempting to create a prospect This issue was introduced by AR 8924 – Automate Clearing Tax Jurisdiction Override on Address Change in CostGuard version 22.8. This AR added a Remove Tax Jurisdiction Overrides on Address Change setting in Customer Care. The setting applies in both Customer Care and CostGuard Client. When this setting was enabled an error occurred on adding a new prospect in CostGuard Client. This setting should not apply when adding a prospect since they are not full customers and tax overrides do not apply. This has been fixed by ignoring the Remove Tax Jurisdiction Overrides on Address Change setting when adding a new prospect. |
Treatment | 84370 | Performance issue with hotline order via collection workbook Processing large batches of hotline orders via the collections workbook would timeout some times. Workbook performance has been improved to help avoid timeouts. |
Address Validation – Core Logic | 84365 | Null value returned when no FIPS code found FIPS codes are the numbers used to identify geographic regions like countries, states and counties. When no FIPS code is defined, Core Logic should return a FIPS code of 00000; however, since Core Logic was updated to use the new Spatial API rather than GSERT, it was returning no FIPS code (nothing) in this case. The address validation web service was updated to account for this scenario and now sets FIPS code to 000000 instead of nothing consistent with the original (GSERT) functionality. |
Platform System Deployment Updates:
Module | Target Deployment Updates |
|---|---|
Metaswitch | 05/09/2023 |
Bulk Data | 05/16/2023 |
Workflow | 05/16/2023 |