Setup > Interactive dashboard > Dashboard views 

The portal view is a single element comprised of a portal page. It is made up of two elements, each entered in one of the function's tabs :

  • A data source that defines an information extraction process from the ADONIX X3 frame of reference. A data source returns the values organized in lines, each line containing columns (the number of columns depends on the data source, the number of lines depends on the data actually extracted when the database is read).
  • A visual component, which describes the fashion in which the extracted data will be presented.

The association of these two elements is accompanied by the definition of a series of setups that are entered in the grids in each tab.

Prerequisites

SEEREFERTTO Refer to documentation Implementation

Screen management

Header

Presentation

Entered in the header is the code that identifies the portal view plus a title.

Close

 

Fields

The following fields are present on this tab :

This code identifies the created records in a unique manner.

  • field APVINTIT

 

Close

 

Tab Data source

Presentation

This tab is used to define a data source, that is the origin of the information to be displayed.

Close

 

Fields

The following fields are present on this tab :

Block number 1

Used to define a data source type. As a function of the type, enter as required an additional code that identifies the source itself and a series of additional parameters defined in the grid at the bottom of the tab.

  • Code (field SRCCOD)

Identifies the data source. As function of the type entered previously, this field can be :

  • a multi-list code (MLT source type).
  • the code of a request, or a SQL request (REQ source type).
  • The code for a statistic (STA data source).
  • The code for a process (TRT data source).
  • empty (the case for the URL and AGD source type, for which only one list of parameters is required).
  • field WDES

 

Grid Data source

  • Parameter (field SRCPARCOD)

Defines the parameter code required for the data source.

  • Parameter title (field SRCPARDES)

Title associated to the previous code.

  • Formula (field SRCPARFOR)

Used to enter, in the form of an evaluate formula, the value of the parameter.

It should be noted that:

  • this formula can be alphanumeric, numeric or date type according to the case, but if the expression type does not correspond to what is expected, there is a conversion.
  • in certain cases, constant values can be given and selected by right click.
  • when several values can be given (for example column numbers), a string of characters is used to express them containing a list of numeric values separated by semi-colons. The successive selection of the columns can in general be made by right click, the list of values then complete it.
  • Description (field SRCPARLIB)

Title associated to the previous code.

Close

 

Tab Visual component

Presentation

This tab is used to define the format to present information (in the form of a grid, of a graphic, of a calendar, etc.). This format is identified by a visual component and the setups attached to it and depends on the data source (some visual components work only with some data sources).

The supplied components and the corresponding constraints are defined in the annex below.

Close

 

Fields

The following fields are present on this tab :

Block number 1

No help linked to this field.

Grid Parameters

  • Parameter (field CMPPARCOD)

 

  • Description (field CMPPARDES)

 

  • Formula (field CMPPARFOR)

No help linked to this field.

  • Description (field CMPPARLIB)

 

Close

 

List of standard data sources

The source types available in standard are described below.

AGD (Agenda)

This type of source corresponds to the CRM calendar.

No code is associated with it.

The setups which must be entered are used to define an inquiry date range.

  • the Number of days before(the current date).
  • the Number of days after(the current date).

Both are numerical expressions.

MLT (Multi-list)

This data source type corresponds to a group of selection lists (such as those found in a left list for an object).

A multi-list code is associated with it.

There is no other associated setup.

REQ (Request)

This data source type corresponds to a request, or a SQL request, identified by its code. Two additional setups are then defined :

  • the first, named FRQ, defines the extraction frequency. The value, which can be selected in a list, goes from 1 (for each use) to 6 (the first time), going through intermediate levels such as 3 (every day). When using the data source, the last calculation date for the request is read to identify whether or not to recalculate before display as a function of the value of this setup.
  • the second, named INITLEVEL, is useful for requests not defined in SQL. It is used to define the level of detail required for the request results display, when this uses breaks (Group column of the requestor). At level 1, only the sections whose level is equal to 1 are displayed along with the corresponding total columns (the others are returned empty). At level 2, the detail of the level 1 and 2 sections is given, plus the following.

STA (Statistic)

This data source corresponds to the display of a statistic, where the code is given. The following setups must be given :

  • the company (CPY) and the site (FCY) on which the query is made (if an empty string is given, everything will be taken). These setups can be selected.
  • the start and end dates for the two possible time intervals (DATDEB1 and DATDEB2, DATFIN1 and DATFIN2)
  • the value of the criteria (1 to 8 maximum, named CRIT1 to CRIT8). The number of criteria for which a different value to the empty string is given defines the depth to which the statistic is displayed.

TRT (Process)

This data source type corresponds to the execution of a standard process, whose name is given. Parameters depending on the process can be requested (by default, it is the 4 standard setups named P1 to P4). The SUBAPSTRT process and the SUBAPSTRTI process document the fashion to create such a data source.

WEB (Web page)

This data source type corresponds to the display of a Web page whose address is evaluated from the URL setup, which must be defined.

