Loading...

XML

Word

Printable

As Cockpit user / operator
*Given*
- I am in the process instance view (history and runtime)
- The current process instance has at least one call activity with at least one called process instance
*Then*
- I can easily navigate to a called process instance (for example by double clicking on the call activity)
*So that*
- an operator who frequently has to navigate large process instance hierarchies can do his/her work efficiently

Challenges

- Note that the "double click" on the call activity mentioned above is one way of implementing this but it may not be the way it will eventually be done. It is used to illustrate the degree of ease of use which should be targeted with this issue
- history vs. runtime: in runtime I can only navigate to called process instances which are currently beeing executed. In history I can navigate to both completed and currently active
- In the event of a multi instance call activity and an a loop in the process, there may be more than one process instance which is called.

depends on

CAM-8675 In cockpit, from a process instance history view, I can easily navigate to a child/called process instance

CAM-8676 In cockpit, from a process instance runtime view, I can easily navigate to a child/called process instance

is duplicated by

CAM-6591 As cockpit User, I can click on a badge on a callActivity to see the called process instance

is related to

CAM-7839 In cockpit, from a process instance, I can easily see the hierarchy of parent (calling) process instances

links to

https://github.com/camunda/camunda-bpm-platform/issues/2201

In cockpit, from a process instance, I can easily navigate to a child/called process instance