In reply to: Daniel Krüger (DCCS)
I'm also for a less hacky option to apply colors to paths, so I get rid of my approach. Add a simple css class to the path element based on the selected color would solve this:
https://community.webcon.com/forum/thread/2181?page=1#m2187
Off topic:
These kind of names are a "no-go" for me. Always use a more descriptive way to inform the users what will happen. Let's imagine a multi approval step workflow and users can have different roles in this.
If we have only "Reject" or "Approve" the user needs to first understand which role he currently has.
If we use a more elaborate naming for the path, it's way more easier:
Reject as QM responsible
Reject as cost center owner
Approve and forward contract to customer
This makes it also easier to choose the correct "Reject" path from the variables in Designer Studio.
Best regards,
Daniel
I agree with both of you, so I would also like to share my perspective.
For me, the biggest pain point is not necessarily the path names themselves, because naming can often depend on the specific process and business context. The bigger challenge is maintaining consistent button/path styles across applications.
My suggestion for WEBCON would be a solution somewhere in between.
Imagine having a central path style selector.
In the global settings, an administrator or developer could define a list of reusable button/path styles. Each style would have:
a unique name (e.g. "Approve", "Warning", "Reject", "Neutral Action"),
predefined styling options (e.g. color, font weight, etc.),
translations.
Additionally, it could be possible to mark one of the styles as the default style.
If a default style is defined, it would be automatically selected when creating a new workflow path/button. This option should not be mandatory — if no default style is selected, the system would behave as it does today, and newly created paths would use the current custom styling option.
Then, when configuring a workflow path, developers could select a style from the centralized list:
Path styling:
Select one of the predefined styles from global settings,
or choose a custom option and define the styling manually (similar to the current functionality).
Additionally, WEBCON could provide a "Used by" tab, allowing users to see where a specific button style is currently applied across the environment.
Benefits of this approach:
Ensures consistent UX across all applications and workflows.
Reduces duplicated configuration and manual styling.
Makes global design changes easier — updating one style would update all paths using it.
Improves governance in larger WEBCON environments.
Allows organizations to maintain their own design standards while still keeping flexibility for specific cases.
This approach could also work together with a centralized path name catalog, as both concepts solve different problems: names improve consistency and understanding, while styles improve usability and visual guidance for users.
Best Regards
Vitalii
10.08.2026
14:49
