Chapter 27. Graph/Jobflow Parameters

The CloverDX Server passes a set of parameters to each graph or jobflow execution.

Keep in mind that ${paramName} placeholders (parameters) are resolved only during the initialization (loading of XML definition file), so if you need the parameters to be resolved for each job execution, you cannot set the job to be pooled. However, current parameter values are always accessible by an inline Java code:

String runId = getGraph().>getGraphProperties().getProperty("RUN_ID");

Properties may be added or replaced:

getGraph().getGraphProperties().setProperty("new_property", value);

This is a set of parameters which are always set by CloverDX Server (for more information, see Job Config Properties):

Table 27.1. Defaults for graph execution configuration

keydescription
SANDBOX_CODE An identifier of a sandbox which contains the executed graph.
JOB_FILEA path to the file (graph, subgraph, jobflow). The path relative to the sandbox root path.
SANDBOX_ROOT An absolute path to sandbox root.
RUN_IDAn ID of the graph execution. In a standalone mode or cluster mode, it is always unique. It may be lower than 0 value, if the run record isn't persistent. For more information, see Chapter 39, Launch Services.
PARENT_RUN_ID A run ID of the graph execution which is a parent to the current one. Useful when the execution is a subgraph, child-job of some jobflow or worker for distributed transformation in a cluster. When the execution doesn't have a parent, the PARENT_RUN_ID is the same as RUN_ID.
ROOT_RUN_ID A run ID of the graph execution which is a root execution to the current one (the one which doesn't have a parent). Useful when the execution is a subgraph, child-job of some jobflow or worker for distributed transformation in a cluster. When the execution doesn't have a parent, the ROOT_RUN_ID is the same as RUN_ID.
CLOVER_USERNAME The username of the user who launched the graph or jobflow.
NODE_IDAn ID of the node running the graph or jobflow.