Employee projects by their tasks
The "Employee projects by their tasks" robot returns to a business process the Bitrix24 (Alaio) projects where an employee has tasks: an array of project IDs, an array of names, the task count per project, the total task count and a Found Y/N flag. The role in the task is selectable: assignee, participant, observer or creator; completed tasks are included by a flag.
The standard Bitrix24 (Alaio) business process designer cannot tell which projects an employee is busy with. The robot answers through tasks: it selects the employee's tasks in the given role (assignee, participant, observer, creator), keeps only those bound to a project and groups them by project. By default only unfinished tasks count; the Include completed tasks flag adds closed ones. The output is an array of project IDs, an array of names, the task count per project (in the same order), the number of projects, the total task count and a Found Y/N flag. Projects are sorted by task count descending, so the first project is where the employee is loaded most. Unlike the "Get employee projects" robot, this one works without the "Workgroups" permission and shows actual workload rather than formal membership. Typical scenarios: check an employee's project load before assigning a task; collect projects with open tasks when an employee leaves; show a manager the task distribution of a subordinate in a weekly report. The robot scans up to 1000 tasks per run.
What input parameters does the robot accept?
| Parameter | Type | Required? | Default |
|---|---|---|---|
| Employee | user | yes | |
| Role in the task | select | — | responsible |
| Include completed tasks | bool | — | N |
What does the robot return?
| Parameter | Type |
|---|---|
| Project IDs | int |
| Project names | string |
| Task count per project | int |
| Number of projects | int |
| Total tasks in projects | int |
| Found (Y/N) | string |
| First project ID | int |
| First project name | string |
What errors can the robot return?
The robot writes these messages to the business process log when it cannot complete a step. The text tells you what to fix in the settings or the data.
- Error: employee is not set
- Error accessing tasks
Scenario: picking an assignee
- A deal moves to the Implementation stage
- The robot counts the projects and open tasks of the candidate assignee
- When the number of projects exceeds three the process assigns the task to another employee