| D17008 for Windows for x64 |
| SAS Enterprise GRC 4.3 |
| Issue(s) Addressed: | Introduced: |
| 41668 | An unknown format type error occurs when you use Data Loading (Carregamento de Dados) in European Portuguese locales (pt or pt_PT) |
D17001 |
| 46085 | A workflow does not start automatically when a near miss amount exceeds the threshold amount |
D17001 |
| 46099 | Financial effects entered as formatted numbers sometimes result in "OpRiskFrameworkError: Not a valid number.." errors |
D17001 |
| 46100 | When exporting questionnaires to Excel, Risk Type details are exported instead of Risk Instance details |
D17001 |
| 45336 | In SASŪ Enterprise GRC, Recovery Amounts incorrectly appear on an Incident's Allocations tab when they should not be included |
D17001 |
| 45333 | The Assessment Template list under risk libraries is not displayed |
D17001 |
| 45329 | The Create Policy link response time is slow |
D17005 |
| 33326 | ALERT - A financial effect might incorrectly use the incident's "Entered On" date |
D17005 |
| 36851 | Risk status shows Open even after it is closed |
D17005 |
| 43004 | Monetary Breakdown table values are incorrect when financial effects have multiple amount entries in different currency denominations |
D17005 |
| 43005 | The Create Incident window becomes read-only |
D17005 |
| 43024 | Searching an incident linked event gives an OpRiskException error |
D17005 |
| 43030 | Configured user with broad scope has slow performance when using the ORA chooser |
D17005 |
| 43159 | ALERT - A "Service Temporarily Unavailable" message occurs when exporting data from SASŪ Enterprise GRC to Excel |
D17005 |
| 43161 | ALERT - A financial effect that was created from an incident has an incorrect converted amount |
D17005 |
| 43436 | The list of assessment templates is incorrectly empty |
D17005 |
| 43627 | Allocation percentage totals are not correct when allocating by amount |
D17005 |
| 45061 | "An error has occurred and has been logged" message appears when selecting a control table heading |
D17005 |
| 45271 | Insurance monetary conversion fails for non-English languages, an IllegalArgumentException appears |
D17005 |
| 45273 | A javascript warning dialog box "Error: '0' is null or not an object" appears when assigning testers to a control instance |
D17005 |
| 45274 | Direct recovery ORA is not automatically the incident ORA when correctly customized |
D17005 |
| 45322 | ALERT - A "Service temporarily unavailable" error message appears when exporting to Excel from the Issues screen |
D17005 |
| 45323 | How to specify and configure up to 5 KRI thresholds |
D17005 |
| 45324 | Normalized KRI scores might be missing from workflow e-mail |
D17005 |
| 45325 | Searching for a user field in a table fails with a "PropertyMessageResources.." error |
D17005 |
| 45326 | "Error on Page" is displayed when you select user values the query page |
D17005 |
| 45328 | Performance is slow when selecting a dimension in the ORA chooser even though "pre-compute" is configured |
D17005 |
| 45334 | Searching for objects in SASŪ Enterprise GRC should enable you to search for Incidents |
D17005 |
| 45353 | A ServletException occurs when you select a linked Test Plan in a Policy |
D17005 |
| 43003 | ALERT - Running orm_create_all_full_load.sas might take a long time and show "there is not enough WORK disk space.." errors |
D17005 |
| 45284 | The KRI report in SASŪ Enterprise GRC does not contain complete information |
D17005 |
| 45327 | When exporting loss data from SASŪ Enterprise GRC to SASŪ OpRisk VaR, if there is no recovery amount, a recovery date is incorrectly assigned |
D17005 |
| 45330 | ALERT - When exporting loss data from SASŪ Enterprise GRC to SASŪ OpRisk VaR, losses that have not been validated are incorrectly omitted |
D17005 |
| 46084 | Unable to control listed order of risks or controls in an assessment |
D17008 |
| 46104 | ALERT - You can create and edit a financial effect even though your role does not give you necessary permissions |
D17008 |
| 43364 | ALERT - A Javascript error occurs when report parameter prompts are Hebrew |
D17008 |
| 44661 | Saving a new incident prompts you for a change reason |
D17008 |
| 46101 | Custom field historical data is incomplete and inaccurate when extracted for report mart build |
D17008 |
| 46103 | Modifying comments or attachments causes Issues and Action Plans to be re-validated |
D17008 |
| 46105 | A newly created incident asks for a reason that you are saving |
D17008 |
| 46110 | The "Return from Validation" button is grayed-out |
D17008 |
| 46113 | You cannot specify an incident discovered date that is later than its financial impact loss date |
D17008 |
| 46119 | A "No value or invalid value for instance.instanceId" error appears when loading MonitorAnswerSheets |
D17008 |
|
| D indicates that the Documentation has special pre-installation, post-installation or other unique instructions not commonly used for hot fix deployment. |