Skip to Main Content
Bentley Infrastructure Cloud IDEAS Portal - New
Status Already exists
Created by Caroline Mathias Castilho
Created on May 26, 2026

Conditional Button Visibility Based on Form Properties

Hi Team,

I would like to propose a powerful enhancement to the workflow capabilities of our forms by extending the logic of the existing "properties condition" feature.

The Suggestion:
Currently, we can use a property's condition to determine the
next status of a workflow. I propose extending this functionality to also control the visibility of workflow buttons on the form.

The Use Case:
This would allow us to create dynamic forms that guide the user toward the correct action and enable multiple workflows within a single form.

For example, imagine a form with a dropdown field "Request Type":

  • If the user selects [Option A], only the button [Submit for A-Approval] is visible.

  • If the user selects [Option B], the first button is hidden, and a different button, [Submit for B-Approval], becomes visible.

The Problem this Solves:
Without this feature, our only option is to create two separate, nearly identical forms—one for each workflow. This creates redundant administrative work and clutters the system. Alternatively, we show all buttons to all users, which is confusing and can lead to them submitting the form to the incorrect workflow.

The Benefit:

  1. Dynamic and Intelligent Forms: The form adapts to user input, creating a much more intuitive and streamlined experience.

  2. Reduced Administrative Overhead: We could manage multiple process variations within a single form, drastically reducing the number of forms we need to create and maintain.

  3. Improved Accuracy: It prevents user error by only showing them the actions that are relevant to their specific situation.

This would be a significant step forward in the flexibility and power of the form builder. Thank you for considering this enhancement.

  • Attach files
  • Admin
    Caitlin Zeuli
    Jun 2, 2026

    You can do almost exactly this today!

    We have a feature in the Workflow called Conditions where you can add Properties that must be set to a specific Value to be able to use a Transition Button.

    While it does not hide the button, it does not allow the user to progress the form using a transition button if the requirements are not met. And an error is returned.


    I know this is not completely aligned with your hopes, but this configuration allows the system to have the best performance since it only checks the button requirements when one is selected.