Tutoriel jBPM Workflow — Exclusive Gateway expliqué

 Dans un workflow métier, certaines décisions doivent choisir un seul chemin parmi plusieurs.

Exemple :

  • Paiement accepté → traiter commande

  • Paiement refusé → annuler commande

Un seul résultat est possible.

Pour cela on utilise le Exclusive Gateway (XOR Gateway).

Cette architecture est couramment utilisée dans les environnements microservices modernes.

👉 environnements microservices modernes

📌 Qu’est-ce qu’un Exclusive Gateway ?

Le Exclusive Gateway permet de diriger le flux vers une seule branche selon une condition.

Contrairement :

  • Parallel Gateway → tous les chemins

  • Inclusive Gateway → plusieurs chemins

  • Exclusive Gateway → un seul chemin

🖼️ Diagramme Exclusive Gateway

🧠 Fonctionnement

Le moteur évalue les conditions dans l’ordre :

👉 La première condition vraie est choisie
👉 Les autres chemins sont ignorés

🛠 Exemple réel — Paiement commande

Commande → Vérification paiement
        → Accepté → Expédition
        → Refusé → Annulation

Une seule branche continue.

🖼️ Exemple métier

🧾 Configuration dans jBPM

Dans jBPM Modeler :

  1. Ajouter Gateway → Exclusive Gateway

  2. Ajouter conditions sur les flux sortants

  3. Ajouter un flux par défaut (recommandé)

Exemple logique

Start
  ↓
Exclusive Gateway
  ↙      ↘
Cond A  Cond B
  ↓      ↓
Task A  Task B
  ↓      ↓
End

⚠️ Erreurs fréquentes

❌ Oublier flux par défaut
❌ Conditions ambiguës
❌ Plusieurs conditions vraies simultanément

🔐 Bonnes pratiques

✔ Toujours définir un chemin par défaut
✔ Conditions mutuellement exclusives
✔ Priorité claire des règles

🎯 Quand utiliser Exclusive Gateway

Utiliser pour :

  • Décision unique

  • Statut accepté/refusé

  • Choix simple

Ne pas utiliser pour :

  • Exécutions parallèles

  • Règles multiples

🎯 Conclusion

L’Exclusive Gateway représente une prise de décision unique.

C’est l’élément le plus utilisé dans les workflows métier.


💼 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), DMN/Drools.

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

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


🎥 Learn IT with Shikha on YouTube

Prefer learning through videos? Watch practical tutorials on Kafka, Camunda, Alfresco, Java, Spring Boot, Microservices and Enterprise Architecture.

▶ Subscribe to Learn IT with Shikha on YouTube

Comments

Post a Comment

Popular posts from this blog

Top 50 Camunda BPM Interview Questions and Answers for Developers (2026 Guide)

Image
  Top 50 Camunda BPM Interview Questions and Answers for Developers (2026 Guide) Introduction Camunda BPM is one of the most widely used workflow automation platforms for building process-driven applications using BPMN, DMN, and microservices architecture . Many companies use Camunda for: Business process automation Microservices orchestration Workflow management Enterprise integration Because of its growing popularity, Camunda BPM interview questions are frequently asked in Java developer interviews . In this guide, we cover 50 important Camunda BPM interview questions and answers ranging from beginner to advanced levels .
Read more

10 BPMN Best Practices Every Camunda Developer Should Know

Image
  10 BPMN Best Practices Every Camunda Developer Should Know Designing BPMN processes in Camunda is easy—but designing them correctly, scalable, and maintainable is what separates beginners from experts. In this guide, you’ll learn 10 essential BPMN best practices that every Camunda developer should follow. 🔹 1. Keep Your Process Simple Avoid overcomplicating diagrams. 👉 A simple process is: Easier to debug Easier to maintain Easier for business users to understand 🔹 2. Use Meaningful Names Bad: Task1 ProcessA Good: Validate Customer Data Approve Loan Request 👉 Always use verb + business context 🔹 3. Use Async Continuations Wisely Use: asyncBefore asyncAfter 👉 Helps in: Retry handling Transaction boundaries Avoiding long DB locks 🔹 4. Avoid Long-Running Service Tasks Problem: Blocks Job Executor Solution: 👉 Use External Tasks for: API calls Heavy processing 🔹 5. Use Exclusive Gateways Properly 👉 Always define conditions clearly Avoid: Multiple true conditions Missing d...
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