What is the best way to determine status of sub-processes and tasks?

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-10-2013 07:09 PM
Hi,
I am new to activiti and am trying to figure out how to get an inventory of all sub-processes and tasks of a given process that includes activated and those that workflow is yet to reach. In short I am trying to create a map of what sub-processes/tasks were already completed, available for actions and which sub-processes/tasks should be anticipated when workflow reaches them.
It seems that items currently active and already completed can be found through regular and historic query API but is there a single call that would bring the full inventory of the process elements with their respective statuses?
Thanks,
Alex
I am new to activiti and am trying to figure out how to get an inventory of all sub-processes and tasks of a given process that includes activated and those that workflow is yet to reach. In short I am trying to create a map of what sub-processes/tasks were already completed, available for actions and which sub-processes/tasks should be anticipated when workflow reaches them.
It seems that items currently active and already completed can be found through regular and historic query API but is there a single call that would bring the full inventory of the process elements with their respective statuses?
Thanks,
Alex
Labels:
- Labels:
-
Archive
1 REPLY 1
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-11-2013 03:30 AM
Hi Alex,
The problem is that process definition does not says which nodes in the graph will be executed (gateways, loops, conditions…..)
You can simulate execution to get future execution path with some probability (activiti-crystalball http://gro-mar.github.io/activiti-crystalball/)
Regards
Martin
those that workflow is yet to reach.I do not know about such a query. You can get process definition and parse all activities there.
The problem is that process definition does not says which nodes in the graph will be executed (gateways, loops, conditions…..)
You can simulate execution to get future execution path with some probability (activiti-crystalball http://gro-mar.github.io/activiti-crystalball/)
Regards
Martin
