e.g.Send event task. This task can be used to send out an event to the event registry with a JMS, Kafka or RabbitMQ destination. In addition, it’s also possible to wait for a response of the outgoing event as
Support for Event definitions which define the event payload, the channel definition to use, and the optional correlation parameters of an incoming or outgoing event. The BPMN start event, boundary event or send task or the CMMN Case element or event listener are linked to an Event definition ...
Now go to the case instance. You'll see that a new task has been created. When going into its details, you can see the event data has correctly been passed through the internal channel and is now displayed in the form:Kafka Implementation ...
Map<String, Object> variables = runtimeService.getVariables(executionId); executionId流程执行ID, 这个id也在待办的task上获取,也就是说想要拿流程变量还需要调用待办列表,而且必须是这个流程没走完,拿的是当前的executionId,走过的节点的executionId是获取不到的。 获取流程历史节点 List<HistoricActivityInstance>...
like with using a HTTP task or send an event with the event registry task. The external worker task can be used to pull work from the BPMN and CMMN engine. This means that a service written in any language can pull for open external worker tasks over a dedicated external worker REST API...
This is a new paradigm that is available to execute service logic outside of the BPMN and CMMN engine. Until this release this could be done by pushing work to another service, like with using a HTTP task or send an event with the event registry task. The external worker task can be ...