Parameters

1. General

Parameters can be transferred to view pages or edit pages at different places in applications and processes. This means that it is easy to reuse pages by providing them with different parameter values from different callers. The application page defines which parameters are required so that it can function correctly.

Example

A view page should present a certain data record. For this, the view page will define and demand an LID parameter. The corresponding data record can only be displayed with a valid LID. The caller of the page, e.g. a button, transfers a certain value for the required LID parameter.

2. Application page - Define parameters




Parameters are defined for application pages on the Parameter tab in the page properties. If the required parameters are found with their fallback values and semantic values, the page displays the corresponding data. Otherwise, the page will not be loaded.

Usually, the parameters are automatically predefined so that additional modifications are not required. In some cases, parameters cannot be predefined. The application developer can then decide which parameters are expected by a page.

3. Transfer parameters




Parameters can be transferred to application pages by the following elements. Please note that parameters values only need to be transferred if the called page defines or demands parameters.
  1. Buttons with the action "No action", "Save" or "Delete".
  2. Buttons with the action Insert data record for free layout tables
  3. Portlet containers for the integrated pages.
  4. Email configuration in applications for the page that provides the mail content.
  5. Column actions in view tables.
  6. Actions of free layout tables.
  7. Buttons in the configuration of the tree application element.
  8. Actions in calendar and resourcen elements.
  9. Link destination for calendar plugins
  10. Chart interactions.
  11. Email actions in processes for the page that provides the mail content.
  12. Push notification action in processes if pages have been as the link destination for the mobile or desktop view
All of the elements named above use application pages as the link destination or integrate them, such as the portlet container or the email configuration.
In older versions of Intrexx, information was transferred using the expert attribute, "rq_", and then used on the opened page, for example, to set a default value in controls using the expert attribute, "customdefault". Parameters are used for this from Intrexx 19.03 onwards. The page, where the default value should be set, can demand the parameter "myDefaultValue", for example. The page caller can transfer this parameter, and then the control on the called page can retrieve the default value from the parameter in the dialog.

4. More information

Parameter dialog