Flushing caches through the Groovy Function Editor makes custom functions unusable in workflows in SAS® Risk Governance Framework


In SAS Risk Governance Framework, custom functions created via the user interface (UI) Groovy Function Editor might suddenly become "invisible" or "invalid" within workflow templates.

This issue typically manifests with the following symptoms:

This issue occurs when you flush a cache directly inside the UI Groovy Function Editor page while actively editing or saving a custom function.

When this problem occurs, the following error is reported in the <SASConfigFolder>/Lev1/Web/Logs/SASServer8_1/SASRiskGovernanceFrameworkMidTier.log file: 

WARN  com.sas.ui.cpb3.parser.expression.CallExpression [] - Function named:NAME:C_<your_customVuntion_Name> is invalid.

Workaround

To work around this issue, call the function using its full canonical path instead of the standard alias, which is commonly used in the Custom Page Builder pages.

Standard Alias: C_Bzs()

Using alias option

Replace the expression with the full invocation path: customfunctions.html5Ui.Bzs()

Full path option

Note: Always flush the caches through the Administration ► Site Maintenance ► Flush Caches path if you want your custom function modifications to take effect in the workflow context.