Deleting an operation or an occurrence
Unlike the behavior for normal dependencies, when you delete an operation or an occurrence containing operations referenced in a condition as conditional predecessor or conditional successor jobs, the scheduler does not redefine the rule criteria to avoid workflow propagation tree from breaking.
This is how the scheduler manages condition dependencies for which
the deleted operation is the conditional predecessor:
- If the condition status has already been evaluated T (True) or F (False)
- All condition dependencies are kept and the condition dependencies whose predecessor is the deleted job are marked as removed.
- If the condition status is undefined (some condition dependencies have not been evaluated yet)
-
- Evaluated condition dependencies whose predecessor is the deleted job are marked as removed.
- Non-evaluated condition dependencies whose predecessor is the deleted job are deleted from the condition.