Share

About task workflows

A Task is a piece of work that a user is meant to complete. In Upchain, you can configure custom task types to provide more granularity to your business needs that align with your existing business processes. Creating task workflows that match up with each task type allows you to clearly define the specific steps the task assignee is meant to follow to complete the task.

Before you start

Before you start modeling workflows in Upchain, we recommend that you already have a process in mind. Mapping this process out in a diagram application gives you a solid base from which to start.

Things to consider include, but are not limited to:

  • Who might create a task?
  • Who will be responsible for completing the task?
  • What are different scenarios that would warrant a task (eg. initial project scoping, filling out requirements, marking requirements as complete, etc.)
  • What are the criteria needed to mark a task as complete?
  • What would be some reasons why a task could not be completed or need to be restarted?
  • Are there any additional actions that should occur at each step? (status updates, etc).

For example, you may have created a custom task type entitled Requirements Definition. Associated to this, you need a workflow to track the progress of this task. The steps might be:

  1. Create the task.
  2. Assign it to the lead mechanical designer.
  3. Review customer requirements.
  4. Break requirements into manageable components.
  5. Fill out the requirements page for the project.
  6. Assign the task to the PM to review.
  7. PM either approves the requirements or sends it back to the lead mechanical designer with comments on what needs fixing.
  8. Lead addresses comments and resubmits for review.
  9. PM approves and the task is complete.

Make sure to include all the steps in your ideal process (happy path) as well as any possible roadblocks (exception path) that may occur. In the example above, it might be the case that the PM does not understand some of the requirements as written and assigns it back to the lead designer to clarify. You should ensure this process is built into your workflow.

To help you in your planning, read through the list of available primitives to get a sense of what is possible.

Was this information helpful?