Hiding attributes and references prevents parameters and values from displaying. This is useful when parameters are irrelevant to a scenario, such as attributes that are unnecessary on certain object types. Hiding attributes and references can reduce the complexity of detail screens and remove clutter for the current job. It can prevent users from seeing data that is not pertinent to their role, for example, a marketing user has no need to view the values that a buyer user needs to view.
Recommended Use
-
A business condition is required when an attribute or a reference should be hidden dynamically, that is, based on another setting in the node.
-
If an attribute or reference should always be hidden, use the Web UI designer or other validation options to hide the object permanently.
Hidden validation can be set in the Web UI as defined in the linked topics below.
Attributes
Validation can be set on attribute objects as defined in:
-
Conditional Attribute Display topic in the System Setup documentation (here)
-
Validity on Description Attributes topic in the System Setup documentation (here)
-
Validity on Specification Attributes topic in the System Setup documentation (here)
Business Conditions
Validation can be set dynamically based on other information on the node via business conditions as defined in:
-
Configuring Business Conditions in Web UI topic (here)
-
Hidden Bind topic (for use with JavaScript business rules) in the Resource Materials online help documentation (here)
References
Validation can be set for references as defined in:
-
Reference Type - Select Valid Source Types topic in the System Setup documentation (here)
-
Reference Type - Select Valid Target Types topic in the System Setup documentation (here)
Users
Validation can be set for users as defined in: