The predecessor is really used for scheduling, but it is not a "hard" dependency meaning that t2 can still be completed even if t1 is not complete. In order to make these hard dependencies, you would have to create a small validation rule that would prevent tasks from being marked as complete if there are any active predecessors. This is something that can either be done with your CSM or demonstrated on an advanced Q&A forum ( http://www.clarizen.com/live-demo.html)
I would like to know how exactly a predecessor works? I would suppose that if t1 is a predecessor of t2 then you can't complete t2 until t1 is completed. This is not what is happening; I can complete each task individually.
How can you limit this?
Please sign in to leave a comment.
Ok. I have already registered to the advanced Q&A forum. Thank you