Home
Orchestrating
Orchestrate anything with HCL Universal Orchestrator.
Data exchange and transformation
This topic explains how you can streamline your workflows using data exchange and transformation.
Passing variables between jobs
This topic shows how to pass variables between jobs.

Orchestrating
Orchestrate anything with HCL Universal Orchestrator.
- Orchestration CLI commands
  You can use the various command options in Orchestration CLI to achieve specific results. The command options are not case sensitive and you can use either uppercase or lowercase letters.
- Job stream definition
  This topic introduces the job stream definition, that can be managed from the Orchestration CLI and from the Dynamic Workload Console.
- Job definition
  This topic introduces the job definition, that can be managed from the Orchestration CLI and from the Dynamic Workload Console.
- Calendar definition
  This topic introduces the calendar definition, that can be managed from the Orchestration CLI and from the Dynamic Workload Console.
- Folder definition
  This topic introduces the folder definition, that can be managed from the Orchestration CLI and from the Dynamic Workload Console.
- Credentials definition
  This topic introduces credentials definition, that can be managed from the Orchestration CLI and from the Dynamic Workload Console.
- Variable table definition
  This topic introduces the variable table definition, that can be managed from the Orchestration CLI and from the Dynamic Workload Console.
- Workstation definition
  This topic introduces the workstation definition, that can be done from the Orchestration CLI and from the Dynamic Workload Console.
- Managing matching criteria
  In this topic you can find a description of matching criteria.
- Managing time zones
  In this topic you can find information about managing time zones.
- Policy-driven plan
  The new HCL Universal Orchestrator policy-driven adaptive plan makes your workload more autonomous, dynamic and scalable.
- Data exchange and transformation
  This topic explains how you can streamline your workflows using data exchange and transformation.
  - Job context structure
    Provides a list and explanation of all fields in the job context structure.
  - Job context structure example
    Job context example
  - Proprietary functions for JSONata
    Full list and description of proprietary HCL Universal Orchestrator functions available for using with JSONata.
  - Passing variables between jobs
    This topic shows how to pass variables between jobs.
    - Passing properties from one job integration to another job in the same job stream instance
      This topic shows how to pass properties from one job integration to another job in the same job stream instance.
    - Passing variables set by using jobprop in one job to another in the same job stream instance
      You can use the jobprop utility installed on dynamic agents to set one or more variables and their value in a job and pass it to the successive job in the same job stream instance. This utility is supported only on executable jobs.

Passing variables between jobs

This topic shows how to pass variables between jobs.

In many scenarios, the job output or a job property of a job in a job stream can be the input for the execution of a successive job in the same job stream or in a different job stream.

In the following scenario, you have JobA and JobB in the same job stream instance and JobA is a predecessor of JobB. JobA passes some properties to JobB at execution time.

You can pass the following properties from JobA to JobB:

JobA exports some properties and JobB references these properties in its definition as variables in a predefined format. At execution time, variables in JobB are automatically resolved. The job properties that you can export depend on the job type you are defining. See Passing properties from one job integration to another job in the same job stream instance.
Only for executable jobs. JobA sets some custom property values by using the jobprop utility on dynamic agents. JobB references these properties as variables in its definition. At execution time, variables in JobB are automatically resolved. See Passing variables set by using jobprop in one job to another in the same job stream instance.