User guide
Quick Start Guide
Dashboard
Overviews
Case detail (Caseoverview)
Case - event
Tasks
Case notes
Documents
User settings
Favorites
Table component
FAQ
Administrator Guide
Platform guide
Administration
Crons
Authentication and Synchronization
Mobile App Setup for Your Environment
Scheme
Dynamic tables
Archiving
Scripts
Service console
Scheduled Tasks
HR Agenda
Sequences
CSP Headers
Logs
Access Token Settings & Session Expiration
Template
Roles
Planning
Users
Organizational structure
Events
Translations
AXIOS API
Calculations & Functions
Integrations
TAS Forms
TAS Forms
Activating the module on the environment
TAS Forms - secret creation guide for Docker Swarm
Advanced Features & Tips
Partners
Product
Business Changelog
Technical Changelog
Version Upgrade Guide
Upgrading to 5.9
Upgrading to 5.3
Dynamic conditions migration
PDF printing adjustment
Editing Task Description vs Task Instructions
Transpiling forEach to a for loop
Rendering HTML on Caseoverview
Upgrading to 5.7
Lodash upgrade v4.17.x (>v5.5)
Main changes and deprecated features (v5.3 > v5.7)
Using validation functions
Differences between TAS4 and TAS5 - a complete overview
Best Practices for Upgrading from v4 to v5
Technical details
News / Important information
- All Categories /
- Administrator Guide
- Platform guide
- Template
- Tasks /
- Multi-instance
Multi-instance
In the Team assistant platform, a Multi-instance process refers to a feature that allows a task or sub-process to be executed multiple times, either in parallel or sequentially, for different inputs. This is useful when a process needs to dynamically handle multiple items, such as:
- Approval by multiple users – The task is assigned to several approvers, and each must provide input before the process can continue.
- Processing multiple items – A sub-process is triggered for each item in a list (e.g., generating invoices for multiple orders).
- Parallel workflows – The same task is assigned to different users or departments simultaneously, with each working independently.
Key Platform Rules:
- Tasks support multiple instances – This means the same task can be executed multiple times for different users or data inputs.
- Variables must be explicitly marked as "Multi-instance" – Not all variables automatically function in a Multi-instance mode. Variables must be explicitly enabled for Multi-instance tasks so that each instance can process its own data.
Example of a Multi-instance Task:
Imagine a purchase approval process where a request must be reviewed by multiple department heads.
- A purchase request is submitted along with a list of departments that need to approve it.
- A Multi-instance approval task is created, generating a separate approval task for each department head.
- Each approver receives their own task instance and can independently approve or reject it.
- Once all tasks are completed, the process moves forward (e.g., the purchase is finalized or denied based on the responses).
Updated
by Anna Gernát