RELATED IDEAS
Make swimlanes systems-agnostic
Currently, swimlanes are auto-created every time a new combination of role/responsibility or system is entered into the "assign role" section of an activity.
This creates multiple swimlanes if the same role uses different systems within a process, resulting in a messy process map.
Having system tags in an activity is a useful function, though.
It would be excellent to be able to "switch off" the inclusion of systems as determinants of additional swimlanes.
This creates multiple swimlanes if the same role uses different systems within a process, resulting in a messy process map.
Having system tags in an activity is a useful function, though.
It would be excellent to be able to "switch off" the inclusion of systems as determinants of additional swimlanes.
-
GuestSep 7, 2022Thanks for the feedback. We'll open this for voting to gauge interest from other clients. In the meantime you can use the System name in the Activity somewhere e.g Task or Note, rather than as a Role/System assigned to Activity. The System will still appear as a tag in the process and will be picked up in reporting, but won't appear as a swimlane participant.0 reply Hide replies
