- Issue created by @spiderman
-
spiderman →
committed 696f20b8 on main
Issue #3505186: Make use of States API optional
-
spiderman →
committed 696f20b8 on main
Currently the module assumes that you want to set the selected field as required *both* when loading an entity form where the entity is in the required state *and* when changing the workflow state on the form (client-side) before submitting the form.
The request here is to make the second part optional, so that we can choose to have the module *only* do the first thing: set the required state of the field when loading an entity form, if the entity is in one of the selected states.
Introduce a new per-field third-party config setting for "use states api" to allow this behaviour to be optional.
A new setting on the field config form labeled "Set field as required immediately upon selecting workflow state using Javascript."
New "use_states_api" boolean config in the per-field third-party settings schema.
Active
1.0
Code
Issue #3505186: Make use of States API optional