All Collections
Working in Daymi
Process Templates 📋
Understanding the difference between Templates and Regular Processes
Understanding the difference between Templates and Regular Processes
Kestutis Vansavicius avatar
Written by Kestutis Vansavicius
Updated over a week ago

If you are new to our platform, you might be wondering about the difference between templates and regular processes. This article will explain the key differences between them and how they are used in our system.

Firstly, active processes (Main Processes & their underlying Subprocesses) are those that have already been created and are visible on your dashboard. You can begin working on these processes, track their progress, and mark them as completed.

Templates (Main Process Templates & their underlying subprocesses) are like blueprints for creating new processes. They are not yet on the dashboard, but rather a starting point to create new processes with the same structure and steps as the original template. Think of them as a pre-made recipe that you can reuse multiple times and deploy to the dashboard when needed.

For instance, if you have a complex ad-hoc project that needs to be repeated multiple times, you can create a template of the process and reuse it whenever needed. This saves you the time and effort of creating the process from scratch each time.

For a recurring daily process that you only need to set up once and use throughout its lifecycle, a template may not be necessary.

💡 We have separate pages for Main Process and Subprocess Templates, but they are connected to each other. Main process templates include various subprocess templates, and each subprocess template is associated with a particular main process template. Same with the regular processes and their menu options. This layout makes it easier for you to work with the lists, particularly if you only need to view main processes.

Main Processes/Subprocesses

Main Process Templates/Subprocess Templates

Already created and visible on dashboard

Not on dashboard, deployed when needed for creating new processes/projects

Can be worked on, tracked and marked as completed

Act as blueprints for new processes/projects

Consist of main processes and underlying subprocesses

Consist of main process templates and underlying subprocess templates

Can be inactivated

Cannot be inactivated, but can be deleted

Did this answer your question?