Screen components

This function is used to manage the URL and the html pages that can then be used in the screens containing a browser section, in order to display :

  • either a web page, by specifying a code of the type URL
  • or a HTML page described in this dictionary, by specifying a code of the type HTML.

This function is also used to store the XSL processes. Associated with the sections of the grid type, an XSL is used :

  • to present in a graphical manner (with graphs not pre-viewable in flash)
  • to manage the interactions (of the type sliding - replace or other) that are used to update the grid in a graphical manner.

This way of working offers an important opening with a wide field of possibilities to the parameterization of software developed from the basis of the X3 technological platform.

Each XSL graphic is associated with a grid, therefore an [M] class that will be displayed or not according to the parameterization of the screen.

The planning and nomenclature graphs are directly modifiable thanks to the interaction process indicated in this dictionary.

As standard, it is planned to ship five XSL that are :

  • APLANM : monthly planning represents one or more activities on a calendar month with 1 to 4 months being displayed at a time.
  • APLANY : annual planning represents one or more activities over a calendar of 12 consecutive scrolling months.
  • ANOMH : horizontal nomenclature representing a nomenclature or an organigram.
  • ANOMV : vertical nomenclature representing an arborescense of the type windows file explorer.
  • ARADAR : the radar is used to display a group of numeric values.

A detailed appendix details these five XSL shipped as standard.

Prerequisite

See also Refer to documentation Implementation

Screen management

The header is used to identify in a unique fashion each element in this table. It is also used to enter all the information necessary on the components of the type URL.

Code (field CODURL)

Code identifying the current record.

Link type (field TYPURL)

Field used to determine the three graphical interfaces :

  • URL : is used to display in a screen, by browser section, a web page, by specifying an URL.
  • XSL : is used to display in a screen, by grid section, a graph, a nomenclature or a radar ; these elements being the based on a grid.
  • Html : is used to display in a screen, by browser section, a web page described in the dictionary.
Description (field ZINTIT)

Component title. It is notably displayed on the screen, when this latter proposes a URL choice or HTML pages.

Evaluated title (field INTEVAL)

Used to have a title for the URL, HTML page or XSL element, variable as a function of a context. If it is entered, the evaluated title is displayed in the place of the title, during the display screen in which this component is placed.

XSL type (field TYPXSL)

Used to refine a XSL link type.

As standard, there are three XSL process types :

  • Planning
  • Nomenclature
  • Radar

The "Miscellaneous" is reserved for specific/custom developments.
Parameter code (field PARXSL)

used to associate XSL with a parameter set defined in miscellaneous table 915. It will intervene in the parameterization of the screens during the characterization of the fields.
Module (field MODULE)

[object Object]

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
Address (field URL)

URL address. It can be evaluated. Examples:

  • http://www.sage.com/
  • ="http://www.sage.com"
  • =ADR1   ADR1 being a variable to be declared and to be loaded in the process linked to the function in which this URL will be used.
Location (field PLEURL)
Security level (field SECLEV)

Tab Definition

This tab is constructed from a unique field that is used to enter the description of a HTML page or a process in XSL language.

field XSLCLOB

Used to write the XSL code or the HTML page code.

Tab Parameters

This tab is used to enter the parameterization used by the XSL process.

Grid Local menus

Code (field UCOD)

The association of a local menu with a parameter is used to supply the XSL component with a group of labels, in the user language, that can be used in its functioning. These menus are referenced to the generation of the window, in a structure that is used by the Web component. The code associated with the menus is not modifiable, but it is possible to change the local menu numbers to make other labels appear. It is possible to define up to 5 local menus in this way.

Example : For standard XSL with monthly planning, the process uses the following three local menus :

  • 9001 : months of the year
  • 9833 : days of the week
  • 9834 : abbreviation for the days in the week

Each local menu is transferred to the XSL process by a code that is fixed.

Example : For the standard XSL for monthly planning, the codes are : MONTH, DAY, ABRDAY.
Local menu (field UMEN)
Description (field ULIB)

Interactions

Script (field UPRG)

The interactions make it possible for the user to intervene in the graph. According to the XSL, they can take different forms - drag/drop, delete, move etc. The XSL process can make successive calls to one of three supervisor sub-programs written in the Adonix language.

Example : For standard XSL for monthly planning, the process uses the MAJPLAN sub-program in AMAJPLAN. It is used to assign an activity to a planning slot. A day can be subdivided into 4 slots.
Subpro (field USPRG)
Description (field UINTIT)

Grid Parameters

Code (field UPARCOD)

The parameters corresponding to the values that characterize several options that are used to reuse the XSL in the different contexts. A description and a default value are associated with each parameter. This value by default will be proposed and can be modified, in the screens using XSL.

Example : For standard XSL with monthly planning, the process uses the following three local menus :

  • NBMONT : Number of months displayed (1 to 12) 
  • MENACT : Local menu activity type (9837 in standard. possibility of a max of 8 choices in this menu)
  • SDATA : Graphic () update
  • PINTER : Interaction program (AMAJPLAN in standard) 
Description (field UPARLIB)
Default value (field UPARDEF)

Specific Buttons

Copy

This button is used to copy this information to another folder.

Utilization

This button is used to list the usage in a log file.

Error messages

In addition to the generic error messages, the following messages can appear during the entry :

Code already defined in line xxx

the code entered must be unique in the table.

Non-existent menu

the local menu number entered must exist in the table of messages and local menus AMENLOC.

Non-existent process

the process must be referenced in the sub-programs table ASUBPROG.

Non existent sub-program

the sub-program must be referenced in the sub-programs table ASUBPROG.

Tables used

See also Refer to documentation Implementation