ACP-120 workflows and automation: what the exam tests

If a validator fails, the work item stays where it is and the post functions never run. A team-managed space allows up to 100 statuses in all, and up to 50 in any one workflow.

01 What does ACP-120 test about workflows and automation?

You read a stem about a transition button that never appears and suspect a permission problem. In this domain the cause is often a transition rule, a status setting or an automation step.

What the exam asks about in this domain

1. 01TransitionsTriggers, conditions, validators, post functions and properties
2. 02Team-managed statusesLimits, board columns and the Any status transition
3. 03Automation flowsTriggers, conditions, actions and branches

Know transitions, team-managed statuses and automation flows.

02 What does each part of a transition do?

A condition decides whether the user may run the transition; if it fails, the button is not shown. A validator checks input before the move, and a post function does extra work after it.

A company-managed transition, in order

1. 1ConditionThe button shows only if it passes
2. 2ValidatorChecks input, including the transition screen
3. 3Post functionsRun after the move; notifications wait until the end

Workflow triggers move work items on events such as a merged pull request, and every one needs a code repository or development app integration.

Conditions hide the transition, validators block it, post functions follow it.

03 How do statuses work in team-managed spaces?

Each status falls into To do, In progress or Done. New statuses get an Any status transition by default, and they stay off the board until you assign them a column.

Deleting a status also deletes its transitions and their rules, and Jira asks you to move its work items to a valid status.

New team-managed statuses accept moves from any status but are hidden from the board.

04 How do automation flows run and branch?

Every flow starts with a trigger, and actions make the changes. Inside a branch, {{issue}} points to the related work item, while {{triggerIssue}} still reaches the trigger work item.

Branches cannot be nested, and a variable created in one branch is not visible anywhere else. In a company-managed space, managing flows takes the Administer spaces and Browse spaces permissions.

In a branch, {{issue}} is the related work item, not the trigger.

Summary

1. A failed condition hides the transition button.
2. A team-managed space holds up to 100 statuses, and 50 per workflow.
3. Branches cannot be nested and do not share variables.

Sources

1. Configure advanced work item workflows | Atlassian Support
2. Create, edit and delete statuses in team-managed spaces | Jira Cloud | Atlassian Support
3. Use automation steps in a flow | Cloud automation Cloud | Atlassian Support
4. Use workflow triggers for company-managed spaces | Atlassian Support
5. Set up a workflow in a team-managed software space | Jira Cloud | Atlassian Support
6. Branch automation flows to perform actions on related work items | Cloud automation Cloud | Atlassian Support
7. Permissions required to manage automation flows | Cloud automation Cloud | Atlassian Support