What Are Business Rules?
Business rules allow you to override the appearance and behavior of fields or regions on a page, provided that the specified conditions in a rule are met at runtime. In this context, a region is simply a dynamic form.
Note:
If you're looking for information on business rules as they pertain to business objects, see Create Rules for Business Objects.For example, suppose you had a data object called Person, that was used in two dynamic forms. Now suppose you want to hide the Organization Name field when the user is a manager, as only HR specialists should see this data. With business rules, you can create a single rule that defines the condition, then overrides the setting for the Hidden property to ensure that Organization Name is hidden when the user is a manager. With this one action, the Organization Name field will be hidden for every region that includes that field.
In other words, business rules let you define a rule at the object level. Let's look at a page with two dynamic forms (Detailed department and NewForm). These are listed in the Regions and Fields section in the image below. Both components use fields from the same data object, and you can quickly see every field used in each component. For example, the Detailed department region consolidates all the fields that are displayed in the form, regardless of the layouts defined in the form. The same applies to the NewForm region. When you set a property in a business rule you are setting it at the object level, so it can be applied to every occurrence of that field, in each component using that data object.
There are two types of rules: extension rules, which are created by you, the extension developer; and built-in rules, which are created by Oracle as part of your extension dependencies. In this example, the Default rule is a built-in rule defined in an extension dependency.