Screens

The screen code can contain 1 to 10 alphanumeric characters. The first character must be a letter. It must not be an Adonix-reserved word.

The screen abbreviation consist of 1 to 4 alphanumeric characters. The first character must be a letter. It must not be an Adonix-reserved word.

This checkbox is used to identify whether a screen is never used as is, either interactively or in imports, but only serves as a template for the creation of other screens. These screens are never validated.

The screen is always generated if this field is not assigned. The screen is not generated if this field corresponds to an inactive activity code.

Select a module for the setup.

Use this field to specify whether the screen has to be created in the folder database or not. It is only specified when the module linked to the screen is active in the folder.

Define your screen using one of the following types:

• Header and Tab are used for objects, inquiry management, and in a window entry template.
• Dialog box is used in a window entry template.
• Full screen is used in a table object and in a window entry template.
• Full screen with list is used in a simple object with a single screen and in a window entry template.
• VT screen.

The Header, Tab, and Dialog box types require the additional entry of the number of lines and columns.

Tab titles take one line and section contours take half a line per feature. The maximum dimensions are 28 lines and 112 columns (88 columns if there is a left list).

These two line and column fields are considered as configuration parameters. A customization modification does not require protection by activity code.

Process in which standard (code STD) actions attached to the screen field are searched for. For an XXX object, the standard process name is SUBXXX. This standard is strongly recommended but not mandatory. The process is updated, or created if it does not exist already, at screen validation when a standard action is added to a field. The label for the sub-program is generated during the transfer of the parameter containing the field value. It is up to the developer to write this sub-program.

Process in which vertical (code SPV) actions attached to the screen field are searched for. For an XXX object, the vertical process name is SPVXXX. This standard is strongly recommended but not mandatory. The process is updated, or created if it does not exist already, at screen validation when a vertical action is added to a field. The label for the sub-program is generated during the transfer of the parameter containing the field value. It is up to the developer to write this sub-program. The update of this field does not require protection by activity code.

Process in which custom/specific (code SPE) actions attached to the screen field are searched for. For an XXX object, the custom/specific process name is SPEXXX. This standard is strongly recommended but not mandatory. The process is updated, or created if it does not exist already, at screen validation when a custom/specific action is added to a field. The label for the sub-program is generated during the transfer of the parameter containing the field value. It is up to the developer to write this sub-program. The update of this field does not require protection by activity code.

This block type defines the presentation of the fields inside a block.

• Table: The fields are organized in a scrolling table (horizontally and vertically if necessary).
• List: List of fields independent from one another.
• Text: Display of fixed background texts that do not need to be entered.
• Hidden: Declaration of a hidden list section. Used to include a screen of hidden technical fields used in processes linked to the screen.
• Flash: Used to display portal views provided externally to the function.
• Office: For Excel, Word, or PowerPoint documents.
• Browser: For a web page.
• HTML editor: Reserved for documentation entry.
• Technical: For XSL components.
• Business Intelligence: For the execution of a BO report. Reserved for the supervisor.

One variable parameter is required for Browser and HTML editor block types.

For security reasons, other block types used in version 6 in web server mode are no longer used.

Indicate the section's position using the line.column coordinates of its upper-left corner.

Indicate a minimum number of lines for a table section if necessary.

Indicate a minimum number of columns for a table section if necessary.

Specifies the entry order of sections. Blocks are entered in ascending order when moving by tabulation from one field to another.

It is used in programming to identify a section. For example, write Affzo 10 to display all the fields in section 10.

It is strongly recommended not to modify the rank of a section in the screen definition.

For a List type section, this field indicates the number of characters allocated to the title of each field. It can be 20, 15, or 12 characters depending on the available space.

Use this field to make a block of data optional.

• If the activity code is not assigned, the block is always generated.
• If this field corresponds to a non-active activity code, the fields for this block are not generated.

This field indicates the maximum number of lines in the table for a Table type section.

For a Table type section, this field contains a list of characters, each representing an authorized basic function (if present) in the table. You can select these characters via a selection window. The following functionalities are available:

• K: Previous and next line in entry mode
• A: Cancellation of a line
• D: Cancellation of a group of lines
• R: Addition of lines at the end of the table
• *: Insertion of lines
• S: Cut
• B: Copy
• C: Paste
• T: Loading of all the lines in the table
• ?: Search
• +: Column justification
• =: Automatic record mode
• 1–9: Number of fixed columns (from the first column)

This field defines the name of the variable at the bottom of the table for a Table type section. It is a technical variable storing the number of lines actually entered. It must be defined as editable with the ABS data type in the Fields tab. Define this variable in invisible mode if a table section needs to be hidden.

• This field must be of BLOB type for an Office block.
• This field must be of CLOB type for a Flash, Browser, or HTML editor block.

Representation of the table section in the screen:

• Character: No graph associated with the table.
• Character or graph: Graph and table are alternatively present on the user's request.
• Character and graph: Graph and table are both present on the screen.
• Graph: Only the graph is present on the screen, and the table is not accessible.

