The current colour options are limited to five colours. This limitation is insufficient for adequately representing the numerous stakeholders involved in a process. Users need more flexibility in colour selection to accommodate different needs. This is more apparent for "documentation only" processes
Proposed solution
An expansion of the available colour palette. Having the ability to create new colours under the 'More Colors' option or select a colour using a hex code.
Alternatives considered
I will differentiate roles using colours to help the stakeholders understand which role is responsible for which task. 5 colors, and white, aren’t enough options to identify all the roles all the time. In the attached example, I required 7 options/roles. As such, I used purple twice but created a new role by incorporating an intermediate/boundary event in the task. Obviously, this is not ideal and is not BPMN 2.0 compliant.
Could use element templates + icons to denote participants
Additional context
The colour picker already supports custom colours, so the main challenge is solving the "configuring of custom colours and storing them" within the context of the modeler. This would allow for greater flexibility, such as allowing users to override the current defaults with custom hex codes. For example, users could either override a 6th colour or replace all existing default colours with their chosen palette.
This approach would enable customers to define and select multiple colours without requiring additional requests or interventions from our side.
Problem you would like to solve
The current colour options are limited to five colours. This limitation is insufficient for adequately representing the numerous stakeholders involved in a process. Users need more flexibility in colour selection to accommodate different needs. This is more apparent for "documentation only" processes
Proposed solution
An expansion of the available colour palette. Having the ability to create new colours under the 'More Colors' option or select a colour using a hex code.
Alternatives considered
I will differentiate roles using colours to help the stakeholders understand which role is responsible for which task. 5 colors, and white, aren’t enough options to identify all the roles all the time. In the attached example, I required 7 options/roles. As such, I used purple twice but created a new role by incorporating an intermediate/boundary event in the task. Obviously, this is not ideal and is not BPMN 2.0 compliant.
Could use element templates + icons to denote participants
Additional context
The colour picker already supports custom colours, so the main challenge is solving the "configuring of custom colours and storing them" within the context of the modeler. This would allow for greater flexibility, such as allowing users to override the current defaults with custom hex codes. For example, users could either override a 6th colour or replace all existing default colours with their chosen palette.
This approach would enable customers to define and select multiple colours without requiring additional requests or interventions from our side.
Feature request link: SUPPORT-22607