Parameters
Parameters can be passed to view pages or input pages at various points in applications and processes. This makes it very easy to reuse pages by having different callers provide them with different parameter values. The application page specifies which parameters are required for it to function properly.
Example
A view page is intended to display a specific dataset. To do this, the view page will define and require a parameter named STRID. The corresponding record can only be displayed with a valid STRID. The element that calls the page—for example, a button—passes a specific value for the required "STRID" parameter.
Application Page - Define Parameters
Parameters are defined on application pages in the page properties under the "Parameters" tab. If the required parameters, along with their fallback and semantic values, are found, the page displays the corresponding data. Otherwise, the page will not load.
As a rule, the parameters are automatically preset, so no modifications are necessary. In some cases, parameters cannot be preset. This allows the application development team to decide for itself which parameters are expected from a page.
For more information on parameters related to application pages, click here.
Pass Parameters
Parameters can be passed to application pages by the elements listed below. Parameter values need to be passed only if the page being called defines or requires parameters.
-
Button with the action "No Action," "Save," or "Delete"
-
Button with the "Add Record" action in custom tables
-
Portlet container for the embedded pages
-
Email configuration in applications for the page that provides the email content
-
Buttons in the configuration of the " Tree" application element
-
Actions in Calendar and Resource Items
-
Jump to Target in Calendar Plugins
-
Email Actions in processes for the page that provides the email content
-
Push notification actions in processes when pages are defined as jump targets for the mobile or desktop view
All of the elements listed above use application pages as jump destinations or are integrated with them, such as in the case of the portlet container or the email configuration.