Skip to content

Processing sequence

Version v1

Purpose

This model comes with 2 processes, that look similar but do behave differently. They get executed by calling drush eca:trigger:custom_event procorder on the console of the Drupal site.

What the 2 processes do is to set a token value, then overwrite that token with a different value and finally print the value out on screen as a message. However, that's what we expect but not what we get. For the first process (the left one), that's what we get. But the second one seems to have a mistake: it doesn't print 12, instead we get the value 5.

This is because the processing order of succeeding actions is not necessarily what we see on screen - where both processes look the same. Instead, the order depends on the order in which the successors got added to the predecessor. The problem being present is, that BPMN, while it relies on that order, doesn't have any form of indicator that would help us to see that in the visual model.

We have recorded a video which discusses that topic alongside this model and demonstrates how to find out about the order os successors. It then also shows how to fix the order in case it got messed up. You can find that by following this link.

Dependencies

  • module
    • eca_base

Used plugins

Events

Actions

Changelog

v1

Initial version