Enable True/False Metadata Mapping for Checkboxes and Radio Buttons in Box Forms
Description:
Today in Box Forms, checkbox and radio button inputs are not natively mapped to Boolean metadata fields (true/false or yes/no), which limits the ability to trigger workflows or create metadata-driven views based on user responses.
Feature Request:
Allow checkboxes and radio buttons in Box Forms to map directly to Boolean metadata fields:
If a checkbox is checked, metadata should reflect “true”; if unchecked, “false.”
For yes/no radio button questions, allow mapping directly to true/false metadata fields.
Impact & Value:
Streamlines workflow automation with Box Relay (e.g., trigger based on form input).
Enables metadata-driven views (e.g., show only records where “Sensitive Data” = true).
Reduces reliance on workarounds to parse and apply Boolean logic from form responses.
Supports regulated and high-volume environments with binary decision routing needs.
Example Use Case:
In a procurement request form, checking a box labeled “Over $10,000?” would automatically set metadata to “true” and trigger an approval chain through Box Relay.
AdminKaitlin K
(Admin, Box)
shared this idea
-
Anonymous
commented
Another use case for this I've run into is applying DocGen conditional logic based on whether a checkbox in a form was marked or not.