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
In order to ensure the efficiency of the Services, automatic protection mechanisms, hereinafter referred to as Protection Policy, are defined to prevent misuse of the Services.
- Process Instance: running or completed process model; a process model can give rise to multiple Process Instances.
- Continuous Execution Time Period: process execution interval in which no asynchronous tasks are executed.
- Maximum Continuous Execution Time Period: Continuous execution time period equal to 5 minutes.
- Standard Multiple Cardinality Tasks: same task executed sequentially a certain number of times defined by process logic.
-Executing Process Instance: uncompleted process instance that is executing orchestration operations or rules, when a Process Instance invokes an asynchronous operation (service task, human task, call activity) it waits for the operation to complete and goes into a state called "idle" distinct from the execution state.
-Subprocess: Process Inst ance created by another Process Instance.
- Rest API: interface for programmatic use of Services from external applications.
- Platform API: interface for programmatic use of Services from within the PaaS Jamio openwork.
3.1. Maximum number of errors generated: 1000 per Process Instance in a Maximum Continuous Run Time. The Process Instance is suspended because it has generated too many errors in a defined time interval.
3.2. Maximum Number of Operations in a Maximum Continuous Execution Time Period: 5000 per Process Instance in a Maximum Continuous Execution Time Period. TheProcess Instance is suspended because it has performed too many operations in a defined interval of time. Operations performed by any subprocesses invoked by the ProcessInstance are also counted.
3.3. Maximum number of executable iterations for a task with standard multiple cardinality: 1000 iterations of the same task in a Maximum continuous execution time period. Process Instance is suspended for a potential infinite loop of aStandard Multiple Cardinality Activity.
3.4. Maximum Total Number of Operations: 10000 total operations per Process Instance. TheProcess Instance is suspended because it has performed too many operations. Operations performed by any subprocesses invoked by the ProcessInstance are also counted.
3.5. Maximum total number of operations: 10000 total operations per Process Instance. TheProcess Inst ance is suspended because it has performed too many operations. Operations performed by any subprocesses invoked by the ProcessInstance are also counted.
3.6. Maximum number of running Process Instances: 20 concurrent instances, including Subprocesses. If an attempt is made to create a Process Instance from Rest API, Platform API, UI, Synchronous Custom Action and this is not possible due to exceeding the maximum number of running Process Instances, an error is returned. If the PaaS Jamio openwork tries to create a Process Instance, upon receiving an event, or a Subprocess and this is not possible due to exceeding the maximum number of running Process Inst ances, theProcess Instance or Subprocess will be created as soon as possible.
For more information see the basic knowladge of Jamio openwork(http://instruments.jamio.com/knowledge_base/).
Rev 1.5 dated 06/21/2021
jamio.com