Inline Scripting tasks: embed JavaScript or Python directly in a workflow

With Inline Scripting tasks, you can now run JavaScript or Python logic as a workflow step — without building or deploying a dedicated plug-in.

A transformation step between tasks — JSON reshaping, a conditional branch based on an API response, a threshold check — required building and deploying a dedicated plug-in. The deployment cycle existed entirely to carry logic that rarely exceeded twenty lines. The Inline Scripting task removes that overhead: write JavaScript or Python directly in the task properties in the Graphical Designer, declare typed inputs and named outputs, and the step runs on the agent at workflow run time with no artifact to package.

No plug-in to build, no deployment to manage

The Inline Scripting task type is included in the HCL Universal Orchestrator installation. Select it from the task type list in the Graphical Designer, write the script body, and it runs on the next workflow run. The task is designed for short, self-contained logic: data shaping, decision points, and lightweight API calls. Scripts that require external package installation or local file access are outside its scope.

Typed inputs, named outputs — data flows like any other task

The script receives input values through the inputs object, with types declared in the task definition. The return value is published as output properties for downstream tasks using the same mechanism as any other task type. All console output is captured in the task log for tracing and debugging.

Isolation that protects the agent, flexibility where you need it

Scripts run in a sandboxed runtime on the agent: local filesystem access is blocked by default. Outbound HTTP calls are also blocked by default; to enable them, add the target hosts to an allowedHosts list through a connection or at the agent level. The sandbox isolates script runs without preventing the workflow from consuming external data through the configured outbound interface.

For the full Inline Scripting task reference, including language actions, sandbox behavior, and output property mapping, see Inline Scripting tasks. For step-by-step configuration in the Graphical Designer, see Configuring an Inline Scripting task in the Graphical Designer. For the complete input and output parameter reference, see Inline Scripting task parameters and output properties.