What are the basic events of Activiti

What is the basic event of Activiti? I believe many inexperienced people are at a loss about it. Therefore, this article summarizes the causes and solutions of the problem. Through this article, I hope you can solve this problem.

The basic events of this article activti and the previous introduction to Activiti Learning (5)-basic components complement each other. The basic component is the basic component when activiti draws the flow chart, while the basic events exist in different builds and play a role.

Although the basic event I mentioned sounds similar to the name of the basic component, there is still an essential difference: the basic event is more functional, so the basic event is included in various basic artifacts; the basic component is more about the location of an element in the drawing in the flowchart.

Basic events are mainly divided into: throwing events and capturing events.

1. Timer event

There are three definitions of timed events: timeDate (specify a specific time for a trigger), timeDuration (specify how long it will be triggered), and timeCycle (specify how often it is triggered), where timeCycle can use cron expressions.

TimeEventDefinition can be included in a start event, an intermediate capture event, or a boundary event.

two。 Error event

Error events can be included in start events, boundary events, or end events.

Error events mainly deal with running all kinds of thrown errors. You need to declare the error element first, and then bind the error element to the errorEventDefination by binding id. The program can throw BPMNerror and set the thrown error code to match the error errorCode to match the error element in the xml, thus triggering the error event. If errorcode is not set, all errors can be caught.

3. Signal event

Can be used in boundary events, intermediate capture time, and intermediate throw events.

The form of writing is similar to that of error events. However, it is important to note that the signal event must define the name attribute.

4. Message event

Can be used in start events and intermediate capture events.

The written form is still similar to the error event signal time.

Both the signal event and the message time send a message to prompt the completion node, the difference is that the signal event is similar to a broadcast, and everyone can accept the signal, but the message time is similar to a private message, and only a single node can accept the information.

5. Cancel event

The cancellation event definition can be used in the transaction subprocess model, and the cancellation event can be used in boundary events and end events.

When you cancel the boundary event, the catching event, which waits for it to be triggered, and the throwing event when you cancel the end event.

6. Compensation event

The compensation mechanism is mainly used for fallback processing for events that have been completed successfully. Compensation definitions can be nested within start events, intermediate catching events, intermediate throwing events, and end events. / / todo

7. Other events

In addition to the common events mentioned above, some other events are defined in the bpmn2.0 specification: conditional event definition, upgrade event definition, connection event definition, and termination event definition.

After reading the above, have you mastered the basic events of Activiti? If you want to learn more skills or want to know more about it, you are welcome to follow the industry information channel, thank you for reading!