2.2 Bugs Fixed in This Release
This section describes the issues which were resolved in this release.
The following bugs have been addressed in OFS CRR Release 8.1.2.10.0.
Table 2-1 Resolved Issues
| Bug ID | Description |
|---|---|
| 38351057 | goAML – Posted Report: Approve Button Not Visible- It has been observed that, in the goAML module, the "Approve" button is not visible on reports that have already been posted. As a result, users are unable to take further approval actions on these posted reports. |
| 38288965 | POP Wallet Setup: goAML Posting Not Working- During the POP Wallet setup, an issue has been identified where the posting to goAML is not functioning as expected |
| 38280716 | Multiple Templates Support Not Working as Expected - An issue has been identified where the functionality for supporting multiple templates is not operating as intended. This feature is designed to allow institutions to configure and manage several reporting templates—such as CA-STR, goAML, and US SAR |
| 38233703 | ECM Milestones for CA-STR: Duplicate Multiple Entries Issue-It has been observed that the ECM (Enterprise Case Management) milestones for CA-STR (Canadian Suspicious Transaction Report) are showing duplicate or multiple entries for the same milestone event. |
| 38221540 | Unable to Save WebConfiguration in RRADMN for POP WebService-There is an issue where users are unable to save the WebConfiguration settings for the POP WebService within the RRADMN (Risk and Reporting Administration) interface. |
| 38186610 | SAR Reports Are Not Getting Approved After Applying ECM Milestones - An issue has been identified where Suspicious Activity Reports (SARs) are not moving to an approved state after the application of ECM (Enterprise Case Management) milestones. |
| 38029877 | SAR Reports Are Not Getting Approved Properly Due to Package (PKG_RRCA_SAVE) Failure in Data Model During Forward Port from 8128 to 81210 -An issue has been encountered during the forward porting process from version 8128 to 81210, where the approval of Suspicious Activity Reports (SAR) is failing. The root cause appears to be the failure of the database package PKG_RRCA_SAVE within the data model. As a result, SAR reports are not moving into an approved status as expected after workflow actions are performed. |