Global Templates
Required Access Level
Super Admin
The Global Templates module allows the Super Admin to configure elements that will be shared and reused by all Tenants across the platform.
This ensures standardization and scalability of the system. By updating a global template, changes are reflected in corresponding processes across all environments.
Global Elements
The platform currently supports the following elements at the global level:
1. Global Process Definitions
BPMN processes and CMMN cases that do not belong to a specific tenant. These process models serve as templates and can be instantiated within the context of any tenant.
TIP
When creating a new global template, uploading an XML file (.bpmn or .cmmn) is optional. If no file is provided, the platform automatically generates a valid default schema based on the selected type.
2. Global Document Types
For forms and processes that require document uploads, you can create global Document Types (e.g., "ID Card", "Proof of Address", "Service Contract"). When managing document types in this area:
- The system binds the type to the global process.
- The Document Type becomes available for forms using that template.
3. Global Attachments
Document templates (physical files, contract templates, and reports) tied to global processes are not bound to a tenantId. Instead, the system uses an is_global flag and physically stores the files in the global/ folder in the storage provider (S3, local disk, etc.). This ensures isolation and prevents data leakage from tenants to public directories.
4. Global Variables and Forms
The variables configured in the Global Templates context form the baseline data vocabulary for forms (e.g., SmartDocs and FlowableForms) used across the platform for a specific process.
5. Global Process Documentation
Every global template carries its own Markdown documentation — the text that explains the process to whoever will operate it. It is written here, in the Documentation tab, with a Write | Preview editor.
Every tenant subscribed to the template reads that same text in the Documentation tab of the definition, without being able to edit it, under a banner naming the global template as its source. It is the same principle as the other global elements: the tenant inherits, it does not fork. Changing the text here reaches every subscriber at once, with no need to republish the process.
Subscribing a tenant to a template
A global template is a package: besides the BPMN/CMMN, it carries decision tables (DMN), forms, roles and documentation. Subscribing a tenant installs the whole package into its environment.
The install is all or nothing
If any linked decision table cannot be deployed — invalid XML, duplicate key, wrong hit policy — the subscription is refused and the error message names every table that did not make it. No subscription is recorded: the tenant does not show up as subscribed to that template version.
That is deliberate. Previously the subscription answered success and showed the tenant on the template version even though the decision table was not in the engine — and the failure only surfaced weeks later, when the first instance reached the business rule task. Fix the DMN in the template and subscribe the tenant again.
When the subscription is accepted, the subscriptions list shows the deployed version, and that version stands for the complete package.
How to Manage
- Navigate to Global (Super Admin) → Global Templates in the sidebar.
- Select the desired Process.
- Use the tabs to manage:
- General: Base process definitions.
- BPMN/CMMN: Model diagram viewer (if applicable).
- Document Types: Create, edit, activate, or suspend document types required for this process.
- Variables: Define the data fields and expected types for global forms.
- Documentation: Write, in Markdown, the text every subscribed tenant will read about this process.
TIP
Only the Super Admin profile can manage global resources — the sidebar's Global (Super Admin) group does not exist for anyone else. Users with the Admin (tenant) profile only manage their local processes, through the Modeling → Process Catalog menu.