Boundary Events vs Event Subprocess en BPMN — Comparaison complète

Dans un workflow BPMN réel, il faut gérer des situations inattendues :

  • L’utilisateur annule une demande

  • Un délai est dépassé

  • Un SLA est violé

  • Un paiement échoue

Deux éléments BPMN permettent cela :

👉 Boundary Events
👉 Event Subprocess

Ils sont souvent confondus mais leur comportement est très différent.

📌 Définitions rapides

Boundary Event
Attaché à une activité spécifique.

Event Subprocess
Attaché à l’ensemble du processus.

🖼️ Différence visuelle

🧠 Compréhension conceptuelle

Boundary Event → surveille une tâche
Event Subprocess → surveille tout le processus

🔥 Comparaison comportementale

FonctionBoundary EventEvent Subprocess
PortéeActivité uniqueProcessus complet
DéclenchementPendant la tâcheÀ tout moment
Cas d’usageException localeÉvénement global
ConnexionAttaché à tâcheAucun flux entrant
VisibilitéLocaleGlobale

🛠 Exemple réel — Approbation de prêt

Processus :

Soumettre → Approbation → Paiement

Événements :

  • L’utilisateur annule

  • Le manager tarde

Cas 1 : Retard d’approbation

👉 Boundary Timer Event
Car le délai concerne uniquement la tâche.

Cas 2 : Annulation utilisateur

👉 Event Subprocess
Car l’annulation peut arriver à tout moment.

🖼️ Exemple réel

🔧 Types de Boundary Event

  • Timer

  • Error

  • Message

  • Escalation

Interrupting → annule la tâche
Non-interrupting → parallèle

🔧 Types d’Event Subprocess

Déclencheurs :

  • Message

  • Timer

  • Signal

  • Escalation

🖼️ Comportement interrupting

⚠️ Erreurs fréquentes

❌ Boundary pour annulation globale
❌ Subprocess pour timeout local
❌ Flux entrant vers subprocess
❌ Mauvais type interrupting

🎯 Règle simple

Utiliser Boundary Event si :

✔ Exception liée à une tâche
✔ Timeout local

Utiliser Event Subprocess si :

✔ Événement global
✔ Action externe

🔐 Bonnes pratiques

Timer SLA → Boundary Event
Action client → Event Subprocess
Erreur technique → Error Boundary
Changement métier → Message Subprocess

🧠 Astuce mémoire

Boundary = Exception locale
Event Subprocess = Événement global

🎯 Conclusion

Boundary Events gèrent les exceptions d’activité
Event Subprocess gère les réactions globales

Un bon choix évite des workflows cassés.

💼 Support professionnel disponible

Si vous rencontrez des problèmes sur des projets réels liés au développement backend d’entreprise ou à l’automatisation des workflows, je propose des services de conseil payants, de débogage en production, de support projet et de formations ciblées.

Les technologies couvertes incluent Java, Spring Boot, PL/SQL, Azure, CMS, ainsi que l’automatisation des workflows (jBPM, Camunda BPM, RHPAM).

📧 Contact: ishikhanirankari@gmail.com | info@realtechnologiesindia.com

🌐 Website: IT Trainings | Digital lectern | Digital rostrum | Digital metal podium     



Comments

Post a Comment

Popular posts from this blog

Scopes of Signal in jBPM

Image
💡 Introduction Signals in jBPM 7 are a core part of event-driven workflow design. They allow asynchronous communication between process instances, making it possible to start , interrupt , or coordinate processes without direct linking. However, signals can have different scopes , which define how far the signal travels and who receives it . Let’s explore the four available scopes in detail: 🔹 Process Scope 🔹 Default Scope 🔹 External Scope 🔹 Project Instance Scope 🧩 1️⃣ Process Scope 📘 Definition Process scope signals are local to a single process instance or its child subprocesses . They are not visible outside that instance hierarchy. 📋 Use Case Used for communication inside the same process , like triggering subprocesses or event sub-processes. 🖼️ Process Scope Example Below is an example of a simple process-scoped signal. Only this process (or its subprocess) will catch this signal. ⚙️ 2️⃣ Default Scope 📘 Definition The default scope ...
Read more

OOPs Concepts in Java | English | Object Oriented Programming Explained

Image
🔹OOPS (Object Oriented Programming System) in Java Object-Oriented Programming (OOPS) is a programming paradigm that uses classes and objects to design software. It simplifies development and maintenance by applying key concepts: 📌 Class: Class   is a user-defined data type which defines its properties and its functions. Class is the only logical representation of the data. For example, Human beings in an organisation is a class like Employee. The age, name, department, salary etc. of a human being/employee are its properties, and the jobs performed by the employees in an organisation are known as functions.  The class does not occupy any memory space till the time an object is instantiated. A class is a user-defined data type that defines properties and functions. For example: Class: Employee Properties: name, age, salary Functions: work(), attendMeeting() A class does not occupy memory until an object is created. ...
Read more

jBPM Installation Guide: Step by Step Setup

  jBPM Installation Guide – Step by Step for Beginners If you are starting with jBPM (Java Business Process Management) , the first step is to set up your environment. In this guide, we’ll walk through how to install jBPM, configure it, and run your first business process. 🔎 What is jBPM? Before we dive into installation, a quick recap: jBPM is an open-source Business Process Management (BPM) suite , written in Java, that allows you to model, execute, and monitor workflows using BPMN 2.0 standards. It can run standalone , embedded in applications , or deployed on a Java EE server . 🖥️ Prerequisites Before installing jBPM, make sure you have: Java JDK 11 or later (Java 17 is commonly used) Maven 3.x (for building and managing dependencies) Git (optional, if you want to clone sample projects) A Database (H2, MySQL, PostgreSQL, or Oracle) – jBPM ships with H2 for testing At least 4GB RAM (8GB recommended for Workbench & KIE Server) 📦 Download ...
Read more