Parameters
Parameters can be transferred to view pages or input pages at various points 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 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 on application pages in the page properties on the "Parameters" tab. If the required parameters with their fallback and semantic values are found, 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. Parameter values only need to be transferred if the page called up defines or requires parameters.
-
Button with the action "No action", "Save" or "Delete"
-
Button with the"Add data record" action for freely designed tables
-
Portlet container for the integrated pages
-
Email configuration in applications for the page that delivers the content of the email
-
Buttons in the configuration of the tree application element
-
Action in calendar and resource elements
-
Jump target for calendar plugins
-
Email action in processes for the page that delivers the content of the email
-
Push message action in processes when pages are defined as jump targets for the mobile or desktop view
All of the above elements use application pages as jump targets or are integrated, e.g. in the portlet container or the e-mail configuration.