List of the visual components available as delivered

The source types available as delivered are described below.

FAG (Instant Diary)

This visual component can only be associated with the CRM diary (AGD source). It displays in the form of a calendar, the fields coming from the diary with the interactions linked to the specificities of the CRM diary. The associated setups are :

  •  the type of calendar (FCCTYPE), which values can be selected. The possible values ar 'XMONTH' (mensual calendar), 'XWWEEK' (weekly calendar), 'XDAY' (daily calendar).
  • the column number of the fields of type action, chrono action,, start date, start hour, end hour, BP, contact, category, object, Actual flag These fields are displayed in the exact extraction order of the AGD data source ; it is therefore not normally possible to modify the default columns (1 to N) displayed with regard to these setups, except to exclude certain information from the display, in which case the value 0 will be entered in the column. For example this can be the case if the start date is equal to the end date or if the notion of time is not used.
  • the indicator that defines if the calendar selector used to pass between one or other of these presentations is present (2=Yes, 1=No).

FCA (Calendar)

This visual component is used to display the dated events in the form of a visual calendar. It can only be used with the following data sources : process, request.

The associated setups are :

  • the type of calendar (FCCTYPE), which values can be selected. The possible values are 'XMONTH' (mensual calendar), 'XWWEEK' (weekly calendar), 'XDAY' (daily calendar).
  • the indicator that defines if the calendar selector used to pass between one or other of these presentations is present (2=Yes, 1=No).
  • The column number of the data source indicating respectively the start date and hour and then the end date and hour. This information must not necessarily be entered, except for the start date, which is used to position the data on the calendar. It is possible to select directly the fields via right click if the associated data source is a request.
  • the column number from the data source specifying the icon used to symbolize the event (fields are optional).

FGR (Instant graphics)

This visual component can be associated with the statistics (data source STA), with the requests (data sources REQ) or the processes (data source TRT). It presents one of the amounts arising from the data source in the form of a graphical representation, with as its title one of the character elements arising from the data source. The associated setups are :

  • the type of graphic (FGGTYPE), which can be selected via right click in following list: 'XLINE' (graphic by line), 'XBAR' (graphic by bar), 'XAREA' (graphic by area ), 'XPIE' (graphic by sector).
  • the numbers of the columns of the fields Value (FGCVAL) can be displayed. If there is only one column, it number is given directly, but if there are several, they must be in a character chain, divided by a semi-colon. Thus the result can be a syntax of type "4;7;3;8"
  • the column number corresponds to the value displayed by default (FGCDEF). If this field is not entered, the first value is used.
  • the column number of the field named (FGCLABEL) is displayed. It should be noted that with a STA source, the first amount is column number 3, column number 1 being the codes stored in the statistical aggregation table and column 2 being the title extracted from the table linked to this code (only these two columns can be used to enter FGCLABEL, but all the other columns are numeric in this case).
  • the flags that define if the graph selector (FGCSELG) used to pass from one representation to another and the value selector (FGCSELC) for presenting one of the numeric columns present in the list of columns, are present (2=Yes, 1=No).

ML1 (Standard multi-list)

This visual component is used to display the data in the form of value lists (each of the lists being identified by a band, the action of clicking on the band triggers the display of the list contents). It is only used with the MLT type (multi-list) data sources and there are no setups.

On using this component, it will be noted that the under-lined fields that correspond to the principal keys of the listed records can be used via a single click, to tunnel to the corresponding record.

RE1 (Standard request)

This visual component is used to display the data in the form of a grid of values. It is only used with the data source of the type REQ (request) and it does not have setups.

Contrary to the more generic component TB1, it authorizes the unfolding of successive levels of the request from the level at which it is displayed (INITLEVEL setup), by clicking on the icon present on the grid title band.

On using this component, it will be noted that the certain fields can be under-lined. In this case, it is the principal keys linked to the on-line tables in the request. A single click on the field is then used to tunnel to the corresponding record.

ST1 (Standard request)

This visual component is used to display the data in the form of a grid of values. It is only used with the data source of the type STA (statistic) and it does not have setups.

Contrary to the more generic component TB1, it authorizes a zoom on the request lines from the level in which it is displayed (INITLEVEL setup), by clicking on an icon present in the grid title band.

On using this component, it will be noted that the certain fields can be under-lined. In this case, it is the principal keys linked to the on-line tables in the statistic. A single click on the field is then used to tunnel to the corresponding record.

TB1 (Standard grid )

This visual component is used to display the data in the form of grids. It can be used with the AGD (diary), REQ (request), STA (statistic) or TRT (process) data source types and there are no setups.

Contrary to the ST1 and RE1 components, it is not used to either zoom or unfold. It is therefore suitable when the data should be displayed in a list at a given level without allowing the display of any sub-detail even if it exists.

Specific Buttons

Error messages

The only error messages are the generic ones.

Tables used

SEEREFERTTO Refer to documentation Implementation