Customers may observe that TERR functions such as getwd() execute successfully when used inside a TERR expression function, even when TERR Services is configured with restricted execution mode (terr.restricted.execution.mode is set to TRUE).

Since getwd() is restricted when executed on the TERR Services server; this behavior may lead to the assumption that the expression is being executed remotely. However, this assumption is incorrect.

TERR expression functions are designed to always execute locally in Spotfire Analyst. These functions are internally executed with a forced local execution flag, which causes them to bypass TERR Services entirely. As a result, TERR Services settings and restrictions do not apply to expression functions.

Additionally, disabling the Use local TERR option does not affect the execution of expression functions.

All

This behavior is expected and by design.

Key points to note:

• TERR expression functions always run on the local TERR engine.

• The 'Use local TERR' setting applies only to Data Functions, not expression functions.

• TERR Services configuration, including restricted execution mode, does not impact expression functions.

• There is no supported method to force a TERR expression function to execute on the TERR Services server.

If server-side execution is required, the logic must be implemented using a Data Function instead of a TERR expression function.

TERR (Spotfire Enterprise Runtime for R) expression functions in Spotfire Analyst always execute on the local TERR engine, regardless of TERR Services configuration or execution mode settings.

Expression Functions :

• expression functions