CostGuard Version 19.11 Core Release Bulletin
Change Orders:
Functional Area | AR/FR | Description |
|---|---|---|
Customer Management | FR 3099 | Client attribute URL validation enhancement – This is an under-the-hood enhancement to bring Client attribute URL validation in line with how Customer Care handles validation. The validation in the Client was more restrictive than Customer Care causing complex URLs for applications like SharePoint to not be accepted in the Client. IDI system users will not see any impact as a result of these changes, except that, with less restrictive validation the Client will now be better able to handle complex URLs. |
RateBill | AR 8525 | Option to not apply Credit Type volume discount on past due accounts – When configuring a Credit Type Volume discount, there is a new check box option to not apply the discount when the account has a past due balance. The setting defaults to unchecked (apply regardless of past due balance). |
FR 3107 | Support for user-defined distance types in native Call Detail Records (CDRs) – Updated UnbillableRule CDR087 so it can be set to ignore. This allows user-defined distance types in native CDRs. | |
FR 3110 | Added Record Count totals to Unbillable Analyzer – The Unbillable Analyzer in CostGuard Client (Applications > BackOffice Management > Usage Management) now provides a total for the Record Count column for Unguidables. Totals are also provided for Record Count and Chargeable Instances columns for Unbillables. These fields were added to help IDI’s billing team provide monthly billing documentation. | |
FR 3114 | Increased grant discounting data volume limit – Data grant discounts can now be configured and operate properly on values up to 15 TB. The previous limit was 1.66 TB. | |
FR 3087 | Usage extensibility data on usage views in Customer Care and the Client – Extensibility data may be useful to some carriers for forensic purposes or to help them understand more about the usage scenario. Prior to this enhancement only the wireless usage view in the Client supported showing extensibility data, and Customer Care did not support extensibility data at all. Now all usage views in the Client and Customer Care support displaying extensibility data (when requested, and depending upon availability from the parser). | |
Security | FR 3097 | Automated synchronization of SaaS and Client users: A new system-defined trigger and action automatically creates/updates the Security User table in Admin Console when a Saas User is created or modified in the Security web application. Using the Sync Security Users function in Admin Console will also fire this trigger. Note: The scheduled job still exists; however, it marked as deleted and the infoscript is blank (the job is not functional). |
Collections Workbooks | AR 8534 | Support in Collections Workbooks to create Orders and leverage Workflow – Prior to this release the Workbook created billing orders only (no connection to Workflow). This release provides four new collections workbook functions that create Orders in the Orders web application for disconnecting, hotlining/redirecting, suspending or restoring an account. Orders operate through Workflow which lets you leverage Workflow functionality for these processes. |
Bulk Data | N/A | Maintenance release containing optimization for deployments |
Resolved Known Issues
Functional Area | PR | Description |
|---|---|---|
Customer Care | 83257 | Users not having Manage Contacts permission were unable to save a new E-Pay Account. The process would fail with no message. Now users not having this permission can create and save an E-Pay account; however, they are only permitted to select an existing contact from the drop down (cannot create a new contact). |
RateBill | 83241 | Rather than display an error message when trying to view usage on an account that is both disconnected and devoid of usage, a message indicating no usage is displayed. |
83242 | Preventing total tier rating from corrupting Database table – When the UsageTypeInfoTemp table is empty the first time rating runs and a Total Tier rate method is used, there is the potential for multiple workers to try running the insert query at the same time to populate this table. To avoid this the update was moved farther upstream and outside of the individual workers.. (Not testable by CostGuard Users) | |
83248 | Fixed periodic usage charge tracing to prevent file name collisions. (Not testable by CostGuard Users) | |
83252 | Unable to view OSG Invoices due to license bit dependency – The OSG View Plus License Logic has been corrected such that when OSGviewplus is configured to be used, the system will apply OSGViewPlus logic to show PDFs/Invoices (logic is no longer dependent on a license bit). | |
Address Validation | 83250 | Insure an error code is not returned for successful basic address validations – The new Address Validation web service returns the USPS failure reason which CostGuard does not expect on successful validations. To compensate, now the Error code field is blanked out (USPS Failure reason is removed) when a successfully validated basic address validation response is returned. |
OnlineBill | 83256 | Forgot password process – Previously, when forgot password ran it assumed the DomainID was set in the session and if it wasn’t it was not properly identifying the domain. This presented an issue if you requested a forgot password email but used a different browser or closed your browser and lost the session with the server. This issue has been resolved and OnlineBill is properly identifying the domain in these scenarios. |
Workflow | 83296 | Fixed Data lookups on the Trigger page so that it no longer displays multiple instances of the same data lookup. |
CostGuard Reports (Corporate Accounts) | 83271 | Standard Data Usage Summary CostGuard Report caused the hard drive to fill up – Revised the SQL logic for the Data Usage Summary to optimize the SQL execution for this report due to large volume on the usage records. Affected reports:
|
83272 | When the Payments by Date Summary report was run against a corporate account, it would show two positive payments when part of a payment was allocated to a child account. This caused the payment amount to be greater than it should have been. This has been addressed by the following enhancements:
|
Platform System Deployment Updates:
Module | Target Deployment Updates |
|---|---|
Logging | 11/01/2019 |
Security | 11/01/2019 |
Bulk Data | 11/04/2019 |
Workflow | 11/07/2019 |