Create Requests

This code is used to identify a request.

Use this field to assign a description to each record.

This title, which describes the record, is used in some screens or records when there is not enough space to display the long title.

Select this check box to activate the current record.

Disabled records keep their content and setup but cannot be used by recalling their code:

• On other records such as documents and settings
• On mass processes

The authorizations for a given function can prohibit the creation of an active record. In this case, the check box is disabled by default. It can only be modified by an authorized user or through a signature workflow.

This indicator defines the fashion in which the representation of the data will be made in the screen. The possibilities offered are as follows :

• Character:  the data is uniquely represented un the form of a grid.
• Char or Graph: the data are presented in the form of one or to modes. The default mode is determined by the field Default display defined in the graphical parameters of the record.
• Char and Graph: the data is presented in the both modes simultaneously. The graphical position  with respect to the grid is determined by the field Position for the Graph tab.
• Graph: the data is uniquely presented in the form of a graph.

Used to organize the relationship between the character and the graphic, when the presentation mode for the data allows both. According to the case :

• if the representation is Char or Graph, the default value is chosen for the representation.
• If the representation is Char and Graph, the position of the graph is given with respect to the data grid.

This is the name of the table from which the information will be extracted. An entry is mandatory even if you plan to display an expression combining several fields related to different tables, or to no table at all. In this case, just enter the code of any one of the tables used in the inquiry. (This implies that the first line of a User-defined Inquiry cannot be such an expression.)

This is the code of the Field that contains the data that will be displayed in the inquiry. Your selection is conditioned by the specific table that you chose in the previous field.

If you leave the field blank, you will have to enter an expression in the next column.

Note that, if the field is indexed (i.e., has several occurrences, such as the CCE field within the BPCUSTOMER table), you will have to reference a specific index, such as CCE(2). The indexes start at 1, not 0, so if you have 4 Dimensions defined in your system, you can enter CCE(1) to CCE(4), but not CCE(0) nor CCE(5).

Used to define the title of the column as it will be displayed on the execution of the request.

By default, when a field in a table is used, its title (as it is stored in the dictionary) is proposed. In a multilingual context, this title is displayed during the execution in the connection language of the user, the dictionary texts being managed in all the connection languages.

This assumes that it is possible to define the translations for a modified title or corresponding to an expression calculated for which no translation has been defined.

In translatable fields such as this one, you can enter a description in a language other than the connection language: Click On line translations from the Actions menu.
 For further information, see On line translation of descriptions.

This is the Expression, composed in the Adonix Language, with the help of the Formula Editor if required, that must be entered if no Field name was assigned on the inquiry line. The expression can integrate fields from any of the available tables, plus constants, operators, functions, and other variables that are needed.

An expression is limited to 200 characters, so, for complex expressions, you may have to use an abbreviated syntax (e.g., specify a table as "[SOH]" instead of "[F:SOH]").

This data type is used to specify how the data will be presented.. In the case of a field, the type associated with the field is proposed by default (but can be modified). In the case of an expression, it must be specified (it can be a generic type such as a string of characters A, a local menu M, a short integer C, a date D, a decimal DCB, a long integer L...). In the case of a string of characters, its maximum length will be specified in the Length field that follows ; in the case of a local menu, both the length of the display and the local menu number to be used are specified. If the data type used is linked to an object, it will be possible to use a tunnel to the object management during the enquiry.

Used to define the length of a field when this field uses a generic data type where the length is not fixed. This is notably the case for the types A and DCB.

Defines the local menu number associated with the field defined on the line.

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

On entry or on display, the following are displayed according to the choices made in the user interface :

• either a title can be chosen in a scrolling list commonly called a combo box
• or a list of buttons.

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

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

When you execute a User-defined Inquiry, you may often want to change the data selection criteria, so that you end up seeing exactly what you want, and not all of the data. To do this, simply enter "Yes" for those critical fields.

When the inquiry runs, it will first pop up a criterion entry window in which you can set beginning and ending values (or leave them blank). Since the criteria are associated with known fields, the Selection Window will allow you to choose proper values.

It is advised that you have at least one field in each inquiry with the Range set to "Yes", so that the Execute Inquiries function (EXEALH) will enable you to initialize and to refresh the data that is displayed on the screen.

This field can be assigned only if the line contains a numerical data element. If set to "Yes", it allows you to roll up totals to higher "Groups" in the inquiry display (i.e., at higher break levels).

But note that while this works fine for "raw" data (such as sales revenue), it is inappropriate to accumulate certain kinds of calculations (such as a percentage like gross margin %), since the total display will NOT be recalculated on the total lines, but rather, will just show an uninterpretable total.