For the last three values, a screen for the graphical parameters is accessible from the contextual menu.

This field is used for web services. Fill it in for tabs containing their own left list. For example, the Addresses screen (BPABPR).

The associated table section number is indicated in the list section.

This field is used to select the portal view for Flash sections.

This table provides help for the entry of fields in the next tab. The system retrieves the characteristics of the fields in the listed tables.

Title of the selected reference table.

Available for a Browser type section.

Enables the entry of one to three URLs. You need to declare these in the Screen component function (GESAUR).

Available for an Office type section.

Used to define the Office document type: Word, Excel, PowerPoint, or Universal.

Define the screen field’s name in this column. This code is composed of one to ten alphanumeric characters. The first character must be a letter. A field named FIELDNAME defined in the screen with the ABV1 abbreviation can be accessed by typing [M:ABV1]FIELDNAME.

The field name is generally coded with three characters. These groups are capitalized in the Section coding function (GESACO). It is recommended to follow this standard.

For custom/specific fields, the field name must start with X_, Y_ or Z_.

Indicate the block number where the field should be positioned.

Specify the field number.

• For a Table type block, the fields are placed from left to right in ascending order of their numbers.

• For a List type block, the number indicates the line number in the block (1 = top line). To place several fields on the same line, you must indicate the order in the decimal part.

  For example, 1.2 indicates the second position on the first line.

Specify a title to be placed on the left of the field (or on top in table mode). You can choose:

• One of the three titles for the field stored in the table
• An evaluated label
• Another text

Use this field to position the fields in the same section. It is necessary to imagine a fictional table. The background text and the associated entry field each count as a column.

Specify the number of columns occupied by the field here. W data type fields are expressed in a number of columns and not in a number of characters. The supervisor considers that the last field of a line takes the number of columns necessary to align the line according to the longest one.

Specify the data type for the field. Additional information can be requested depending on the chosen data type.

This field defines the local menu number associated with the field defined on the line.

When a field is of local menu type, it is stored as a numeric value (from 1 to 255) corresponding to the rank of a title in a table named local menu. This numeric value is stored in the APLSTD messages table.

On entry or display, according to the choices made in the user interface, you can see either:

• A title that can be chosen in a scrolling combo box
• A list of buttons

The benefit of this type of entry is that the list of choices is displayed in the user's connection language.

Each local menu number characterizes the list of available titles. For example, local menu 1 corresponds to the No/Yes choice in this order. In this particular case, the user interface can also be a checkbox.

Define the length of a field when this field uses a generic data type whose length is not fixed.

This is the case for A and DCB types. For BLOBs and CLOBs, the maximum storage length must be entered. The codification is as follows:

This information indicates whether the field should be entered or not. There are three possible values :

• Enter: Normal.
• Displayed: The field is never entered but always visible.
• Hidden: The field is present as a screen variable but not entered or displayed.

Indicate for a hidden field if its description should be taken into account in the XML description of the window. The possible values are:

• No transferred: Not taken into account. Corresponds to the V140 technical field.
• All clients: Taken into account by the client and web services.
• Web services: Taken into account by web services only. Corresponds to the V140 hidden field.

For hidden fields in the technical section, this field must be set to All clients, as this technology is used to display XSL graphs.

For other hidden field cases, it is recommended to put Not downloaded, except for specific reasons determined on a case-by-case basis.

Use this field to manage the presence of the field according to the entry mode of a table.

• The Form mode, accessible by right-clicking on the variable at the bottom of the table, allows you to display or enter a table line in a window. All the fields of the line that are marked with the Form or Form and table modes are accessible in one page or several tabs depending on the number of fields.
• In Table mode, only the fields marked with the Table or Form and table modes are accessible.

The actions defined for the fields are active in both modes.

Use this field to indicate whether the screen is to be created in the folder database.

The screen is always generated if this field is not filled in. The screen is not generated if this field corresponds to an inactive activity code.

Activity codes starting with X, Y, or Z make the entire screen specific. It is not affected by folder update.

Indicate the field dimension.

This dimension is automatically assigned in the case of a drop-down table.

This dimension can also be automatically assigned if the field’s activity code includes a dimension.

This information indicates whether the field is mandatory or not.

For an alphanumeric field, mandatory means that the field cannot be empty.

For a numeric or date field, mandatory means that a null value cannot be entered.

Set to Yes to insert a line break after the field, so the next field is on the next line.

Set to Yes for the field to be hidden if the size of the screen is too small. For example, the field can be visible on a desktop display and hidden on a mobile device.

When the data type is associated with an object, this information is used to automatically create a tunnel available in the contextual menu of the field.

This allows direct access to the management of this object.

If set to Yes, an additional field that displays the title of the selected field is added to the right of the field.

You need to configure this field in the Title or Short title field in the General tab of the associated table.

The options depend on the data type (use the search window).

This column defines the options applicable to the field entry. These options are represented by characters that can be concatenated when several options are required.

