Note: this feature is available exclusively in the PRO business version and can only be used in Conditional process control. Not all form fields need to be visible from the start. In some cases, it makes sense to show additional fields only after a user selects a specific option or enters a particular value in another field. The Conditional Field Display feature is designed for these scenarios. It helps keep forms simple and easy to navigate by showing users only the fields that are relevant to them. Field display conditions can be configured in the form builder using the menu on the right: In order for a field to control the visibility of other fields, it must be assigned a Field Key or an Extension Key. Example Let’s assume that in the Orders process, on the Approval activity, the user can decide whether to accept or reject an order. If they choose the Reject option, we want to display an additional required field: Rejection reason. To make this possible, the Decision field on the Approval activity must be assigned an appropriate value in the Extension Key field: Next, we move on to configuring the condition. Click the Conditions button in the menu: Once the Conditions window appears, click the Add button, then fill in the required fields:
Name – any name for the condition that will make it easy to identify later.
Field – here you will find a list of all fields and extensions that have been assigned a Field Key or Extension Key within the process.
Operator – defines how the field value is compared to the value provided in the condition.
Available operators: = the field is equal to the value specified in the Value field != the field is not equal to the value specified in the Value field > the field is greater than the specified value (for numeric fields) >= the field is greater than or equal to the specified value (for numeric fields) < the field is less than the specified value (for numeric fields) <= the field is less than or equal to the specified value (for numeric fields) Note: The Value field can be left empty. In this case, the comparison will be made against an empty value. In our example, the condition will look as follows: The feature also allows you to create more advanced conditions. Individual rules can be combined using the AND and OR operators by selecting the appropriate tab in the condition configuration. You can add new conditions by clicking the Add rule button, while more complex structures can be created using condition groups via the Add group button. Grouping conditions makes it possible to build advanced field visibility logic that includes multiple criteria and dependencies. Example of using a condition group: In the example shown, the condition will be met only if the Reject option is selected in the field with the key decision, and either Marketing or Accounting is selected in the field with the key department. After creating and saving the condition, it must be assigned to the field whose visibility depends on it. In our example, this is the Rejection reason field: When configuring conditions, care should be taken to ensure they are not too restrictive. Incorrect settings may cause some fields not to appear in situations where they should be visible. If you have any difficulties setting up conditions, please contact us. We’ll see how we can help 🙂
In order for a field to control the visibility of other fields, it must be assigned a Field Key or an Extension Key. Example Let’s assume that in the Orders process, on the Approval activity, the user can decide whether to accept or reject an order. If they choose the Reject option, we want to display an additional required field: Rejection reason. To make this possible, the Decision field on the Approval activity must be assigned an appropriate value in the Extension Key field: 
