| D25004 |
| SAS Model Manager 2.3 |
| Issue(s) Addressed: | Introduced: |
| 41764 | Expanding or clicking items in the Project Tree responds slowly |
D25001 |
| 42319 | When using Java Web Start, clear the java cache after applying SASĀ® Model Manager hot fixes |
D25001 |
| 41954 | Performance reports give a "report could not be generated ... invalid input variables ..." error |
D25001 |
| 42718 | The Characteristic Analysis reports are empty |
D25001 |
| 42719 | Assessment results for a formatted numeric target variable are incorrect |
D25001 |
| 39671 | Connection-refused-to-host errors occur if a firewall exists when you log on to SASĀ® Model Manager |
D25002 |
| 43220 | A libname INDB is not assigned error occurs when you use the Publish Scoring Function window to create a Teradata function |
D25002 |
| 43026 | Performance-monitoring reports are not sorted and they contain missing values |
D25002 |
| 44251 | The Define Dashboard Report Indicators report fails to respond when running on a non-localized version |
D25003 |
| 44253 | MM_GetModels macro returns "ERROR: A character operand was found in the %EVAL function or %IF condition where a numeric operand is required." |
D25003 |
| 44419 | Performance Monitoring Reports give an "Invalid string" error when using score code that contains non-English Characters |
D25003 |
| 45906 | User-defined formats return incorrect bin definitions on Performance Reports |
D25004 |
| 46169 | Bin definitions might cause performance monitoring graphs to be incorrect |
D25004 |
| 46170 | Performance monitoring reports give "ERROR: File WORK.PREDICTORSUMMARY.DATA does not exist" |
D25004 |
|
| D indicates that the Documentation has special pre-installation, post-installation or other unique instructions not commonly used for hot fix deployment. |