Using conditional dependencies
Using conditional dependencies is a powerful way to manage scheduling workflow processing. It allows you to dynamically define alternative branches, for example, to run a recovery alternative flow. These alternative branches, when their processing completes, are automatically removed from the current plan when the daily plan batch is run.
For example, an application developer can use conditional logic to reduce the Total Cost of Ownership (TCO) and increase the automation of the business processes managed using HCL Workload Automation for Z. By using conditional dependencies while implementing workflow, he can automate the flow to follow alternative branches when a combination of specific criteria on operations occurs.
You can define conditional dependencies
at the following levels:
- Job level
- By conditioning the start of the conditional successor to the check on job return code or status of the conditional predecessor. For more details, see Making an operation dependent on the status or return code of another operation.
- Step level
- By conditioning the start of the conditional successor to a specific step return code of the conditional predecessor. For more details, see Making an operation dependent on another operation step return code.