The primary object of the behavior descriptor is to capture business methods (behaviors) used on the page. In order to attain this, the behavior descriptor first provides means of capturing or defining all objects that could provide properties and methods for the page. In this definition both the known name and the class and scope of the object could be define.

In essence the behavior descriptor has two primary modes, 1) object definition, and 2) logic or business method definition.

Example of such logic could be an indicator for customer that are due for renewal, customers that have overdue in payments. These could also be logics to determine mode, for example whether the user is a novice that wants full help displayed or experienced that just want the entry forms.

In all these case, the logic would mostly be used to determine whether portion of the page (segment), should be visible (rendered) or not. This could also be used to determine whether portion of the page should be enabled for data entry, or in display only mode.

With the logic to show or not to show, is also the possible requirement for showing multiple times, like lists.

It is the define type behavior that provides means of object definition, whereas the logic type behavior provides capture for business or presentation logic or expression in general. Lastly, the repeat region specification is capture by the repeat type behavior.

The repeat type usually provides object definitions for the elements in the repeat region. As such the repeat type provides for both, 2) logic or method definition, and 1) object definition.

The discussions on behaviors are present along the line of these divisions.

Behavior-Define
Behavior-Logic
Behavior-Repeat

The general concepts of behaviors are platform independent; however, along the line of the described divisions, there are implementation aspects that entail platform specific discussions.