Within the Web UI, JavaScript business conditions can use the Data Validation binds to display customized messages, apply a mandatory status, apply a read only status, or apply a hidden status to an attribute or reference.
Considerations
-
Objects with multiple binds show messages as defined in the individual Data Validation bind topics.
-
In addition to attributes and references, the Mandatory bind can be used in workflows.
-
In addition to attributes and references, the Data Issues Report bind can be used for metadata and Smartsheets.
-
Conditional data validation in the Web UI does not work properly with lazy loaded tabs via the Lazy checkbox in the designer. The Lazy checkbox must not be checked to accurately display data for the Mandatory, Read Only, and Hidden binds. For more information, refer to the Tab Pages topic in the Web User Interfaces documentation here.
-
Generally, use privilege rules to govern what end users can access instead of using JavaScript binds to hide objects, for example, personal IDs. An object that has been hidden via the Hidden bind continues to include the data in the browser which makes it accessible. For more information, refer to the Privilege Rules topic in the System Setup documentation here.
-
Configuring business conditions in the Web UI and other methods for configuring data validation for the Web UI are discussed in the Data Validation in Web UI topic in the Web User Interfaces documentation here.
The Hidden, Mandatory, and Read Only binds are available for use in Node Details screens with the following Web UI components:
-
Attribute Value Component (here)
-
Attribute Value Group Component (here)
-
Globally Configured Reference component (here)
-
References Component (here)
The following topics include information on each of the Data Validation binds: