Hi Jon, there is an "executable" field that is only set to true if there are no active predecessors. Are you using this field?
Comment actions
Post
Follow
How to creating a validation rule.
I would like to create a validation rule that prevents a task from becoming executable until it's predecessor has been completed. Can you help me with that?
Please sign in to leave a comment.
3 comments
Date
Votes
I see that the executable field does not become true until the predecessor has been completed. I guess what I'm trying to do is prevent a task from being completed regardless of if is executable or not. I'd like it to be totally dependent on the predecessor being completed.
Comment actions
You would create a validation rule on Tasks where the criteria is $Executable = False && $Status = 'Complete'
That means that is a task is not executable and someone tries to market it as complete, it will trigger a validation message. If you would like a step-by-step walkthrough I would recommend hopping on one of our Q&A webinars (http://webinars.clarizen.com)
Comment actions