activiti learning summary 5

1. Multi-instance
   multi-instance execution is divided into two ways, sequential execution and concurrent execution. Sequential execution, such as looping 3 times, first generate one, complete, then generate another, and then complete, until the third instance generates
   concurrent execution, multiple instances are generated at a time, and 3 instances are generated at a time when the task is executed.

Multi- instance process during execution The engine automatically generates the following variables
   nrOfInstances The total number of instances to be generated nrOfActiveInstances The number    of instances that are being
   executed, that is, the number of instances that have not been executed The configured properties are isSequential--whether the number of times the loopCardinality cycle is executed sequentially 2. Timer definition method, the format adopts ISO-8061, cron     1: timerDate: occurs at a certain point in time, "2011-03-11T12:13:14" Occurs at this time and cannot be used cron     2: timeCycle: recurring at a certain interval, "R3/PT10H" loops every 10 hours, looping 3 times     3: timeDuration: how long to wait to occur once, "P10D" 10 days Occurs later, "PT10H" occurs 10 hours later 3. Timer boundary event, which means that a certain task will be executed at a certain time     <boundaryEvent id="boundarytimer1" name="" cancelActivity="













      <timerEventDefinition>
        <timeDuration>PT20S</timeDuration>
      </timerEventDefinition>
    </boundaryEvent>
    cancelActivity: whether to cancel the current task, true cancel
    attachedToRef: current task Id

4. The subprocess subProcess can realize abnormal boundary events and encapsulate some processes In the sub-process, set an exception boundary event on the sub-process boundary. The errorcode of the boundary event needs to be the
same , and the ErrorCode cannot be the number

5. Exception boundary event
    <boundaryEvent id="boundaryerror1" name=" " cancelActivity="true" attachedToRef="subprocess1">
      <errorEventDefinition errorRef="cancelStock"></errorEventDefinition>
    </boundaryEvent>
    errorRef="cancelStock" needs to be consistent with the errorRef of the abnormal end event in the subprocess6

. Calling process (sub-process) This is different from sub-process. Sub-process refers to the department process process in a process definition.
The calling process can directly call another process definition. The calling process is generally used to define some general processes, and other processes can call these defined general processes uniformly
. 7. The timer captures the event in the middle, and when the process executes to the event , wait, and execute according to the set time scheduling mode.