What is the problem you are trying to solve?
Conditional Field visibility across Fieldsets in Fragment configuration.
The ability to make one Field in a Fieldset dependent on the value of another provides a great opportunity to improve the UX for the Page Builder.
However, this feature is currently limited because it cannot be applied to Fields in other Fieldsets, or indeed to an entire Fieldset.
Examples of where this might be a problem might be:
- A Fragment that provides 2 (or more) options via a Select configuration that offer entirely different presentations to the users - example is one where there’s an option to use Clay “Labels” using the default sizes (label, label-lg) and types (label-primary, label-success etc.), another option that provides the ability to select a colour (from a stylebook) to apply as a background color to a , and so on. The ideal configuration would be for the basic option to be in one Fieldset, with a separate Fieldset for “Label Config”, “Panel Config”, etc.
- A Fragment with a lot of configuration options, where it simply provides a more elegant UX to group fields into Fieldsets based on their behaviour, and to allow some fields in each Fieldset to be dependent on fields in others.
Neither of these use-cases is supported because the system only allows fields within a Fieldset to be dependent on other fields in the same Fieldset. The outcome is that for either of the above use-cases the designer must put all fields into a single Fieldset.
What is your project about? (e. g. Intranet, Partner Portal, Enterprise Website, etc)
Enterprise website (liferay.dev)
What is your proposed solution? (optional)
Simple - allow two changes:
- Allow one Field to be displayed depending on the value of a Field in a different Fieldset
- Allow an entire Fieldset to be displayed depending on the value of a Field in a different Fieldset