Version

    40. Graph/Jobflow Parameters

    Parameters by Execution Type
    Adding Another Graph Parameters

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

    Graph parameters can be used by ${paramName} placeholders. Keep in mind that these placeholders are resolved at the start of job execution during the initialization (loading of XML definition file).

    This is a set of parameters which are always set by CloverDX Server:

    Table 27. Defaults for graph execution configuration
    Key Description

    SANDBOX_CODE

    An identifier of a sandbox which contains the executed graph.

    JOB_FILE

    A path to the file (graph, subgraph, jobflow). The path relative to the sandbox root path.

    SANDBOX_ROOT

    An absolute path to sandbox root.

    RUN_ID

    An ID of the graph execution. In a standalone mode or Cluster mode, it is always unique. It may be a value lower than 0, if the run record isn’t persistent.

    PARENT_RUN_ID

    A run ID of the graph execution which is the 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 the 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_ID

    An ID of the node running the graph or jobflow.