Job Variable Changes in Child Workflows

Prev Next

Breaking Change Notice

This breaking change applies to parent and child workflows in the 2023.2 Itential Platform release.

Job Variable Validation Check

When adding a new input job variable or modifying the name of an existing job variable in a child workflow, it is best practice to update the childJob task in the parent workflow to reflect those changes. However, in some instances, when a job variable is modified in a child workflow, the user may inadvertently forget to make the necessary changes in the parent workflow and the childJob does not start.

To remediate this issue, Itential has implemented a validation check that will stop the parent workflow from running and prevent the workflow from being saved. Additionally, a caution message is displayed to alert users there is a job variable mismatch in a workflow that has a childJob.

What should I do?

For effective workflow execution, always remember to change the parent workflow when modifying a job variable in a child workflow. If you still experience issues, or need additional assistance, please contact the Product Support Team.