Overview
The Workflows feature in the Control Center workspace allows users to design and manage custom processes for your organization.
A workflow is a sequence of connected nodes (steps) that can be configured to define how, when, under what conditions it runs, and which path(s) the process should follow. These can be:
- Tasks: System or user-assigned tasks that can be managed by the assigned users in Neostella.
Also, there are other types of steps:
- Rules: It is a logical step with set conditions; according to the conditions met, a decision defines the path to be followed. Depending on its position within the workflow, it can be a Starting Rule or a Rule.
- Starting Rule: It is the workflow’s entry point: it listens for a trigger, checks conditions, starts a workflow if met, and activates the next step.
- Rule: It is an intermediate decision step that evaluates the workflow conditions accordingly.
- Delays: It pauses a step execution for a specified period or until a specific condition is met. It allows workflows to wait before continuing to the next step.
Something important is that Workflows are always linked to a specific System Context in Neostella (and its related Objects), meaning a workflow can run a record corresponding to an Object.
For Example:
If the Object Project has related Objects, such as Settlement, Document, Contact, etc, these Objects can be used.
Key Characteristics
- A Workflow always has a starting point that dictates when this process is started, but can have multiple possible endpoints depending on the inputs received at each rule.
- After the starting point, you can design your workflow connecting Nodes or Steps (Task, Automation, nested Workflows, Rules and Delays).
- Workflows are created as Templates, but once applied to a specific record of the Object, it is created a Workflow record.