https://www.lakedrops.com

Event Condition Action

Unleash all Drupal features: how ambitious site builders take it to the next level with ECA and BPMN

DrupalCon Europe 2024
go.lakedrops.com/eca-barcelona-2024

Jürgen Haas

26. September 2024

About myself

Member on drupal.org for 17+ years
Maintainer of ~100 modules

Find me online:
go.lakedrops.com/jurgenhaas


Track Lead Privacy & Compliance


Co-founder and Managing Director

Agenda

  1. ECA Introduction
  2. ECA is for every Drupal site
  3. Use Case 1: Large Intranet
  4. Use Case 2: Booking System
  5. Conclusion
  6. Q&A

go.lakedrops.com/eca-barcelona-2024

ECA Introduction

ECA is the no-code solution that empowers you to orchestrate your Drupal site.

ECA is a powerful, versatile, and user-friendly rules engine for Drupal. The core module is a processor that validates and executes event-condition-action plugins. Integrated with the graphical user interface BPMN.iO, ECA is a robust system for building conditionally triggered action sets.

Started in July 2021

1.0.0 published in July 2022

Steady growth in user statistics
currently ~5.500 sites

2.0.0 published in June 2024
currently at 2.0.5

Dependencies

Just 1: Drupal Core

Sub-modules

  • access
  • base
  • cache
  • config
  • content
  • endpoint
  • file
  • form

  • language
  • log
  • migrate
  • misc
  • queue
  • render
  • user
  • views
  • workflow

Extra modules

There are 2 extra sub-modules:

UI

Can be turned off on production sites, just like with fields or views UI.

Developer

Provides helpful Drush commands and code generators for ECA plugins.

Integration with other modules

Around 40+ modules already integrating with ECA, including some bigger ones like AI, Commerce, Easy Email, Flag, Tamper, Webform, and many more

650+ plugins

For every Drupal site

  • Simple tasks: notifications, logging or form altering
  • Advanced tasks: redirect after login
  • Complex tasks: customize editor experience
  • Leading Edge: building applications

Alerting

Notifications

Authentication flow: simple

Authentication flow: complex

Use Case 1
SAP frontend

Front end to a global SAP system to manage ledgers with workflows, revisions and external audits for up to 5 years ahead.

  • 30-40 different user roles
  • 25 node types
  • 20 taxonomies
  • 18 workflow states
  • intense rules to validate data and references

Only allow to delete the latest revision

Error handling and alerting

Export multiple views into ZIP archives

Validate complex node form

Auto-generate entity labels across references and prevent unintended changes

Ensure unique values

Status indicator calculated across references

Validate node form considering taxonomy term values

Validate node form with several loops

Workflow transitions

Use Case 2
Booking System

Allocations

Bookings

Contacts

Contracts

Using Views to receive the lists of items.

Using Easy Email to send messages in different languages.

  • Queue
    • booking reminders
    • missing signatures
    • forthcoming arrivals
  • Cron to process queues

Conclusion

ECA is for every Drupal site!


Customers and end-users love it! Why?

  • It helps them understand.
  • It creates transparency.
  • They feel involved and independent.

Q&A

Session Feedback





Thank you for your attention!