Dependent Steps and Step Permissions - Using eziTask

Now that you understand how to create steps and assign a step to an employee, here are some pointers on some of the more advanced behaviors of steps and step permissions:

Dependent Steps

We treat steps in eziTask as “dependent steps” - this means that we allow a step to be checked off only if all steps that come before it are also checked off. In real life, with most tasks, before a later step can even be started, earlier steps need to be completed first. Sometimes multiple steps can be done in parallel, but to simplify the user experience in eziTask, the rule is that a step can only be completed once all previous steps are completed. For your team’s convenience, once the step assignee for the previous step has checked off the step as completed, we will send an automatic notification to the step assignee for the immediate next step that his/her step can be started. This cascades and continues all the way to the last step. Once the last step is completed, the whole task is automatically set to be in finished state, and the checkbox becomes green.

Step Permissions

Finishing steps is done in the same way as finishing a task. Simply click the checkbox to the left of the step and it will turn green (assuming that you permission to complete it). If you’ve created the task, then you will always have permission to complete any of the steps within the task. If you’re an assignee to a step, then you’ll be able to complete that step. If you’re an assignee to the task but not to the step, you won’t be able to complete the step. However, a special case is where the step has no assignee, in which case the step is available to any of the task assignees to complete.