| C3S004 for Linux for x64 |
| SAS Model Risk Management 7.3 |
| Issue(s) Addressed: | Introduced: |
| 61899 | Special characters are not displayed correctly in reports for SAS® Model Risk Management or a content release on SAS® Risk Governance Framework |
C3S001 |
| 61831 | You see a "GoJS evaluation" watermark in SAS® Model Risk Management or in a content release on SAS® Risk Governance Framework |
C3S001 |
| 61893 | The Dimension Browser screen stops responding in SAS® Model Risk Management or in a content release on SAS® Risk Governance Framework |
C3S001 |
| 61894 | SAS® Model Risk Management or a content release on SAS® Risk Governance Framework stops responding after you edit a document in Rich Text Format |
C3S001 |
| 62750 | The ETL job in SAS® Model Risk Management or a content release on the SAS® Risk Governance Framework cannot connect to the SAS® LASR™ Analytic Server |
C3S002 |
| 61916 | The Export to Excel feature in SAS® Enterprise GRC and SAS® Model Risk Management contains security vulnerabilities |
C3S002 |
| 62682 | SAS® Model Risk Management and SAS® Enterprise GRC include a version of Apache POI that contains security vulnerabilities |
C3S002 |
| 62816 | Linked object tables in SAS® Model Risk Management display the link instance RK instead of the link instance ID |
C3S002 |
| 62817 | The UserChooser component in SAS® Model Risk Management displays both active and inactive users |
C3S002 |
| 62820 | SAS® Model Risk Management ignores the group number when you add a rich text document to a business object |
C3S002 |
| 62845 | With Microsoft Internet Explorer, SAS® Model Risk Management does not close the secondary browser tab after you create a linked business object |
C3S002 |
| 62851 | The Update Document and Update Rich Text Document screens in SAS® Model Risk Management do not show the group number value |
C3S002 |
| 62857 | You can specify a customization file for a content attachment in SAS® Model Risk Management or a content release on SAS® Risk Governance Framework |
C3S002 |
| 62859 | SAS® Model Risk Management does not save the value of a Boolean custom field for the Attachments business object, when the value is No |
C3S002 |
| 62860 | The GetBusinessObjects function in SAS® Model Risk Management returns the wrong business object in a linked relationship |
C3S002 |
| 62868 | The adjustDate function fails in a workflow template for SAS® Model Risk Management or a content release on the SAS® Risk Governance Framework |
C3S002 |
| 64379 | The grid_host.map file does not allow enough characters for a host name, causing the ETL job in SAS® Model Risk Management to fail |
C3S004 |
| 64072 | You see a "java.lang.NullPointerException" error in the SAS® Cache Locator log after you flush caches in SAS® Model Risk Management |
C3S004 |
| 64382 | SAS® Model Risk Management displays an empty query table when you click Next to display the next set of objects |
C3S004 |
| 64429 | SAS® Model Risk Management returns a "java.lang.IllegalArgumentException" error when you try to remove a user's default location |
C3S004 |
| 64439 | SAS® Risk Governance Framework does not display some attachments for a business object that was created from an existing object |
C3S004 |
| 64789 | SAS® Model Risk Management fails to respond when you select a workflow action for an object and a field value contains consecutive question marks |
C3S004 |
| 64790 | You see a "delegation already exists" error in SAS® Model Risk Management when you add a delegate for the same time period as an existing delegate |
C3S004 |
| 64797 | SAS® Model Risk Management or a content release on the SAS® Risk Governance Framework incorrectly converts dates that you enter manually |
C3S004 |
| 64800 | You see a "not a valid JSON document" error when you add a link attachment to an object in a content release on the SAS® Risk Governance Framework |
C3S004 |
| 64801 | You experience slow performance in SAS® Model Risk Management when you edit a business object that contains a large number of attachments |
C3S004 |
|
| D indicates that the Documentation has special pre-installation, post-installation or other unique instructions not commonly used for hot fix deployment. |
General Information about Hot Fixes