Deleting Actions removes them from the Project, along with every step that calls them in Scenarios and other Actions. Before anything is removed, ACCELQ checks each selected Action and shows which ones can be deleted, which cannot, and what deleting the rest would affect. You decide exactly which Actions go and which consequences you accept.
How ACCELQ evaluates a delete
Every selected Action lands in one of three groups. The group decides whether the Action can be deleted and whether it is included by default.
| Group | What it means | In the delete |
|---|---|---|
| Cannot be deleted | Another user has it locked, or it is published to other Projects | Left out. Shown first, on a separate screen |
| Ready to delete | Not referenced anywhere | Included by default |
| Has an impact | Referenced in Scenarios, other Actions or scheduled jobs | Left out until you include it |
When no selected Action is blocked, the blocker screen is skipped and the delete opens directly on the review screen.
Actions that cannot be deleted
Some Actions cannot be deleted right now because deleting them would override someone else's work or break other Projects. These Actions are listed on a separate screen with the reason for each. Select Acknowledge and continue to go on with the rest of your selection. The blocked Actions stay untouched, and you can delete them later once the reason is resolved.
If every selected Action is blocked, the screen offers only Close.
Checked out by another user
Another user is editing the Action. Deleting it would discard their changes. Ask them to check it in, then delete it.
Actions you have checked out yourself are not blocked.
Published to other Projects
The Action is shared with other Projects, and deleting it would break the Scenarios there. Unpublish the Action first, then delete it.
Used in a Scenario checked out by another user
Deleting the Action removes its step from every Scenario that uses it. If one of those Scenarios is checked out by someone else, that change would collide with their work. Ask them to check the Scenario in, then delete the Action.
Actions ready to delete
An Action is ready to delete when no Scenario, Action or scheduled job references it. Deleting it changes nothing else in the Project, so these Actions are checked by default. Uncheck any you want to keep.
Actions with an impact
An Action has an impact when Scenarios, other Actions or scheduled jobs reference it. Deleting it changes those too, so these Actions are unchecked by default. Nothing in this group is deleted unless you check it.
Each row shows a reference summary, such as Referenced in 9 Scenarios; 13 Actions. Select the summary to see exactly which Scenarios, Actions and jobs are involved. Check Actions one at a time, or use the checkbox in the group header to include the whole group.
Once you include an Action with an impact, a note above the buttons totals what the delete will modify across everything you checked. A Scenario or job referenced by several of the checked Actions is counted once.
What happens to the references
- Scenarios: the step that calls the deleted Action is removed.
- Other Actions: the step that calls the deleted Action is removed.
- Scheduled jobs: jobs that run the affected Scenarios use the updated Scenarios from their next run.
Restoring a deleted Action from the recycle bin does not restore the removed steps. Review the reference list before you include an Action with an impact.
Example: retiring a branch locator flow
A retail banking team has redesigned its branch locator and is cleaning up Actions from the old flow. They select four Actions and delete them together.
| Action | What ACCELQ finds | Group | Team's decision |
|---|---|---|---|
| Update alert preferences | Checked out by Priya Mehta | Cannot be deleted | Left for later |
| Download monthly statement | No references | Ready to delete | Deleted |
| Find nearby branches | Referenced in 9 Scenarios and 13 Actions | Has an impact | Checked and deleted |
| Verify bill total | Referenced in 1 Scenario, 2 Actions and 2 scheduled jobs | Has an impact | Left unchecked |
The blocker screen opens first and lists Update alert preferences. The team continues, and the review screen opens with one Action checked: Delete 1 Action.
They expand Find nearby branches and confirm its 9 Scenarios all belong to the old branch locator flow. They check it, and the note above the buttons now totals 9 Scenarios and 13 Actions to be modified. Verify bill total still feeds the nightly billing regression job, so they leave it unchecked.
They select Delete 2 Actions. Two Actions are deleted, the steps calling Find nearby branches are removed, and the other two Actions stay in the Project unchanged.
Things to keep in mind
- The delete button always shows how many Actions will be deleted, and updates as you check or uncheck rows.
- Blocked and unchecked Actions are skipped, not failed. Everything you checked is deleted in one step.
- Back on the review screen returns to the blocker list without losing your selections.
- If nothing is checked, the button reads Nothing to delete and stays disabled.
Comments
0 comments
Please sign in to leave a comment.