Task-Based Rules

Task-based rules are built from the following blocks, or choices. You step through the Rules Wizard, selecting choices at each step, then specifying values for most choices. The rule you build displays as an actual sentence, like the following:
For all active tasks, if current task step is due in 1 day(s), email current task step
events to Assignee(s) and Project Creator. Execute this rule on schedule Daily-early-am.
Rules Wizard Step Choices Notes
Selector: To what assets should the rule apply?
  • All active tasks
All active tasks are the tasks that are neither completed nor canceled. These are the tasks a project manager (and assignee) needs to track. You can create a rule to automatically check when tasks are near due or overdue, and can notify the assignee accordingly.
Condition: What conditions should the rule check?
  • If task is due in a particular number of days and time
  • If task is overdue by a particular number of days and time
  • If current task step is due in a particular number of days and time
  • If current task step is overdue by a particular number of days and time
You can specify whether you are interested in when a task is due or if a task is near due or overdue. WorldServer uses the task step Due Date and Time to determine when a task is due.
Action: What should this rule do?
  • Email task events to project user(s)
  • Email task events to a particular user
  • Email current task step events to project user(s)
  • Email current task step events to a particular user
These actions let you notify the appropriate users about active task status. For example, Email current task step events to project user(s) lets you select one or more of the following to notify about a task event or task step status:
  • Claimant
  • Assignee(s)
  • Task Creator
  • Project Creator
Exception: What exceptions should this rule check?
  • If task is due in a particular number of days and time
  • If task is overdue by a particular number of days and time
  • If current task step is due in a particular number of days and time
  • If current task step is overdue by a particular number of days and time
The exceptions to use as criteria for tasks correspond to the conditions specified.
Execution: When should the rule run?
  • Manually only
  • On a particular schedule
If you choose to run the rule on a schedule, you are prompted to select a recurrence.
Note: Be careful with manual rules. If you have a long running rule—one that may run longer than your session timeout, you can run into timeout issues. You should make sure to run these under a recurrence (even one that starts in just a few minutes) so the rule runs, effectively, in background rather than in your personal session.