Delete (on a step's details, next to Edit) moves the step to Deleted steps instead of erasing it. The step disappears from the job and the Designer and never runs again, but its run history is kept, so past runs still show it by name.
What deleting does
- The step's Runs After links, gates and alerts are removed with it. Anything that ran after the step simply no longer waits for it.
- A step that was globally managed asks first: deleting it detaches it from the global definition.
- The step's name and key can be reused straight away.
Deleting a pool
A pool with steps in it asks what to do with them:
| Choice | Result |
|---|---|
| Yes -- delete the pool and its steps | Everything in the pool goes to Deleted steps. |
| No -- delete only the pool | The steps stay in the job as ordinary steps. Whatever ran before the pool now runs before each of those steps, and whatever ran after the pool now waits for all of them -- the flow stays as it was, with the pool's grouping removed. |
| Cancel | Nothing changes. |
Getting a step back
Click Deleted steps... above New Step, pick one or more, and choose:
- Restore -- brings the step back into the job. Its old links, gates and alerts are not restored, so re-wire it under Runs After. If another step has taken its key in the meantime, the restored step gets a new key. A step whose pool is still deleted comes back as an ordinary step; restore the pool first (the dialog does this when you pick both) to keep it inside.
- Delete permanently -- removes the step and its run history for good. This can't be undone.
See also: Glossary for related terms.