In general, the rules you set are executed in the order you specified them - so you need to take that into consideration.
Business Rule Evaluation Order
Are WFRs evaluated in the order Work Item rules, Project rules, Task rules? We have a task rule that sets the value of a custom project field based on a task field value. I have added a project rule that checks whether the custom project field changes. The project rule rule is not detecting when the custom project field value changes. I am wondering if the project rule is running before the task rule. What I suspect is the project rule runs, checks the project field, and doesn't see a change; THEN the task rule runs, and makes the change.
Please sign in to leave a comment.
Workflow rules are designed to be real-time so there are some limitations. A workflow rule that checks for changes will only run if there is a direct change as opposed to an indirect change, meaning if the field is changed by another rule it won't trigger the rule (this is an indirect change). If you update a task and that rolls up to the project, that is still considered an indirect change. "ischanged()" is looking for a user directly making a change to that field. This is in order to prevent infinite loops and other logic issues that can dramatically impact performance.
You may want to consider running a scheduled workflow rule instead to monitor the project-level field.
@Josh That explains it. And thanks for the alternate solution.