Data models

• Template code (field MODELE)

Code identifying the current record.

• Description (field ZINTIT)

• Active (field ENAFLG)

Select this check box to activate the current record.

Disabled records keep their content and setup but cannot be used by recalling their code:

• On other records such as documents and settings
• On mass processes

The authorizations for a given function can prohibit the creation of an active record. In this case, the check box is disabled by default. It can only be modified by an authorized user or through a signature workflow.

• Activity code (field CODACT)

An activity code is used to:

• Make an element optional in the dictionary if the value associated with the activity code is null
• Identify the specific/custom elements if they are marked with a code starting with X, Y, or Z
• Size a maximum number of lines when the activity code marks elements from a grid

If the activity code is disabled:

• The marked element will not be useable
• The associated code will not be generated nor activated

• Module (field MODULE)

Select a module for the setup.

Use this field to specify if the screen has to be created in the folder database. This is the case when the module linked to the screen is active on the folder.

• Setup templates (field FLGAPH)

Specifies that the data template is linked to the setup template.

• Workflow (field FLGWRK)

Specifies that the data template is linked to a workflow.

• Deliverable definition (field FLGADLV)

• Main table (field TABREF)

It identifies the main table from which other tables are read via direct links or through cascade. This table is supposed to be on line if the model is used in a Workflow rule of the Manual type. In the case of a Manual Workflow, it belongs to the join that is open and run through upon Workflow execution.

• Linked table (field TABLNK)

It identifies the table linked to the table of origin.

• Abbrev. (field ABRLNK)

It corresponds to the abbreviation under which the linked table is open.

If this field is not populated, the default abbreviation of the table is used. It is particularly useful to enter an abbreviation if the table appears several times in the grid, since several linked lines in the same table need to be on line simultaneously.

• Origin table (field TABORI)

It identifies the main table at the origin of the link described on the current line. It may be the main table, or one of the linked tables on the previous lines.

• Abbrev. (field ABRORI)

It corresponds to the abbreviation under which the linked table is open.

If this field is not populated, the default abbreviation of the table is used. It is particularly useful to enter an abbreviation if the table appears several times in the grid, since several linked lines in the same table need to be on line simultaneously.

• Key (field CLELNK)

It defines the table key code used to read the linked lines. By default, the first key of the table is used.

• Type (field TYPLNK)

This type takes on one of the two following values:

• 1,1 : it means that for each line in the table of origin, only one line in the linked table is read (this line is defined by the key expression).
• 1,N: in this case, several lines in the linked tables can be read. They are defined by the key expression, that can be incomplete if it is divided into several parts (those lines whose entered key elements correspond to the given value are run through).

• Link expression (field EXPLNK)

This field is defined as one or more calculated expressions separated by a semi colon. Each expression is evaluated, and the result used to identify the value of the key used to perform the join. When multiple joins are authorized, only the first elements of the key can be given.

In the expressions, constants can be used, as well as fields coming from the tables previously defined in the link list.

• Selection expression (field EXPSEL)

This selection formula is applied on the table defined in the Linked tablecolumn, and allows to filter that data in the template Caution, these conditions are not applied for the indexation process. The syntax is the script syntax of Sage X3 used in the Filter instructions.

• Company field (field FLDCPY)

This field defines the current company, from the Workflow rule viewpoint. In this way, when the allocation rule is available by company, the proper rule is used depending on the value of the field.

• Site field (field FLDFCY)

This field defines a current site, which enables the current company to be derived from it (if it is not defined in the company field), from the Workflow rule viewpoint. In this way, when the allocation rule is available by company, the proper rule is selected depending on the value of the field.

• Legislation field (field FLDLEG)

This field is used to filter the records related to a legislation during the patch creation or the patch integration carried out by the ACOPAPH function (patch templates).

• Option title (field AZOPTLIB)

• Option code (field OPTCOD)

• Option condition (field OPTCND)

• Error message (field AZOPTERR)