Automatic conditional dependencies resolution

When you add new occurrences to the current plan, the scheduler applies some criteria to identify potential conditional successors:

1. Searches, among all the potential conditional successors defined in the database, for those existing in the plan.
2. Selects the closest following conditional predecessor.
3. Determines whether to add a new condition dependency to the existing condition or to create a new condition ad hoc as follows:
   • If the condition dependency referring to the new predecessor occurrence is not present in the plan for the conditional successor, a new COND ID is created.
   • If the condition dependency referring to the new predecessor occurrence is already present in the plan for the conditional successor, then:
     • If that condition dependency has not yet been filled in the plan, the condition dependency is added to the existing COND ID.
     • If the condition dependency has already been filled in the plan, then a new condition containing that condition dependency is created and marked as a clone. A different COND ID is generated, but the original one is also saved and displayed in the description of the cloned condition. The new COND ID is the first available number in the range from 1 to 999.