Resolved Issues in 37.014.00.00 and later
Not all resolved issues are included on the page below when the release notes are first published. This page will be continuously updated bi-weekly for the subsequent sandbox releases until the next quarterly release.
Issues resolved in 37.014.00.00
Engineering tracking ID | Support tracking ID | Impacted functionality | Reported Issue | Resolved Issue |
ZR-23860 | 427204 | Contract Modification | Retrospective CT MOD is not captured in the CT MOD tab. |
In the initial zero-dollar period, the SO collected the start and end date. For example, 31-Mar-2023 and 31-Mar-2023. In the revised period customers increased it by ten days (31-Mar-2023 and 10-Apr-2023), and expected to trigger the CT MOD rule. In the current logic, if the line is not released, the calculation terms are rounded so that the initial SO and updated SO terms become zero thus not triggering the CT MOD rule. With this release, the rounding is removed when an existing user brings the updated SO within one or two days, the system triggers the term increase CT MOD rule. |
ZR-21945 | 398545 | UI | Latency during linking revenue contract to the de-linked lines | When the user tries to link a revenue contract to all the delinked lines, the operation faces a latency issue, and the system becomes slow. This is an internal issue and has been resolved. |
ZR-23651 | 425729 | UI | Issue while downloading bundle data | When the user tried to download the bundle configuration data, the download resulted in displaying an HTML format, but the history data could be downloaded. This issue is because of a special character present in the bundle data while the allowed data type is only alphabets. This issue is resolved by handling the special characters in the data. |
ZR-20619 | 389347 | UI | Performance issues during multiple job requests | Multiple APIs simultaneously trigger jobs to fetch data regularly until a response is received. Few RCs take a longer time to return data. Multiple refresh or page navigation results in multiple job requests that will queue in the scheduler resulting in performance issues. This issue is fixed by creating a new API that terminates the pending jobs running in the scheduler for a specific session when you refresh the job. |
Issues resolved in 37.014.01.00
Engineering tracking ID | Support tracking ID | Impacted functionality | Reported Issue | Resolved Issue |
ZR-20983 | 390413 | Reporting and Analytics | Line staging exception report |
The Line Staging Exception report contained multiple error columns making it difficult to review and analyze. This release combines these error messages into a single-column heading. In the case of stage table records with multiple error messages, the report will duplicate the record to show both error messages as separate rows. |
ZR-24492 | Data Collection | Unfreeze the RC without changing the CT Mod end date. | Currently, the first batch of the revision period calls the Reallocation API without triggering or changing the CT mod end date. The system follows the prior CT mod end date and reverses the posted adjustment. Later, for the same period, if the user collects the Pros changes, the system does not reverse the reversal, thus losing the prior Adjustments Revenue. You had to move the RC to Retro or provide the data fix to correct the RC. To avoid this, we will call the Switch Allocation API to correct the revenue from this release. |
Issues resolved in 37.014.04.00
Engineering tracking ID | Support tracking ID | Impacted functionality | Reported Issue | Resolved Issue |
ZR-25163 | 436177 | Close Process Dashboard | Auto POB and Unreleased POB tabs display blank results when accessed through RC workbench. |
Auto POB and Unreleased POB tabs displayed blank results when accessed directly through the workbench menu. You can now access these tabs only through Close Process Dashboard > Data Validation tab. |
Issues resolved in 37.014.05.00
Engineering tracking ID | Support tracking ID | Impacted functionality | Reported Issue | Resolved Issue |
ZR-25786 | 440857 | Close Process Dashboard | An issue in downloading SSP Exceptions | When the volume of SSP exceptions is vast, the system generates blank data when you try to export the SSP exception report due to the timeout error. This issue is resolved by limiting the data to fifty thousand (50,000) records for each export to avoid technical errors. |
ZR-26158 | 441615 | Data Collection | An issue in RC Summarisation |
While performing unfreeze RC from UI, the system did not recalculate real-time summarisation. This issue is now fixed by adding Summarisation logic. |
Issues resolved in 37.013.00.00 and later
Refer to Resolved Issues in 37.013.00.00 and later to get a complete list of all issues resolved in this release.