flowable / flowable/flowable-engine
Flowable (REST-only): How to get “where am I” and the exact path taken for one process run?
- Lingua principale
- Java
- Stelle
- 9.5k
- Fork
- 2.9k
- Merge medio
- 7h 8m
- PR unite (30g)
- 2
Descrizione
Hey there!
We are working with Flowable as our workflow engine in java, but our code is in typescript and we communicate with the engine via RESTful API calls.
I'm working on a feature trying to understand 2 things (given a processInstanceId) -
1. **Current position** - on which node a current workflow instance run is on? (“where am I?”)
2. **Actual path** - the ordered list of activities that really executed in this run (e.g. model has node1→node2→node3, but this run did node1→node3 so the final result should be ["node1","node3"]).
I’ve tried many things but mostly - "/runtime/executions" for the active tree and "/history/historic-activity-instances" (+ variables) to rebuild the path. This breaks in parallel/multi-instance (parallelForEach) and async cases: inner nodes use different executionIds, and runtime rows disappear after completion (executions are done and deleted so i cant query their activities).
Question: Is there a REST-only, recommended approach (or example) to (a) get current activity the instance is on and (b) reconstruct the exact visited activities with a stable parent/child mapping in history? Happy to share a small BPMN + payloads if useful.
also sorry for opening an issue, I uploaded the question 9 days ago in the flowable-forum and didn't get any response :(
Guida per i contributori
Nessuna guida per i contributori indicizzata per questo repository
Direzione di ricerca
L’issue indica /runtime/executions e /history/historic-activity-instances come i punti di ingresso REST rilevanti; inizia verificandone il comportamento per le istanze completate, parallele e asincrone. Non vengono indicati file o test. Il lavoro è completato quando viene individuato un modo supportato e REST-only per ottenere le attività correnti e visitate, oppure viene documentato che la mappatura stabile richiesta non è disponibile.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- java, typescript
- Ambito
- api, backend
- Tipo di issue
- Funzionalità
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Stato di attività
- Ferma
- Chiarezza
- Da chiarire
- Idoneità per principianti
- 25/100