How to use resources for multi-processing of a function

You can specify that a specific human resource is used for repeated execution of a variety of sequential functions, even if the human resource is requested elsewhere in the context of the general resource allocation strategy. If you activate the Commit resource attribute of either the carries out or is used by connection (Simulation attribute type group), the human resource is committed to carrying out various sequential functions repeatedly. The resource allocation strategy specified is retained until you change it by entering a different value for the Commit resource attribute. If the control flow branches at a rule, the two paths inherit the resource commitment that was predefined before the rule was passed through. Within the paths, the resource allocation can be changed independently of other paths.

The human resource is released as soon as a function occurs to which the resource has not been committed. Thus, the resource is committed as long as functions to which the resource it is allocated succeed one another directly. Events are not taken into account. The resource may also be released for joining AND or OR rules. This may be due to any of the following:

If an additive resource has been allocated to a function and would have to wait for another resource, it is released to be able to carry out other functions. After a join, the value of the resource's Commit resource attribute is enabled if at least one of the incoming process folders has an active value. If all values are disabled, the values of the Commit resource attribute are disabled.

If a process folder reaches a joining XOR rule and is forwarded, the resource remains committed if it was previously committed. If the process folder is not forwarded, the resource is released. The resource allocation strategies of committing resources (connection attribute) and of assigning priorities (human resources attribute) may be contradictory. In this case, the commitment of resources takes precedence.