For the complete documentation index, see llms.txt. This page is also available as Markdown.

Rewst Options Builder

What is Rewst's Options Builder?

When you add an options-based component to a form, such as a drop-down, radio buttons, or a multi-select, you need to tell Rewst which choices should show up in the list. The Rewst Options Builder is used to configure those options using either a static list or a workflow-driven source.

The Rewst Agent will use the Options Builder to set up your form options when it builds on your behalf. To access the Options Builder for manual form updates, right click on any options-based component that has been placed on the Form Builder Canvas.

Modifying a form using the Options Builder will work for both parent and child organizations.

Static options

Static options are great for options that never change. Use them when the list is short, stable, and lives in your head rather than another system.

  • Label - This is the text users see for this choice. Keep it short and descriptive — for example 'High priority'.

  • Value - This is the value submitted with the form when this option is picked. Workflows and conditions reference this value, so keep it stable — for example 'high'.

  • Description - This optional helper text is shown alongside the option to explain when to pick it.

  • Flags - Default pre-selects this option when the form opens. Disabled shows the option but prevents users from picking it. Required (checkbox groups) forces this specific choice to be ticked.

Workflow options

Workflow options should be used when the list is fetched live from aother system, like your PSA or Microsoft, every time someone opens the form. Pick this for customer names, users, tickets devices— anything that changes on its own and would go stale if you typed it out.

Source workflow

Choose the workflow that supplies the options for the field.

  • Click Load Fields once your workflow is chosen to sample its output. Pulled fields will appear in the Preview panel. Click Refresh Fields to reload the workflow sync.

  • Field mappings - Choose the fields used for each option's value and label.

    • Value - This is the field saved when a user picks this option; for example, a record ID. This is the value submitted with the form.

    • Label - This is the field shown to users. Pick up to 5; they're joined into one label. Drag chips to reorder. Type commas, hyphens, or spaces between chips as separators.

    • Max Options - This caps how many options the component shows. Leave blank to return all options up to the platform limit.

  • Static inputs - Optionally check Enable to send fixed values to the options workflow.

  • Field bindings - Optionally check Enable, to reload options when another form field changes.

Sort and filtering

  • Sort - Control the order in which options appear. Choose the field to sort by, as well as either ascending or descending order.

  • Filtering rules - This sets the form to only show only options that match the rules in the list. Click Add rule to add a new rule; for example, when the date Equals 2026-09-10.

Advanced

Configure additional metadata, raw filters, and runtime controls.

  • Runtime controls - These controls affect how Rewst loads and delivers workflow-generated options. Leave them at their defaults unless you need smaller select batches or results that are always fetched fresh.

  • Advanced mapping - These are optional paths for option descriptions, disabled state, grouping, and metadata.

    • Description path - This maps a row field to option.description. Components that support descriptions show this text under the option label.

    • Disabled path - This maps a row field to option.disabled. Use a boolean-like field; true disables the option so it remains visible but cannot be selected.

    • Group path - This maps a row field to option.group. It's used for grouping in components such as cascader and available for option sorting or filtering.

    • Meta path - This maps an object field to option.meta. Use it to carry extra record data for populate-fields, required markers, or component-specific behavior.

  • Raw filters - Use JSON logic or templates for advanced filtering. Filter workflow results before they are shown as selectable options. Each result is available as item; the mapped option is available as option. If both filters are set, an option must pass both.

Last updated

Was this helpful?