Refer to documentation Implementation
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. |
|   |
Close
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. |
| Identifies the data source. As function of the type entered previously, this field can be :
|
|   |
Grid Data source
| Defines the parameter code required for the data source. |
| Title associated to the previous code. |
| Used to enter, in the form of an evaluate formula, the value of the parameter. It should be noted that:
|
| Title associated to the previous code. |
Close
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
|   |
|   |
| No help linked to this field. |
|   |
Close
The source types available in standard are described below.
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.
Both are numerical expressions.
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.
This data source type corresponds to a request, or a SQL request, identified by its code. Two additional setups are then defined :
This data source corresponds to the display of a statistic, where the code is given. The following setups must be given :
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.
This data source type corresponds to the display of a Web page whose address is evaluated from the URL setup, which must be defined.
The source types available as delivered are described below.
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 :
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 :
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 :
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.
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.
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.
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.