Specify dependencies on an unconnected work item

Specify a dependency on a proxy job

About this task

You can specify a dependency on another flow, or a work item that is running within another flow, or on a work item elsewhere in the current flow by creating a proxy event. You can specify the following types of dependencies:

  • When the work item is submitted
  • When the work item starts
  • When the work item ends successfully
  • When the work item exits with any exit code
  • When the work item exits with a specific exit code
  • When the work item exits with any of the specified exit codes. You can specify a list of space-separated exit codes with the event type Ends with exit code... and Equal to and Not equal to. You can specify a list of exit codes for a proxy job, proxy template job, proxy job script, and proxy local job.

Procedure

  1. Change to proxy event mode by clicking the Insert Proxy Event button.
  2. Click in the workspace where you want to insert the proxy event. The proxy event icon does not yet appear in the workspace. The Proxy Event Definition dialog box appears.
  3. In the Create proxy for... box, leave the default at Job.
  4. In the Job name field, specify the fully qualified name of the job, in the following format:

    flow_name:subflow_name:job_name

    If the job is not defined within a subflow, simply specify the flow name and the job name, separated by a colon.

    Note: You cannot specify a proxy for a manual job.

  5. If the flow containing the job is not owned by your user ID, in the Owner field, specify the user ID that owns the flow containing the proxy job.
  6. In the Duration field, specify the number of minutes within which the proxy event should remain valid after it becomes true. If the number is 0(default duration), the proxy event will always be valid and will never expire after it becomes true.
  7. In the Event type field, select the type of dependency you want to use to trigger the successor job, job array, subflow or flow, and the appropriate operator and values.
  8. In the Description field, add any descriptive text that may be used for understanding this event.
  9. Click OK. The proxy event appears in the workspace, and you can draw the appropriate dependency lines to any work items.

Specify a dependency on a proxy job array

Procedure

  1. Change to proxy event mode by clicking the Insert Proxy Event button.
  2. Click in the workspace where you want to insert the proxy event. The proxy event icon does not yet appear in the workspace. The Proxy Event Definition dialog box appears.
  3. In the Create proxy for... box, select Job Array.
  4. In the Job array name field, specify the fully qualified name of the job array, in the following format:

    flow_name:subflow_name:job_array_name

    If the job array is not defined within a subflow, simply specify the flow name and the job array name, separated by a colon.

  5. If the flow containing the job array is not owned by your user ID, in the Owner field, specify the user ID that owns the flow containing the proxy job array.
  6. In the Duration field, specify the number of minutes within which the proxy event should remain valid after it becomes true. If the number is 0(default duration), the proxy event will always be valid and will never expire after it becomes true.
  7. In the Event type field, select the type of dependency you want to use to trigger the successor job, job array, subflow or flow, and the appropriate operator and values.
  8. In the Description field, add any descriptive text that may be used for understanding this event.
  9. Click OK. The proxy event appears in the workspace, and you can draw the appropriate dependency lines to any work items.

Specify a dependency on a proxy subflow

About this task

You can specify the type of dependency to be one of the following:

  • The flow completes successfully—the default
  • The flow fails
  • The flow ends with any exit code
  • The flow fails with the specified exit code
  • The subflow completes successfully with the specified exit code
  • The flow has the specified exit code
  • A specified number of successful jobs
  • A specified number of jobs finished with any exit code
  • A specified number of unsuccessful jobs
  • A specified number of started jobs

Procedure

  1. Change to proxy event mode by clicking the Insert Proxy Event button.
  2. Click in the workspace where you want to insert the proxy event. The proxy event icon does not yet appear in the workspace. The Proxy Event Definition dialog box appears.
  3. In the Create proxy for... box, select Subflow.
  4. In the Subflow name field, specify the fully qualified name of the subflow, in the following format:

    flow_name:subflow_name

  5. If the flow containing the subflow is not owned by your user ID, in the Owner field, specify the user ID that owns the flow containing the proxy subflow.
  6. In the Duration field, specify the number of minutes within which the proxy event should remain valid after it becomes true. If the number is 0(default duration), the proxy event will always be valid and will never expire after it becomes true.
  7. In the Event type field, select the type of dependency you want to use to trigger the successor job, job array, subflow or flow, and the appropriate operator and values.
  8. In the Description field, add any descriptive text that may be used for understanding this event.
  9. Click OK. The proxy event appears in the workspace, and you can draw the appropriate dependency lines to any work items.

Specify a dependency on a proxy flow

Procedure

  1. Change to proxy event mode by clicking the Insert Proxy Event button.
  2. Click in the workspace where you want to insert the proxy event. The proxy event icon does not yet appear in the workspace. The Proxy Event Definition dialog box appears.
  3. In the Create proxy for... box, select Flow.
  4. In the Flow name field, specify the name of the flow.
  5. If the flow is not owned by your user ID, in the Owner field, specify the user ID that owns the flow.
  6. In the Duration field, specify the number of minutes within which the proxy event should remain valid after it becomes true. If the number is 0(default duration), the proxy event will always be valid and will never expire after it becomes true.
  7. In the Event type field, select the type of dependency you want to use to trigger the successor job, job array, subflow or flow, and the appropriate operator and values.
  8. In the Description field, add any descriptive text that may be used for understanding this event.
  9. Click OK. The proxy event appears in the workspace, and you can draw the appropriate dependency lines to any work items.
    Note:

    You can change the text of the label that appears above the proxy event in the workspace if the label text is too long.