Refer to documentation Implementation
Presentation
If the function is opened without having selected a specific query, a preliminary entry screen makes it possible to choose it.
A screen containing a single tab opens, in which there is a group of columns containing the data arising from the query interrogation (they are stored in the ALISTER table).
In the header there is the information relating to the last query execution.
The execution can be carried out by the key, which makes it possible to trigger a refresh in a generic fashion (it is also used for the left lists), or using File/Refresh. It can also be carried out by entering the criteria with the help of the appropriate button.
In order for the execution to happen, it is necessary that the user be authorized (this makes it possible, when the queries are shared, to only authorize inquiries on queries already carried out).
In the table that follows, the columns coming from the query are found with detail lines. By positioning the cursor on a line, it is possible by right click, to zoom onto the records relative to the information which keys are displayed on the line. For instance, if there is a query giving by country, then by customer, then by order line, the detail of the products and the corresponding quantities, it is possible to zoom onto the customer record corresponding to the customer on the line, on the country record, on the product... (but not onto the order if the order number does not appear in the line).
It is also possible to navigate from page to page with the radio buttons situated in the top menu line, and using the buttons at the bottom of the page described below.
Close
Fields
The following fields are present on this tab :
Block number 1
| This code is used to identify a request. |
| Title associated to the previous code. |
| It specifies the execution time (in seconds) necessary to the last request execution. When a long execution is in progress, the number of seconds elapsed is displayed as the execution progresses. |
| This field defines the current level of detail and the maximum level number (the maximum level is used at the start: 4/4 is displayed if, for instance, the maximum level number is 4). The level management buttons make it possible to then navigate from one level to another. |
| It indicates the date and time of the last generation. These fields are empty if no generation has been made yet. |
|   |
| It defines the code of the last user who executed the request (when the request is shared, the user can be different from the current user). |
| It specifies the number of lines created by the request when it was last executed. When a long execution is in progress, the number of lines being found is displayed as the execution progresses. |
| It indicates a page number and the maximum number of pages on which the request is displayed (this depends on the maximum number of lines displayed in the screen, parameterized in the request definition). |
Close
Action icon
By right click on the lines, a group of zooms can be obtained, depending on the context linked to the query, to perform a tunnel up to the data related to the query.
Close
Used to change the query. |
Used to re-launch the execution (it is equivalent to a refresh). |
It makes it possible to modify the query criteria. By validating these criteria, the query is executed, then its result is displayed. |
It makes it possible to create, on a client workstation, a file in the csv format (usable by a spreadsheet), It is simply necessary to give the file path (without specifying the network path, the client workstation being used by default). It is also possible to create the file on a network server (provided that this server includes an Adonix run-time), thanks to the server@path syntax. The format of the created file is defined by the values of the RQTFMT and RQTSEP setups. |
In addition to the generic error messages, the following messages can appear during the entry :
The attempt to create a file in the csv format has failed.