Object Definition Syntax › OBJECT Statement › FACTORY Optional Statement › Optional Statements (FACTORY Optional Statement)

Optional Statements (FACTORY Optional Statement)

At least one of these optional statements must be specified:

REL_ATTR name

Identifies the attribute that will represent this object when it is referenced (used as an SREL) by another object. Here is an example:

REL_ATTR id ;

REL_ATTR name, srel_name (attr1,attr2,…)

Identifies the attributes that will represent this object when it is referenced (used as an “named” SREL) by another object. where

srel_name

matches the "named" SREL name

attr1

is mapped to by the first attribute in the "named" SREL attribute list.

attr2

is mapped to by the second attribute in the "named" SREL attribute list.

DISPLAY_NAME name

Defines an external name for the table.

DISPLAY_NAME "Call Request" ;

COMMON_NAME name

Defines the attribute to be displayed in drop-down lists or when the user double‑clicks a field, as well as when the tag does not specify a complete attribute. In the first example, the value for sym appears on the window instead of the value for the REL_ATTR. The second example allows you to specify a tag as cr.customer instead of cr.customer.combo_name.

COMMON_NAME sym ;

COMMON_NAME combo_name ;

FUNCTION_GROUP name

Indicates which security access group is permitted to access the object. For example:

FUNCTION_GROUP "admin" ;

STANDARD_LISTS { }

Creates lists of objects that are kept in a cache and can be displayed on list or select windows. The parameters determine whether the lists are master lists or restricted lists, whether the objects included in the list must meet specified conditions, how the lists can be sorted, and what additional attributes are stored. Refer STANDARD_LISTS Optional Statement for the description of the syntax.