When a workflow runs, the objects that pass from one workflow element to another are not Javascript objects. What is passed from one element to the next is the serialization of a Java object that has a Javascript image. As a consequence, you cannot use the whole Javascript language, but only those classes that are present in the API Explorer. You cannot pass function objects from one workflow element to another.

Orchestrator runs the code in scriptable task elements in a context that is not the Rhino root context. Orchestrator transparently wraps scriptable task elements and actions into Javascript functions, which it then runs. A scriptable task element that contains System.log(this); does not display the global object this in the same way as a standard Rhino implementation.

You can only call actions that return nonserializable objects from scripting, and not from workflows. To call an action that returns a nonserializable object, you must write a scriptable task element that calls the action by using the System.getModuleModuleName.action() method.

Workflow validation does not check whether a workflow attribute type is different to an input type of an action or subworkflow. If you change the type of a workflow input parameter, for example from VIM3:VirtualMachine to VC:VirtualMachine, but you do not update any scriptable tasks or actions that use the original input type, the workflow validates but does not run.