Stories of digital innovation by no-code
Learn about channel program opportunities
Join the Network
Leverage the resources of Jamio designers
We collaborate with universities
Jamio openwork world news
Keep up on the world of no-code and digitization
The periodical on no-code and BPM
Check out our guides full of clarification for digitization
With Jamio you can build processes that become work organizers, being able to distribute a large number of tasks to many people in one or more organizations!
The business cases that can be implemented are unlimited and range from the simple distribution of tasks within authorization processes, to processing tasks related to, for example,job order progress, machine design, human resource management....
Managing tasks with a process approach makes it possible to never forget that a certain task needs to be executed, is in someone's charge, and has maximum execution times; especially when a process procedure has a long duration or when there are numerous procedures of the same type running.
The Task in Jamio, in fact, is an object under the government and control of a process and remains so until it is completed.
During the modeling of a process-Design Time-it 's possible to configure objects called Human Tasks: the user activities that allow "people" to interact with the process. Each Task can be customized by defining its metadata. More than one Task can be customized in a process, for example, one to manage the collection of information that will be used later, others to show documentation, gather opinions and approvals, etc. Deadlines, escalations, completion rules, executors and other features can be set for each task.
One of the strengths of Jamio's Task Manager is its ability to be abstract in defining executors. In fact, during modeling, executors can be defined with organizational rules; these rules are then resolved at Run Time when a process is executing: this allows the organization not to be plastered!!!
An example
If you indicate a "person" -Mario Rossi-as the executor of a task, the risk of making the solution rigid would be very high because only and exclusively Mario Rossi could then perform that task.
If, on the other hand, you indicate that the Executors of a task are - the users belonging to the Quality Manager Group- or - the Organizational Position is Production Manager- or - the User belongs to the Logistics Department-. and/or any complex combination of many rules, you manage to achieve great flexibility and independence from people who may over time change roles and/or be on vacation and/or change companies...,
Processes modeled in this way will always work as long as the organizational structure remains consistent with the rules set.
When a process is running -RunTime- on a Jamio workspace and crosses a Human Task , automatic execution along that branch stops and a Task is assigned to all users who meet the organizational rule described for Task Executors. The process then resumes its automatic execution when the Task is completed by the executor and/or through configurable automations. The executor can take charge of the task by accessing it from a personal Task List.
Completion of a Task and the consequent progress of the process along that branch can be affected either by information entered by the executing user or by external events indicated at design time in the completion conditions.
Examples