Named Instance : Predecessor dependencies with named instance

In the case of a design that works with a normal schedule and predecessor named instance schedule, the named instance predecessor MUST BE fill in the normal schedule. It is complicated to maintain the predecessor strategy between the schedules.

When you add a new instance in named instance (SKD2_INST), you MUST add the predecessor dependency in the normal schedule (SKD_TEST).

When you delete an instance in named instance (SKD2_INST), you MUST delete the predecessor dependency in the normal schedule (SKD_TEST).

Let's go to a better way :

A better way to keep the dependency with all named instance without filling each time a new instance would be to have an option like "*" in the listbox "Instance Name" of Edit Dependency window.