Why Workflows Track Each Case Separately
Fuente:
Zenodo
Salvato in:
| Autore principale: | |
|---|---|
| Natura: | Recurso digital |
| Pubblicazione: |
Zenodo
2023
|
| Accesso online: | |
| Tags: |
Aggiungi Tag
Nessun Tag, puoi essere il primo ad aggiungerne!!
|
| _version_ | 1866901555956940800 |
|---|---|
| author | Hense, Andreas |
| author_facet | Hense, Andreas |
| contents | <p>What does it mean for a workflow to be case-based, and why is this concept essential for real-world automation?<br>This video explains the notion of case-based workflows and clarifies its importance for the execution of business processes in workflow management systems.</p> <p>Using a travel booking example, the video distinguishes between tasks, work items, and activities, and illustrates how each workflow case progresses independently through a process. It demonstrates how multiple instances of a workflow—one per case—are executed concurrently and represented by separate Petri nets that capture the individual state of each case. This perspective highlights how case-based execution enables individualized handling of customers, requests, or transactions within the same process definition.</p> <p>The explanation provides a conceptual foundation for understanding workflow execution semantics and the relationship between process models and runtime behavior.</p> <p>Related resource:<br>- Airline example video:<br> https://youtu.be/U77SPPdfAos</p> <p>Supplementary material, including example models, is available on GitHub:<br>https://github.com/ahense/bpa <br>(Download the complete package via “Code” → “Download ZIP”.)</p> <p>This is video #46 of the BPASeries.</p> |
| format | Recurso digital |
| id | zenodo_https___doi_org_10_5281_zenodo_18322243 |
| institution | Zenodo |
| language | |
| publishDate | 2023 |
| publisher | Zenodo |
| record_format | zenodo |
| spellingShingle | Why Workflows Track Each Case Separately Hense, Andreas <p>What does it mean for a workflow to be case-based, and why is this concept essential for real-world automation?<br>This video explains the notion of case-based workflows and clarifies its importance for the execution of business processes in workflow management systems.</p> <p>Using a travel booking example, the video distinguishes between tasks, work items, and activities, and illustrates how each workflow case progresses independently through a process. It demonstrates how multiple instances of a workflow—one per case—are executed concurrently and represented by separate Petri nets that capture the individual state of each case. This perspective highlights how case-based execution enables individualized handling of customers, requests, or transactions within the same process definition.</p> <p>The explanation provides a conceptual foundation for understanding workflow execution semantics and the relationship between process models and runtime behavior.</p> <p>Related resource:<br>- Airline example video:<br> https://youtu.be/U77SPPdfAos</p> <p>Supplementary material, including example models, is available on GitHub:<br>https://github.com/ahense/bpa <br>(Download the complete package via “Code” → “Download ZIP”.)</p> <p>This is video #46 of the BPASeries.</p> |
| title | Why Workflows Track Each Case Separately |
| url | https://doi.org/10.5281/zenodo.18322243 |