We are starting to put Projects aspects of the PM solution to work. In trying to make things work in Projects ASAP - help in modifying the Activity2 process from Jon Hodge ; thank you Jon - once the schedule is late - that is latest start date is past - it then seems that the rules about predecessors is ignored. What I see, for example, is that in a project if Activity # 6 is a successor to Activity # 4, once the latest start date for Activity #4 is past, when the scheduling Action is done, Activity #6 is activated even if Actitivy #4 is NOT complete.
Is there a way to keep that predecessor/successor scheduling rules in force even when the 'dates' involved in the critical path method try to force activation? Ours is a project where "Activity #6" really can't get started until #4 is done and having it activated early would cause team members to be notified before they can do anything about it.
I know we are a couple releases behind and this may have been solved, but I can't seem to find anything on the topic in our install of Innovator or on the fora on the web-site.
Thanks in advance.