You can create dependencies between subprocesses within the same main process. This lets you design workflows where certain subprocesses are blocked until others are completed, ensuring that work progresses in the correct order and dependencies are respected.
Important to Know
Dependencies are configured directly in the process form.
They can only exist within the same main process - cross-process dependencies are not supported.
Dependencies apply only to processes, not programs.
Example: Investor Communication Process
Main Process: Investor Communication
Subprocess | Depends On |
Portfolio Valuation | â |
NAV Review & Sign-Off | Portfolio Valuation |
Investor Reporting | NAV Review & Sign-Off |
Newsletter Drafting | NAV Review & Sign-Off |
Content Review & Compliance Approval | Newsletter Drafting |
Distribution | Content Review & Compliance Approval |
In this setup:
The NAV Review subprocess can only begin after Portfolio Valuation is complete.
Each subsequent subprocess is blocked until its dependency is finished.
Once a preceding subprocess is completed, the next one becomes unblocked, and notifications are sent based on each subprocessâs settings.
Configuration Rules
Subprocesses cannot depend on themselves or form circular dependencies.
All dependency changes are logged in the subprocess history.
Each dependent subprocess can include a notification toggle to alert users when it becomes unblocked.
Behavior
Users cannot perform the following actions on blocked subprocesses:
Change status
Change verification status
When a subprocess is completed:
Dependent subprocesses are unblocked in real time.
If you enable the notification checkbox for a subprocess, the system will automatically send a notification when the subprocess becomes unblocked - that is, once all preceding subprocesses are completed.
Notifications are sent to:
Maker (if set)
Backup maker (if maker missing)
Owner, if neither a maker nor a backup maker are assigned (the owner is defined in the process edit form)
All team members (if owner is a team)
Activation & Deactivation Logic
When you deactivate a subprocess that depends on others, itâs turned off as usual, and its dependencies are removed.
If you deactivate a subprocess that other subprocesses depend on, those subprocesses will become unblocked. Youâll see a warning message before confirming.
When subprocesses are reactivated, their dependencies are automatically restored.
User Interface
Dashboard
Includes a Hide blocked items toggle to quickly filter and show only unblocked subprocesses.
Blocked subprocesses display disabled status controls with tooltips explaining whatâs blocking them.
Main Process Details View
Includes a full Process Flow view for visualising the entire process.
