Parameters

Parameters can be set at various points in applications and processes to view pages or input pages. 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 purpose, the view page will define and request a STRID parameter. The corresponding data record can only be displayed with a valid STRID. The caller of the page, e.g. a button, transfers a specific value for the required parameter "STRID".

Application page - Define parameters

Parameters are defined for application pages on the Parameter tab in 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.

Further information on parameters in connection with application pages can be found here.

Transfer parameters

Parameters can be transferred to application pages by the following elements. Please note that parameter values only need to be transferred if the called page defines or demands parameters.

  1. Button with the action "No action", "Save" or "Delete"

  2. Button with the action "Add 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 resource elements.

  9. Link destination for calendar plugins

  10. Diagram 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.

More information

Define parameters