This field allows you to sort the data elements that will be displayed in the inquiry - in the order in which they appear on the lines in this table. Sorting may be either done Ascending or Descending.

You must set this field to a value other than No to be able to Group data (since otherwise the data would be unorganized). But, in a simple inquiry with no grouping (no roll up capability), you can sort data but not necessarily group it (e.g., for a listing of sales orders).

This field is used to create a break level. If this field has the valueYes, a group of fields that follow can be made by break in the current field and potentially any totaled values will be displayed at the group level.

This field can only be entered if a sort has been defined on the current line (Ascending or Descending according to choice).

For example, if a list of users is defined by profile, a break by profile can be used to group on a single line all the users linked to a profile and to display totaled data linked to the group (for example their number of there is a field equal to 1 that is accumulated).

Corresponds to the level of detail desired for the display of the information.

Level 1 signifies that the information is displayed at level one of the aggregation (the highest) and all the successive levels, level 2 signifies that the information will not be displayed at level 1 but at level 2 and all the more detailed levels etc. The highest level therefore corresponds to the most detail level of the inquiry, that which is displayed by default when launching the inquiry.

This level is assigned by default to 1 on the first line and incremented each time a break is requested (Group=yes) for the previous field. It can be modified in order to display an amount at a different aggregation level. For example, when sorting and grouping the information by a code such as the user code and the user name is required in the next column, it is clear that this name must be displayed at the same level as the user code and not only at the more detailed levels.

This field can only be entered if the representation mode selected in the header is not Character. It is used to specify the fashion in which the graphical representation will be used.

It can take the following values:

