Hierarchy - Organization Control/Field

  • Updated

A Organization is a hierarchy control that allows to response one or multiple organization(s)' name which is managed in Yeeflow organization

Similar with a user control, the user will only be able to choose organization(s) that you have already managed in Yeeflow. Using a organization control to display, assign a task, even control the access to some section of this form or a data list of this application.  


Label & Binding

The label will display as the title of this field. You can define the name for this field.

In Form Builder, You also can switch off "Display Title" to hide the label on this form. 

Binding is also only applicable for form builder. A organization field can be reset to bind with any other organization controls on this form. 

<Return to Top>

Parent Node

Parent Node is optional to be set for organization controls. No binding of parent node will provide all your Yeeflow organizations and sub-organizations(if hierarchy is enabled) to choose. 

Using a custom set of parent node to restrict a subordinate list of an organization that will appear in this organization field. There are two options to associate its parent node. 

Static:  A static parent node will provide all sub-organizations in your Yeeflow. You can choose any of them. The user will be able to select its subordinate organizations then. 

Variable: A variable parent node will allow you to bind another organization control/field (from  Expression Editor) on this form.  That another organization field is always a multiple one, so that the user will be able to choose some from these multiple organizations.



Define the appearance of this field to change the styles. 

  • Placeholder

Placeholder is a text input that provides a short prompt that describes the expected value of user input. The prompt is displayed in the field before you enter a value, and disappears when you begin typing.

  • Dynamic Display Rules

When you set a dynamic display rule for this field, It behaves differently based on specific conditions and rules.  There are seven actions(Hide/Show/Read-only/Editable/Set Background/Set Border color/Set Font color) for this control. 

Learn how to create dynamic display rules for a field

  • Allow Comment

You can enable/disable comments on this field after the form is submitted. There are two options to trigger comments entering:  On Click and Mouse Hover

For a bound control, the comment key will be auto-bound with this control/field.

  • Hierarchy

Similar with Metadata control, hierarchy is an important feature of a organization. You can maintain any number of hierarchies for one organization.

You can enable/disable hierarchy for this field.  By default, it's disabled for organization fields.

A enabled hierarchy is a way to offer this field with all organizations and their subordinates in your Yeeflow or your custom parent node.

A disabled hierarchy will offer the sub-organizations under your Yeeflow or subordinates under its parent node. 

<Return to Top>


Validation will verify that the data users enter in this form meets the standards you specify before the form can be submitted.

  • Readonly

Set this field as read-only to create variable form pages of your workflow(or application versions) . All bound controls (fields) can be made read-only, with the exception of fields that are already read-only by default.  E.g. Calculation.

  • Required

Required field will make sure the user provides a response. When a field is required, an error message will display under this field and at right top of the form. The form cannot be submitted until a value has been added to the field.

Required fields are indicated by a red asterisk next to the label. By default, fields are never required.

Note: Only a required field in visible of this form will trigger the validation action.

  • Multiple

You can enable/disable multiple choices for a organization field. If multiple enabled, the users are able to choose one or multiple organization(s) according to your custom set of parent node and hierarchy. 


  • Custom Validation

You can set a custom error message that will display under your field when specified conditions become true. It will allow you to add any number of rules for validating your field.
Learn more about the Custom Validation.

  • Event Rules (only applicable for Forms)

Event rules allow you to set actions that should be taken on events that meet your designated rule criteria. You can create event rules to execute any number of actions based on this field. 

Learn more about the Event Rules

  • Default Value

Default values can be used to automatically populate the field’s value for users. The user can then choose to change the default value. The default value can always be the same value or can change based on certain conditions such as a Event Rule of another field on the form.

A default Current User's Organization will help you to get the user's organization by using this form page.


  • Unique Value

There are certain fields that you never want to contain duplicate values. You can easily prevent a field to enter a duplicate values by making it unique.  

<Return to Top>

Was this article helpful?




Please sign in to leave a comment.