It is possible to choose these options through a selection window. The available options depend on the field type. A detailed description of all possible options is available. The combination of these options allows the supervisor to apply a specific entry format to the field.

You can set a specific format for the field using Sage X3 syntax through the contextual menu. The existence of this information is indicated by a $ in the field.

This field allows you to enter options or an entry format.

Specify the display length if it is different from the entry length. The entry in this field is scrollable. By default, on alphanumeric fields longer than 30 characters, the supervisor sets a display length of 30 characters.

This entry format is taken into account when no indications are provided on the field format and the data type linked to this field.

Specify an expression used to initialize the field. If the expression is preceded by the * character, the default value is always assigned, even if the field is already initialized.

For an icon field, the value entered here indicates the icon to be displayed. For example:

• 0: New
• 1: Open
• 2: Save
• 3: Cut
• 4: Copy
• 5: Paste

To avoid displaying the icon, leave the field empty.

If this field is not filled in, the field is always accessible to users.

If this field is filled in, a user can only access the field if he is authorized by the corresponding access code.

This possibility to restrict access to a field is reserved for specific or custom fields and does not require protection by an activity code.

The field is defined as being enterable. However, under certain conditions it is not. The entry condition is a logical expression written in Sage X3 syntax.

If the expression is true during entry, the field is entered. If not, it is displayed and its value is saved.

Example: To enter a field only if the previous field is set to Yes, enter [M]ZONEPREC=2.

Use this field to specify the type of graphic object used:

• Checkbox for Yes/No fields (local menu 1).
• Radio buttons for local menu fields with a restricted number of choices.
• Progress bar for numeric fields.
• Icon for alphanumeric fields.
• Photo for BLOB fields.
• Multiline text for alphanumeric, CLOB, or BLOB fields.
• Relative RTF (KR format) for alphanumeric fields. Contains the name of a file without its extension.
• Absolute RTF (KH format) for alphanumeric fields. Contains the directory, file name, and file extension.

On a table section field, the authorized objects are checkbox and icon.

After selecting the graphic object type, it is possible to configure its display by right-clicking and selecting Parameters in the drop-down list. A Graphic parameters window appears.

You can add a specific style on the field by parameter setting.

This is reserved for customization.

Updating this field does not require protection by an activity code.

You can define here a control table to check the entry and, in some cases, to provide a selection of the possible values.

This is reserved for customization.

Updating this field does not require protection by an activity code.

Set of parameters available to load the graph with the table fields.

These parameters are described in the miscellaneous table 915.

Define the graphical representation of the table column.

This information is necessary for graphs:

• Default: The representation defined for the whole graph is used.
• Bar
• Line

You can define the particular actions associated with the field. The possible action types are:

• Before field: Action before any entry or display of the field. For example, it can be used to define the field format.
• Init button: Used to define the button names in the contextual menu.
• Initialization: Used to initialize a field.
• Before entry: Action carried out before each entry. For example, it can be used to set MKSTAT and prevent entry.
• Control: Allows testing the validity of the field.
• After field: Carried out after the control if it is valid. For example, it allows you to assign or display other fields.
• After change: Same as After field, but triggered only if the field has been modified.
• Selection: Triggered by the F12 key.
• Button 1: Triggered by the F9 key. Reserved for tunnels.
• Buttons 2 to 20: The F4 key displays a list of contextual menus.
• Before line: Only for scrolling tables. It allows you to trigger an action each time you enter a line in modification mode.
• After line: Only for scrolling tables. It allows you to trigger an action after each line entry.
• Click: Only for icon fields. It allows you to trigger an action when clicking the icon.

The action code refers to the action table that specifies the sub-program to be called. Three particular codes exist: STD, SPE, and SPV.

These codes indicate that the action is not cataloged but uses a label that is defined respectively in the standard processes for STD, specific or custom processes for SPE, and vertical processes for SPV.

Define the action's execution context:

• Interactive: Online entry.
• Import/batch: Loading in import or batch mode. The actions are executed on the fields after all fields have been filled in.
• Always: Executed in all contexts.

This field is available for specific and vertical developments. You can specify:

• For an SPV action: Whether to deactivate the STD action of the same type.
• For an SPE action: Whether to deactivate the SPV or STD action of the same type.

This part of the screen allows you to define the value of some parameters.

Enter the parameter code here.

These parameters correspond to the actions defined for a field.

For example, for the postcode checking action, the country code and city fields must be provided.

Be careful to respect the parameter type specified in the help.

This part of the screen allows you to define the value of the selected parameter.

Enter the value assigned to the parameter here.

These parameters correspond to the actions defined for a field.

For example, for the postcode checking action, the country code and city fields must be defined.

Be careful to respect the parameter type specified in the help.

This action is available from the Fields tab.

You can automate the creation of fields on the screen based on the tables specified in the Header tab.

This action is available from the Actions grid.

You can access in editing mode the sub-programs of the STD, SPE, or SPV actions related to the SUBxxx, SPExxx, or SPVxxx processes.