Web item that you can use to specify the parameters of a Web template.
The following information lists the parameters for the Web Template Parameters Web item, arranged according to the various parameter groupings.
Internal Display
Parameter | Description |
---|---|
Errors Visible (ERRORS_VISIBLE) |
You use this parameter to specify whether error messages are to be displayed in the Web application. |
Warnings Visible (WARNINGS_VISIBLE) |
You use this parameter to specify whether warnings are to be displayed in the Web application. |
Information Visible (INFORMATION_VISIBLE) |
You use this parameter to specify whether information is to be displayed in the Web application. |
System Messages Visible (SYSTEM_MESSAGES_VISIBLE) |
You use this parameter to specify whether system messages are to be displayed in the Web application. You can also select a value for Display Mode for System Messages (SYSTEM_MESSAGES_DISPLAY_MODE):
|
Behavior
Parameter | Description |
---|---|
Display Variables Screen (DISPLAY_VARIABLE_SCREEN) |
Relevant when calling a Web template that contains one or more query views with input-ready variables. You use this parameter to force display of the Variables screen. If this parameter is not set, the variable screen is suppressed if possible. It is still displayed though if for example input-ready mandatory variables have not been filled. |
Use Specific Variant Catalog (USE_SPECIFIC_VARIANT_CATALOG) |
Relevant when calling a Web template that contains one or more query views with input-ready variables. Using this parameter, you can use the variant catalog for the queries used. If the Web application contains just one query, you can use the variants for this query. |
Reset Variable Values to Default (CLEAR_VARIABLES) |
Relevant when calling a Web template that contains one or more query views with input-ready variables. You use this parameter to remove the default values from the query view. The variables then have the default values from the variable definition. |
Display Same Variable Only Once (MELT_VARIABLES) |
Relevant when calling a Web template that contains multiple query views with input-ready variables. You use this parameter to specify for the variable screen whether variables that are used in all the query views and in the same context (same compounding and initial value) are to be displayed for input just once. If the variables are based on different InfoProviders, the input help is read from the master data table. |
Display Personalized Variables (SHOW_PERSONALIZED_VARIABLES) |
You use this parameter to specify whether the personalized variable values are already displayed as initial in the General Variables screen area. More information: Personalizing Variables in Web Applications |
Web Template Has Main Object (TEMPLATE_HAS_MAIN_OBJECT) |
You use this parameter to define a main object for a Web template and use it for personalization (for example, for generic Web templates) or the Text Web item. You can use reports (report default template), or query views (query view template) as main objects. If you activate this parameter, you specify the Web template (MAIN_TEMPLATE_OBJECT) as the main object:
|
RRI Open Mode (RRI_OPEN_MODE) |
You use this parameter to specify how the jump target for the report-report interface (RRI) is to be opened.
More information: |
Standard Actions of the Web Template (WEB_TEMPLATE_ACTIONS) |
You use this parameter to specify a command sequence that is to be executed at specific times on the server. The following times are currently supported:
More information: |
Only Update Changes (USE_SNIPPETS) |
You use this parameter to define whether the Web application should be displayed flicker-free. With flicker-free display of Web applications, only changes to Web template objects caused by navigation are updated. The unchanged parts of the Web application remain in their original state. This provides the user with a better (flicker-free) display. |
Behavior when Loading a Bookmark (BOOKMARK_LOADING) |
Here you specify the behavior of the Web template when loading a bookmark. The following options are available for this purpose:
|
Stateless Navigation (STATELESS) |
The status is removed on the server after each navigation step. Using this parameter is only recommended with pages that are rarely navigated to. Take note of the following background information when setting this parameter: Between two navigation steps, the status of the web application on J2EE and ABAP is not retained in the main memory. During a navigation step, however, additional computing effort arises in order to restore the status at the beginning of the navigation step and to remove the status at the end of the navigation step. This makes navigation slower for the user due to the additional computing effort. As users generally pause between two navigation steps, however, a larger throughput Is possible in multi-user operation, as the main memory is not in permanent use.
In planning applications, the STATELESS setting only causes a minor reduction of the occupied memory on J2EE, as planning applications require the status to be retained on J2EE and ABAP. |
Use Layout Container for Export (EXPORT_LAYOUT) |
This parameter makes it possible to display multiple juxtaposed Web items in the print version. You also have to insert the Web items into the Container Layout Web Item. In the dialog for creating the PDF document, choose the options Fit to Page or Fit to Page Width. More information: |
Data Binding
Parameter | Description |
---|---|
Variant (VARIANT) |
You use this parameter to specify which variant to execute the Web application with. |
Document Save Level for InfoProvider Data (DOCUMENT_SAVE_LEVEL) |
You use this parameter to specify for which area the documents for InfoProvider data are to be created:
Planning applications are normally created for the InfoProvider level. Plan data is generally recorded with other data and evaluated later. If you create comments that you want to be visible for the analysis, you have to choose InfoProvider level for the planning application. More information: Creating New Documents |
From a technical point of view, Web template parameters are Web items. The Web item is not included in the list of Web items in Web Application Designer however, but is available in the Properties screen area in Web Application Designer.
More Information: