Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: minor spelling edits

...

Default tasks can be included in each step of the workflow.  Default tasks are assigned to "roles" (participant types), because you don't know ahead of time who will be involved in the actual actions).

When users move to a step in a live Action the task will be automatically assigned to the person playing the specified role in that particular action.

...

Due dates for default tasks need to be set relative to real dates in the actions.  Because you don't know this ahead of time you need to set the due dates a certain number of days before or after either the date that the step was reached in the actual action or relative to a custom date defined for that action type. We'll get to custom data latelater, so for this tutorial you will be setting the due dates relative to the step change date.

...

It's always a good idea to check this box because it ensures that the task is completed before allowing the user to move to the next step.

The Then click Submit and close the tab to dismiss the step editor.

...

Open your action (if you've created more that than one action type make sure it's the same action type where you added the default task).

...

On the step change screen you see you your default task.  

Info
titleGetting a warning/error message?

Tasks can only be assigned to people with a login to the system (otherwise they would have no way of seeing them). So make sure you have added a valid user to the role the task will be assigned to (you're probably the only user at this stage so add yourself to the role to be sure).

...