A preset is created for use on a particular form. Enter this form here.

Every preset has a program code, which allows you to grant rights to the preset.

By default, the preset has the same program code as the form for which the preset was created. This means that the user will automatically have the same rights to the preset as to the form to which the preset relates.

Note: To be able to use a preset, you need Read rights to a program code for a preset.

Example

Both the Sales department and the Service department need data from the Sales orders form. If the service employees are only allowed to view service orders, and the sales employees are only allowed to view sales orders, you could specify two presets (create two lines) for the form, and grant one department rights to the program code of one preset, and grant the other department rights to the program code of the other preset. This would result in two lines on the Presets form, both with the same program code for the Sales orders form (700000), but each with a different preset program code. If both departments are allowed to use both presets, the form program code will be the same as the preset program code.

The preset code must be numeric and must be a number higher than 10,000. Preset codes lower than 10,000 are reserved by Isah.

The description of the preset is displayed in the list box containing the presets of the form to which the preset relates.

Select this check box if there is stored procedure on the SQL tab. You can use the Stored procedure field to determine the sorting column and then to select this column in the sorting field on the form.

If the Stored procedure check box is selected, it is assumed that the result set has been sorted on the first column. This column will therefore be automatically selected in the sorting field.

If the Stored procedure check box is empty, it is assumed that the result set has been sorted on the ORDER BY component from the dynamic SQL statement. This ORDER BY component is determined and then automatically selected in the sorting field. If the SQL statement does not contain an ORDER BY component, it is assumed that the result set must be sorted on the first column.

Example 1

A result set is retrieved using a stored procedure, and the Stored procedure check box is empty or selected:

SQL statement:

Select A, B

In this case, the result set will be sorted on A, as this is the first column in the result set. The sorting field will contain 'A' as the sorting value.

Example 2

A result set is retrieved using a dynamic SQL statement, and the Stored procedure check box is empty:

SQL statement:

Select A, B

Order by B

In this case, because of the ORDER BY component, the result set will be sorted on 'B'. The sorting field will contain 'B' as the sorting value.

Example 3

A result set is retrieved using a dynamic SQL statement, and the Stored procedure check box is selected:

SQL statement:

Select A, B

Order by B

In this case, because of the ORDER BY component, the result set will be sorted on 'B'. Because the Stored procedure check box is selected, the sorting field will display 'A' as the sorting value, as 'A' is the first column in the set.

Every Isah form to which presets can be applied has a list box containing the valid presets for the form in question. Select this check box to make the current preset is visible in the list box of the form to which the preset relates.

If this check box is selected, the preset is a standard Isah preset. These default presets cannot be changed or deleted. You can copy or change the SQL statement, and save it under a new preset code.

Tip: If the default preset already contains the Dynamic SQL preset, you can use it to find the mandatory fields. Dynamic SQL contains the same SQL commands as the stored procedure. If this is not the case, you can use IsahMonitor to find information such as the stored procedure that has been used.

Whether or not a user may export the list of a preset depends on the user's rights. The list export function has its own program code (100009999). Users with rights to this program code can export every list. The value of the Allow list export field is not relevant in this case. If a user does not have rights to program code 100009999, you can use the Allow list export field to specify for each preset whether the user may export the list.

Whether or not a user of a preset may create a print preview depends on the rights assigned to the user. The creation of a print preview has its own program code (100009992). Users with rights to this program code can create print previews of any preset. The value of the Allow print preview field is irrelevant in this case. If a user does not have any rights to program code 100009992, use the Allow print preview option for each preset to indicate whether the user can create a print preview.

Whether or not a user of a preset may create a pivot table depends on the rights assigned to the user. The creation of a pivot table has its own program code (100009991). Users with rights to this program code can create pivot tables of any preset. The value of the Allow pivot table field is irrelevant in this case. If a user does not have any rights to program code 100009991, use the Allow pivot table option for each preset to indicate whether the user can create a pivot table.

The advanced preset options provide some additional options for each preset, such as the possibility of sorting data by multiple columns and grouping data. Use this option to specify whether these options should always be enabled or disabled for the new preset. For the 'Depends on user setting' option, the software checks the setting of the Advanced options by preset pane on the form to which the preset applies. This pane, which can be opened from the View menu, enables you to specify for each preset whether the advanced options should be enabled or disabled.

It is recommended to enable the advanced options by preset only if they will actually be used for the preset, as the forms may take longer to open when the advanced options have been enabled.