• None or Label if the line field is of the type alphanumeric. The field using the value Label will be used as the graph title. Warning, only a line in the grid can take this value ; if it is already present on a line, it will be necessary to first modify the value of the line carrying the value Label in order to return the value None before being able to assign this value to another line in the grid.
• None, Value or Default if the field is of the type numeric. The rule is as follows :
• None signifies that the field will never be presented in the graph.
• If the graph defined in the last tab is used to make several series appear, all the series corresponding to the fields marked Default will be displayed (provided they haven't already).
• if the graph in the last tab is not used to make a series appear, the column corresponding to the first field marked Default will be displayed (this will be the first if none has been declared before).

This field can only be entered :

• if the representation method chosen in the header is not Character.
• on the numeric fields where a value will be displayed.

It is used to manage the graph combinations if the graphic type defined in the graphical parameters is used to make several series appear, independently of different types (it is ignored in other cases). In practice, the usable combinations are as follows :

• Type = Multi graph, Default graph=Lines, Representation=Multi
• Type = Multi graph, Default graph=Bars, Representation=Multi

The rule is as follows :

• Default signifies that the graphical presentation of the series corresponds to the default graph of the last tab (Bars, or Lines in this case).
• Bar or Line is used to force the corresponding presentation method in question.

Here is entered the setup value in the form of a calculated expression involving variables linked to the launch context. If the setup is a start-end range, two values must be entered.

Specify the maximum number of lines returned by the query. The default value is 0. The maximum number is 100.

The maximum number of lines corresponds to a query parameter (maxrows) that stops the search once the number of lines meets the conditions that have been found in the database (these lines will then be sorted, but the database does not guarantee that the N lines found are the first N in the sort order). This represents an optimization used to limit the database load.

Makes it possible to fix the first x columns of a grid in the case of horizontal paging.

Allows the stopping of the search after this period of time. (expressed in seconds) This makes it possible to avoid waiting too long a time, namely in the case where a new query is being set up.

Note: Contrary to the maximum number of lines, this information is not transmitted to the data base. The maximum time can be exceeded if the duration of the inquiry is too long.

It defines the code of a report that will be associated with the File / List function from the query inquiry. If this is not entered, the report ALISTE is used, which will submit a default page format. It is possible to duplicate this generic report (in principle it will then only be necessary to modify the page format) to create reports perfectly defined for the query thus defined.

The report code entered here can be associated with a set of print codes via the dedicated function.

Used to enter selection criteria, which are logical expressions applied to table fields, and that can include constants, functions and operators. Only the lines in the table that meet these conditions will be extracted. The formula editor is used to simplify the writing of such expressions.

It is necessary to define here the links that have not been defined in the dictionay or which have to be used in priority. The link structure must correspond to the key of the file to be linked. It must have as many fields separated by semi-colons as key parts. In effect, the exact syntax is the following:

[F:ABV1]CLE=expression1 ; expression2..., where:

    [F:ABV1]CLE is the key of the linked table. Using the right click provides access to the Choose a table function, which submits the list of all the tables presented in the first tab. Selecting a table leads to the display of the first index in the table. If another index is required, the function Choose an index is also accessible via right click, which will make it possible to choose from amongst the list of all the indices for the table previously selected.

    expression1, expression2 represent the expressions used to give values to the various fields of the previously defined key (if the key has only one part, there is only one expression, otherwise, the expressions are separated by a semi-colon). There is also the Choose a field function, used to enter the various values of the key with fields of one of the tables concerned. After the choice of the key, which displays the number of semi-colons defining the sections of the key to be entered, this function is used to successively fill all the missing sections. It should be underlined that constant key parts can be defined.

From the database perspective, this syntax defines left outer joins. It should be noted that a second syntax enables strict joins to be created (which can be interesting from a performance point of view). A tilde (~) is then added to the syntax which becomes:

[F:ABV1]CLE=expression1 ; expression2...

Used to manage the display of a query in inquiry mode, with the following behaviors:

• Normal query: the result of the query is displayed if the query has already been viewed by the user. In effect, if the box is not checked, each user launching the query creates a set of data that belongs to them and which cannot be viewed by anyone else.
• Shared query: the result of the execution of this query by a user can be viewed by other users. Shared queries are useful in that when a large query is launched at a given moment by a single user, a group of users can then access the common information. It is recommended, for this type of query, that only one user can run the query, the others having inquiry access. In addition, it is preferable to run this type of query in batch mode if it is particularly large; the corresponding batch task code is called CALALH.
• Recalculated query: the result of the query is never displayed automatically. It is necessary to press on the button to refresh or enter the criteria. This type of query is interesting in that it makes it possible to avoid reloading data if they are known to become rapidly obsolete.

Used to make a classification criterion available for requests.

This access code makes it possible to prohibit access to the current record for some users.

If the field is populated, only users that have this access code with read access rights (and write access rights respectively) can view (or with write access rights, modify) the record.

The execution right controls who can execute the query in question (by refreshing the query or by modifying the parameters and then re-running it).

Used to determine the authorization filters applied to the forming of the query. These filters are the filters by site, by role and by access code.

The filtering principles are the following:

• The object code is used to define the access code and site code fields on which the filter will be applied.
• This filter is then carried out based on the authorized sites and access rights assigned for object management to the user running the query.
• Similarly, the filter on the roles, defined by the object code, is also applied.

This of course supposes that the table on which the filters are carried out is part of the generated query. What is meant here is the table containing the access code and site code fields, and, when necessary, the field defined by the roles assigned to the user. This is not necessarily the main table in the query: for instance, a query on document lines can be filtered with respect to authorizations given for the fields of tables linked to the document header.

Warning, these filters are only applied during the running of the query and not during inquiry. This is important if the query is shared, for instance, or if the filters by site for a user have changed between the time when the query has been calculated and the time when it is viewed.

Used to link the authorizations to access the query with those authorizations granted on the function.

The principle is as follows: upon entering the query, it is checked that the linked fucntion is authorized to the user (for at least one site, if the authorization on said function is granted by site). This is checked only in the case when this query is not shared.

In effect, if the query is shared, it is admitted that the authorizations of the person that run the query are applied and shared with all those that have the right to view it. It is therefore necessary to be very careful when defining the authorizations of the shared queries if they concern sensitive data. This is done using the access code located in this tab.

This field is used once there is more than one numeric value in the grid that is likely to be presented in a graphical form. It can take one of two values :

• Single graph : in this case, only one column of values is displayed at a time (a selector is used to make to choice)/
• Multi-graph : in this case, all the columns are displayed, combined according to the parameter defined by the parameter Representation.

When several series are presented in the graph (provided that the presentation of all the series is identical and is not by sector type), it is possible to specify how the series values are combined in the display, by entering the following value :

• Multi is used to present the values of each series side by side (one color by series)
• Cumulative is used to present the values in a vertical total.
• Comparative is used to present them in a relative comparison (the height of the graph is constant).

Defines the graphical representation used for the data to be presented (from the choices Bars, Lines, Area, Sectors). An image is displayed as a function of the choice made illustrating the type of presentation obtained.

If only one series of values is available, the graphical representation is by default fixed by this parameter.

If several series of values are presented, it is possible to mix the presentation modes (one series in the form of bars, another in the form of lines for example). In this case, each series of values is represented as a function of the field Representation located in the grid of fields :

• if it is Bar or Line, this representation mode is used for the series of values concerned if it is compatible with the default graphical representation (it is not possible to mix sectors with bars or lines).
• if it is Default, the default graphical representation for the series is used.

When used, if the representation of the series is homogenous (that is there is only one series in the graph), there is a graph type selector for the user to select a different mode of presentation.

Image explaining the information previously entered.