When you execute SAS code in a content release on the SAS Risk Governance Framework, you can now dynamically choose the SAS Workspace Server that is used to run the code. With the following new configuration property, you can specify the name of a Groovy script that returns the name of the desired workspace server:

The Groovy script should return the name of the SAS Workspace Server in string format, such as either of the following values:

• SASApp - Logical Workspace Server
• SASApp - Logical Pooled Workspace Server

For example, you could choose a SAS Workspace Server based on the roles for the current user. You could run the code on the SASApp - Logical Workspace Server if the user is an administrative user and the SASApp - Logical Pooled Workspace Server if the user is not an administrator.

The Groovy script should be placed in the WebDAV repository in the sasdav/Products/SASRiskGovernanceFramework/RiskGovFrwkMid-Tier/solution-identifier/Scripts directory.

The SAS Risk Governance Framework uses the following priority order to determine which SAS Workspace Server to use when running SAS code:

1. the server that is specified in an invocation of the SASCodeExec Java class in a Groovy script or through the ExecuteSASCode function in a screen definition file 
2. the value returned by the Groovy script that is specified in the monitor.workspaceServerNameGroovy configuration property
3. the value of the monitor.workspaceServerName configuration property
4. the SASApp - Logical Pooled Workspace Server

Click the Hot Fix tab in this note to access the hot fix for this issue.

Operating System and Release Information

A fix for this issue for SAS Risk Governance Framework 7.4 is available at: