Tasks.Item10508 proposes a hideempty argument for FlexFormPlugin, to surpress empty form fields. A more advanced step would be to implement includevalues and excludevalues arguments. These would operate analogously to the current include and exclude arguments, but rather than regex-testing the field names, they would test the values.

Testing numeric values with regex would be a little tricky, but it would be better than nothing at all. It could still be very nice for data collection apps that use well known value ranges.

-- AaronFuleki - 18 Mar 2011

Do you want to suppress formields to be displayed based on their value or do you want to filter values to be able to chose from while editing a formfield?

-- MichaelDaum - 18 Mar 2011

I was thinking of this purely from a display suppression standpoint, e.g.:

%RENDERFORDISPLAY{
  excludevalues="pony|kitty"
}%

...wouldn't display any form fields with values of pony or kitty.

Your second suggestion sounds like it could be really powerful, but might open a sizable can of UX worms without thinking about it a bit more. The argument name excludevalues does sound more like it would suppress values while editing, and not fields with those values while viewing. My bad.

-- AaronFuleki - 21 Mar 2011

Okay, gotit. Well, hiding formfields based on their value is really easy.

The other idea (exclude some values to chose from) is probably not doable on the plugin level because all of the interaction is hidden behind expanding the $edit variable which is finally implemented by the FieldDefinition class itself.

-- MichaelDaum - 21 Mar 2011

Micha: I'm still getting spammed on this task. Is this something you're interested in doing, or should we file it away for the future?

-- AaronFuleki - 14 Jan 2012