I was considering putting in an ER for this, unless someone has a better solution. Thoughts?
- Current State: Deriving multiple selections from a single Option List is restricted. Creating a checklist UI currently requires building individual boolean attributes for every possible choice, leading to heavy rule maintenance and a static user interface.
- Proposed Enhancement: Introduce a display type property that allows an Option List to render as a dynamic group of Checkboxes (or a Multi-Select Image Grid). The system must capture all checked values and store them as a single collection (array or delimited string) for downstream rule processing.
- Business Impact: Drastically reduces development time and rule complexity. It enables dynamic, data-driven checklist UIs where options can be filtered or hidden using standard Option List constraints, eliminating the need to manage dozens of separate variables.
- Use Case Example: A user configuring a product needs to select optional hardware accessories. An Option List dynamically generates checkboxes for the currently available hardware. The user checks three boxes, and those three values are passed directly to a single "Selected Hardware" collection variable.
