Seeking clarification on role of Successors

Created on 9 August 2022, over 2 years ago
Updated 12 December 2023, about 1 year ago

Problem/Motivation

It's likely it's terminology used with modellers, but not being familiar with these I am struggling to understand how “Successors” fit in to the flow of creating a model.

Coming from the Rules module, I am used to at the basic level simply having to create a trigger and an action.

Having attempted the same with a test model using this modeller, the action was not triggered by the event (in my test case it was the cancellation of an account).

To get the action to work, I had to add the action as a “Successor” to the cancel user account event.

This caused the action to work, but I don't know why.

It appears that each event, condition, and action can have Successors. It would be very much appreciated if somebody would explain the role of Successors so that I can try to make sense of the model construction process. Thanks

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

💬 Support request
Status

Fixed

Version

1.0

Component

Documentation

Created by

🇬🇧United Kingdom Janner

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • 🇬🇧United Kingdom welly

    Just to clarify this a bit further, I'm new to ECA and also trying to understand successors but possibly in the context of the classic modeller.

    If I understand it correctly, the event, conditions and actions are not a "this first (event), then this (condition) and then this (action)"? but the conditions and actions fieldsets provide conditions and actions for the events created in the events fieldset?

    I originally understood it as you create an event (user logs in) and then you create a condition (user role is admin) and then you create an action (show a message) - but actually the condition and action you actually assign to the event?

  • 🇩🇪Germany jurgenhaas Gottmadingen

    An ECA model can be a chain of actions, that follow an event. With successors, you can link them together, so that you determine, in which order those actions should be executed. And for each of those "links", where an action is a successor of either the initial event or another action, you can optionally attach a condition, so that the successor only gets processed, when that condition returns true.

  • 🇬🇧United Kingdom welly

    That makes sense, thanks very much @jurgenhaas! Appreciate your work on this module, it's a brilliant endeavour!

Production build 0.71.5 2024