Problem Note 60206: SAS® Risk and Finance Workbench 2.3 Hot Fix A4G002: Release Notes
SAS Risk and Finance Workbench 2.3 Hot Fix A4G002 contains the following changes:
- Adds software component properties and tools to manage those properties in order to maintain the content package SAS Regulatory Content for IFRS 9 across releases
- Adds support for business-friendly custom sheet labels for EBA templates that have a valid value of SHEET_CD
- Adds support for the Legal Entity Identifier (LEI) attribute definition as part of the entity hierarchy definition. LEI is required for the final XBRL reports that are used for regulatory submissions.
- Adds support for versioning of the RFW LUA APIs as part of the content package SAS Regulatory Content for IFRS 9
- Adds support to drill into details from cells in worksheets that are defined based on regulatory report specifications
- Adds the ability of the _OG macro to correctly resolve a formula in the following cases:
* if the cell to be exported references a non-exported cell
* if there are multiple worksheets that refer to the same underlying worksheet but with different filters
- Adds the ability of the LUA APIs to handle large scenario files
- Adds the ability to allow Read-Only access to a worksheet template definition to users that have only Read access to the data
- Adds the ability to allow Read-Only access to a worksheet to users that have only Read access to the data
- Adds the ability to create multiple packages for the same SAS Regulatory Content for EBA Taxonomies content package in the same RFW project, in which each content package refers to its own unique set of hierarchies
- Adds the ability to present a change log that contains a summary of the data changes of a task transition
- Adds the ability to publish results of report run for package-based reports to project- and entity-specific folders on the server
- Adds the ability to reference a status label in place of action label in order to detect the success or failure of a script execution through a process flow task
- Adds the ability to restrict the editing of worksheets by a “maker” user (that is, a user that makes the data) to certain users in specific states, and to not allow the editing of the worksheets while a “checker” user (that is, a user that reviews the data) reviews the data
- Adds the ability to specify at project creation time whether to allow a user to enter or change a cell value without a comment
- Adds the ability to support the correct display of worksheets when multiple content packages for the same SAS Regulatory Content for EBA Taxonomies content package are created within the same RFW project
- Adds the ability to support more filters than the called worksheet data by using the getWorksheet REST API
- Adds the ability to support subtotals and formulas on the x-axis, that is, the column hierarchies. By itself, the time hierarchy does not have any aggregation.
- Adds the ability to specify a URL that can be launched as part of a task in the process flow definition. Users can specify a direct URL, a relative URL, or a URL with pre-defined parameters. The ability to override or change the parameter values during project execution is not supported at this time.
- Adds the ability to perform a REST API call that submits SAS code which in turn runs a PROC HTTP step in RFW by using a more secure mechanism. This feature uses "CAS Ticket Granting Ticket" in place of logon credentials in order to strengthen the level of security.
- Adds the ability to support the use of a time period as a parameter to the _OG macro. This feature enables you to reuse the report templates across RFW projects.
- For loading data from the landing area or running the Data Sufficiency or Preview Data from Landing Area reports, adds support for the selection of a landing area data set from the available list of data sets that are in folders for multiple projects and multiple entities
- Enhances the LUA API with the ability to return the software component URI from the metadata as part of the content package SAS Regulatory Content for IFRS 9
- Enhances the process flow APIs with the ability to retrieve action-related information in addition to the details that are already returned
- Improves error handling in the "get Hierarchy Key" LUA API as part of the content package SAS Regulatory Content for IFRS 9
- Improves error handling in the "load hierarchy data" LUA API as part of the content package SAS Regulatory Content for IFRS 9
- Improves the error messaging when the content package SAS Regulatory Content for EBA Taxonomies is not installed or when some of the taxonomy specification tables are not set up correctly
- Improves the handling of spaces that precede or trail key values in a process flow definition
- Improves the messaging in the UI when loading data
- Adds the display of the model group version on the Model Group Runs summary page
- Includes the utility LUA APIs for other dependent APIs as part of the content package SAS Regulatory Content for IFRS 9
- Resolves an issue with worksheet rendering in order to handle use cases that are related to dynamic row hierarchy and dynamic z-axis
- Resolves an "out-of-memory" error that occurs when RFW queries for a large number of scenarios from the scenario repository. In this hot fix, this is addressed by querying for scenario details one at a time.
- Resolves a regression issue in which allocation does not properly update a cell in a multidimensional worksheet with two or more levels of hierarchy on the y-axis
- Resolves a regression issue with data synchronization in which the application does not support both refresh and no refresh actions when multiple users are working on the same set of data or worksheet
- Resolves a regression issue with EBA validation errors not being displayed on a worksheet cell hover-over
- Resolves an issue regarding the ability to resolve cross-sheet formulas when the participating hierarchies are flipped in two different worksheets
- Resolves an issue regarding the ability to save worksheet data changes when other worksheets that have user visibility restrictions are present
- Resolves an issue regarding calls to the workspace server failing when using a REST API that submits SAS code that calls a PROC HTTP step in RFW. The called REST API needs access to the server tier via a workspace. The acquisition fails when the HTTP_TOKENAUTH option is used with a PROC HTTP step. The hot fix resolves the problem by allowing host authentication and reusing the user logon credentials in order to make the appropriate calls.
- Resolves an issue in which changing the worksheet category refreshes the worksheet list but shows data from the previous worksheet
- Resolves an issue with the clearing of user preferences that pertains to worksheets for which the content package SAS Regulatory Content for EBA Taxonomies is deleted
- Resolves an issue regarding the consistent handling of user security across all levels of a hierarchy and multiple hierarchies on an axis
- Resolves an issue regarding the consistent resolution of data crossings across the UI, export functionality, and reports
- Resolves an issue with the handling of single quotation marks in project and hierarchy names when they are fetched through content package APIs
- Resolves an issue in which the entity name is truncated when it is fetched through the content package API
- Resolves an issue with the inheritance of work groups for worksheet templates and projects not taking into account worksheet template refinements (for example, line item exclusions)
- Resolves an issue with not allowing multiple versions of the same hierarchy in a project
- Resolves an issue with not being able to change a worksheet category if a user changes the filters on the existing worksheet that is being viewed
- Resolves an issue with optimization of the content package API calls from the UI
- Resolves an issue with project deletion failing when there are a large number of hierarchies (that is, more than 1000) present in the system
- Resolves an issue with the retrieval of project properties if a property has been defined with an empty name
- Resolves an issue with users being able to modify historical data if time is specified on the y-axis, that is, row hierarchy in a worksheet
- Resolves a "nullpointerexception" error when reading large scenario data from the scenario repository into RFW
- Resolves an issue with the ability to display data if a scenario hierarchy is used on the y- (row) or x- (column) axis
- Resolves an issue with the ability to load data from landing area data set to RFW for all templates that have at least one row of data present
- Resolves an issue with the ability to load detailed data from specific work group folders when a user is member of multiple work groups, as part of the content package SAS Regulatory Content for IFRS 9
- Resolves an issue with the ability to migrate package hierarchy definitions from RFW 2.2 to 2.3
- Resolves an issue with the ability to preview the landing area data for currencies other than the current or reporting currency
- Resolves an issue with the definition of a correct path for a SAS Model Implementation Platform run instance in the Attribution Analysis task as part of the content package SAS Regulatory Content for IFRS 9
- Resolves an issue with aliasing of APIs for compatibility while they are referenced in the content package SAS Regulatory Content for IFRS 9
- Resolves some issues with case sensitivity in the LUA APIs as part of the content package SAS Regulatory Content for IFRS 9
- Resolves some issues that pertain to editing worksheet template definitions and a subsequent cancel action that causes abnormal UI behavior
- Resolves an issue when a user changes an iteration, changes a value on a worksheet, and saves, in which earlier iteration data is also updated
- Corrects the name of allocation rules that are called from the content package SAS Regulatory Content for IFRS 9
Operating System and Release Information
SAS System | SAS Risk and Finance Workbench | Microsoft® Windows® for x64 | 2.3 | 2.4 | 9.4 TS1M4 | 9.4 TS1M4 |
Linux for x64 | 2.3 | 2.4 | 9.4 TS1M4 | 9.4 TS1M4 |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
Type: | Problem Note |
Priority: | high |
Date Modified: | 2017-03-31 04:13:31 |
Date Created: | 2017-03-30 03:15:27 |