About document workflows

The Documents section on a project is where you find all documents pertaining to the project. This makes sharing and collaborating on content (eg. project plans, requirements, specifications, etc.) easy to do directly in Upchain. Supporting documentation may also be added to an item in the Item Details Pane > Documents tab.

A Document workflow is used to move a document through each lifecycle status, from a Draft state, to In Review as it awaits the approval of a project manager, and finally to Published once approved. This is the default document workflow, however you can configure your own workflow that suits your business requirements.

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:

• What is your current process to publish a document?
• Do you need separate workflows for different document types?
• Who will be responsible for approving a document before it is published?
• Are there any additional actions that should occur at each step? (notifications, status updates, etc).

For example, the steps might be:

1. Document creator assigns the document to their team lead to review.
2. Team lead approves the document.
3. Team lead assigns the document to the PM for final approval before publishing.
4. PM reviews the document and approves it.
5. The document is published.

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 preceding example, it might be the case that the designer does not agree with the markup sent to them and assigns it back to the work order creator to change or discard. 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.