Home > Data Model Assistant

Define Advanced Properties

In this chapter, we will present how to define the following advanced properties:

• Table

• Mandatory element

• Implementation class (JavaBean)

• User interface component

• Function (computed value)

• Trigger

• Access properties

• Auto-increment

• Selection node

• Node category

These properties can be defined in the advanced properties section while editing an element.

Table

It is possible to manually qualify a complex node as a table, by specifying the following properties;

• Primary key , mandatory field where each element in primary key is denoted by its absolute XPath notation,

• Table record labelling , optional fields used for presenting each record inside a hierarchy,

• Activation rules , optional fields used for defining rules on table actions, such as occurrence creation, deletion, etc.,

• Specific filters , optional fields used for specifying filters and displaying only the occurrences corresponding to given criteria.

The Royalties table is defined as below:

Note: Label in hierarchy and Specific filters elements have to be firstly defined in the Business Objects and Rules table.

See also:

• Table definition

Mandatory Element

To specify that an element is mandatory, its mandatory element property has to be set to yes : 

See also:

• Mandatory element definition

Implementation Class (JavaBean)

To specify that a complex element is implemented by a Java class, the Implementation class element has to be associated with a business object firstly defined in the the Business Objects and Rules table:

See also:

• Mapping of datatypes

User interface component

To specify that a element has to be displayed with a specific renderer, the User interface component element has to be associated with a uiBean component firstly defined in the Business Objects and Rules table:

See also:

• UIComponents definition

Function (computed value)

Thanks to the EBX.Platform programmatic extension, we can also implement a specific class in order to specify a default value for a field.

Example: we want to populate the default value of lo_range with the result of a specific computation.

First, in the Business Objects and Rules table, we declare the java class computing the default value . Then, we associate this rule with the lo_range element in the Royalties table:

See also:

• Computed values definition

Trigger

To define a trigger on an element, the Trigger element has to be associated with a Java class firstly defined in the Business Objects and Rules table:

See also:

• Trigger definition

Access Properties

Access properties are defined by the Access properties element:

See also:

• Access properties definition

Auto-Increment

An auto-increment can be added to an element of type int or integer , by specifying the following properties: Start value and Increment step . 

See also:

• Auto-Increment definition

Selection Node

The Selection Node property can be used to identify an element as being a selection node. For example, we create a link between the Authors table and the Titles table:

See also:

• Selection node definition

Node category

The category of an element is specified by the Node Category element:

See also:

• Category definition

Home > Data Model Assistant