Who would benefit? |
A user in Enrich who wants a "one way" approval for an entity, where the current approval process is based on a boolean field (very common approach). |
What impact would it make? |
Much much easier to use and understand for the editor. Less risk as a button is only "one way" (false => true) |
How should it work? |
Add a field type setting to a booean field type in river. (Setting: BUTTON_TRUE_DISPLAYTITLE = Approve;Approved) When this setting is available, and the boolean value is False, the UI will change in Enrich so that a button is displayed instead of true and false values (title of the button is picked up from the setting). |
Why is it needed? |
To make the user interface better for the users and to remove the walkaround stamp on the current approach. |
Additional feedback, background or context:
Current view:
Suggested button views: