Set Properties For Regions and Fields

For each field or region on the page, you can set some properties to override the values set by lower-level rules, including the built-in rules provided by Oracle (as long as they are not locked).

These properties include:

• Required – Make required or optional
• Hidden – Visible or hidden
• Read Only – Editable or read only
• Value – Static or expression

In this context, a region is simply a dynamic form.

Property settings affect the display only if the currently logged-in user meets the specified conditions. If more than one rule impacts a given field, it can be tricky to sort out what is finally displayed at runtime to each user group; Understand What Will Be Shown at Runtime can help you.

To set a property on a field or region:

1. Locate the field or region you want to modify.
2. Click the dash—or an existing value—in the appropriate column, and select a new value for the property in the dropdown list.

   For example, you can modify a field’s Hidden property by selecting Visible or Hidden in the dropdown:

   
   Description of the illustration metadata-select-property.png

   VB Studio automatically saves your work for you, so there's no need to do so explicitly.

   If you change your mind after setting a property, use the Remove Override option to remove your setting and restore the property to its original value.

   Descriptive Flexfields (DFF) and Extensible Flexfield (EFF) sections (or contexts), when shown, are treated like any other fields; that is, you can set the Required, Hidden, Read Only, and Value properties for them as needed.

   Remember that the Default rule is always active, which establishes the out-of-the-box behavior. All other built-in and extension rules are essentially overriding what is specified in the Default rule. If none of the other rules evaluate to true, then the only overrides applied are those defined in the Default rule.

   Note:

   A field marked as hidden can still be rendered as visible at runtime. For example, suppose when a page's rules are evaluated, a given field is both required, which means it must have a value, but also hidden. In addition, the field does not have a default value, which means that the user must supply a value explicitly. But how can the user supply a value if the field is hidden? To protect users from encountering this quandary, VB Studio will show the field even though it is marked as hidden, thus allowing users to enter a required value and move on from the page.