Hi!
Current state:
When using orchestration , it's possible to link and synchronize a process with a process map. This is a great feature for monitoring and controlling a process!
Problem:
However, when building an overview of dependent processes (e.g. two or more processes that run within the same schedule), it would be very helpful to link multiple processes directly to a single process map. This would allow us to monitor and control them together from one central place.
Workaround/ Solution finding:
Our current workaround is to create an extra process that contains the individual processes as sub-steps, and then link that wrapper process to the process map (without scheduling it). While this technically works, it becomes messy over time and requires maintaining the same logic in multiple places. This increases the risk of errors and makes orchestration harder to manage.
I did notice that within the process map builder, there is an option to add a process map to another process map (so nested maps). However, the task status indicators (success, warning, failed) do not reflect the actual status of the nested process map (see screenshots down below). Because of this, it's not reliable for monitoring or controlling multiple processes from a single map.
Feature suggestion:
Managing multiple processes from a single map would be easier if one of the following changes were implemented:
-
Allow linking multiple processes directly to a single process map.
-
Nested process maps reflect accurate status indicators for monitoring and control.
Screenshots:
Web interface (deployed):
Nested map is always (even with failed tasks) a single green check. Redirects on click to the nested map.
Editor view:
From editor view it seems like it should show a list of indicators connected to the nested map.
