Application Parameters

WDDISABLEUSERPERSONALIZATION

• X

• No value specified

Suppresses the implicit personalization options.

More information: Personalization and Customizing

WDENABLEUIELEMENTSHIDE

• X (default value)

• No value specified

Suppresses the option to hide a UI element from the context menu.

Remember that if this feature is activated or deactivated, the function "Restore All Changes" is also activated or deactivated.

The setting does not affect the personalization of UI element Table.

WDFORCEEXTERNALSTYLESHEET /

-

• X

• No value specified

URL parameter WDFORCEEXTERNALSTYLESHEET has been replaced with parameter WDUSEEXTERNALSTYLESHEET. For compatibility reasons, the switch WDFORCEEXTERNALSTYLESHEET is still evaluated. The default value WDUSEEXTERNALSTYLESHEET=ON must be set. For more information, see the description of parameter WDUSEEXTERNALSTYLESHEET.

WDSTYLE_LABELALIGNMENT /

WDSTYLE-LABELALIGNMENT

• USEGL (default value)

• LEFT

• RIGHT

• No value specified

Controlling alignment of .Label.

Value USEGLmeans that all Labels are right-aligned if WDUIGUIDELINE=GL20 is set. All Labels are left-aligned, if WDUIGUIDELINE=GL11 is set.

LEFT means that allLabels are left-aligned. Default value RIGHT means that all Labels are right-aligned. If Label.width is set to initial, it is displayed with 100% width.

Activating right-aligned Labels can make the layout worse. In this case reset the width of the Label, and make changes to the layout.

WDSTYLE_TOOLBARDESIGN

WDSTYLE-TOOLBARDESIGN

• FLAT (default value)

• HIGH

This parameter changes the appearance of ToolBarButton, ToolBarButtonChoice, ToolBarToggleButton in a ToolBar with property ToolBar.design=standard.

Value FLAT means that the specified ToolBar-UI elements are displayed with no highlighting, like text in the ToolBar. Value HIGH means that ToolBarUI elements are displayed exactly like normal Buttons.

WDTHEMEROOT /

SAP-THEME

• sap_bluecrystal

• sap_chrome

• sap_corbu (default value)

• sap_hcb

• sap_standard

• sap_tradeshow

• sap_tradeshow_plus

Stylesheets for the application without portal integration. You can import user-configured stylesheets with report WD_THEMES.

See also Stylesheets in Web Dynpro ABAP.

WDUIGUIDELINE /

WDUIGUIDELINE

• GL20 (default value)

• GL11

• FIORI

Classic or new behavior in visualization, filtering, sorting, and selecting. Siehe auch:

• Filtering in Tables

• Sorting in Tables

• Selection in Tables

Default value GL20 differs widely in the UI and in the behavior of some UI elements.

• The red star for visualizing the state property with value required is always rendered on the left side of the Label. See also Truncating Contents in the FormLayout.

• With drag & drop in MatrixLayoutand GridLayout, visualization has been changed slightly: The insert selection is now a dashed line specifying the insert position and no longer a box with the dimensions of the dragged object.

1875625

Value FIORI activates some changes:

With the DEFAULT theme value, at application runtime the theme is determined from the guideline used.

• The SAP_BLUECRYSTAL theme is used for the FIORI guideline.

• The CORBU theme is used for guidelines GL11 and GL20.

Instead of the DEFAULT theme, you can specify a theme, for example SAP_CORBU.

If an application uses the FIORI UI guideline, the application can only run in render mode STANDARD. This means that if a different render mode is set in parameter WDPREFERREDRENDERING, the STANDARD render mode is always used at runtime.

When new Web Dynpro ABAP applications are created in the Workbench, application parameters WDUIGUIDELINE = FIORI and WDPREFERREDRENDERING = STAND_ONLY are set automatically. The application parameters can be changed. As described above, the render mode STANDARD is always applied to applications that use the FIORI guideline. If you want the application to use a different render mode, you should use a different guideline, for example GL20 (Guideline 2.0).

Active components, such as Flash, Silverlight, Java, and ActiveX are no longer displayed. If an application with the FIORI guidline contains a UI element with an active component, the UI element is not displayed and cannot be used at runtime. Active components contain, for example, the following UI elements: FLASH_ISLAND, SILVERLIGHT_ISLAND, INTERACTIVE_FORM, OFFICE_CONTROL, GANTT, and NETWORK. Instead of these active components, HTML_ISLAND for instance can be used.

WDUSEANIMATION /

SAP-LS-USEANIMATION

• X (default value)

• No value specified

If the WDLIGHTSPEED parameter is active, this parameter (active by default) renders show and hide effects, for instance, for popups. You can deactivate this parameter if required for system performance.

Name of the user parameter: WDUSEANIMATION

WDUSEEXTERNALSTYLESHEET /

-

• ON (default value)

• OFF

• FORCE

Web Dynpro applications use style sheets transferred by a portal or NWBC (URL parameters sap-ep-themeroot, sap-cssurl), provided the version of the stylesheet is new enough. If the version is too old, a fallback mechanism is executed. This avoids unattractive rendering and JavaScript errors. However, bear in mind that any customer branding can get lost. It is also possible to transfer a stylesheet installed on the SAP system using URL parameter sap-theme

With parameter WDUSEEXTERNALSTYLESHEET you can influence how information from external stylesheets is used.

• WDUSEEXTERNALSTYLESHEET=ON: External style sheets are used.

  This is the default setting. The mechanism described above is activated. External stylesheet information is evaluated.

• WDUSEEXTERNALSTYLESHEET=FORCE: Obsolete external style sheets are also used.

  This setting is the same as the default setting but with one difference: The external stylesheet will be used if the version synchronization fails. Bear in mind that this could result in unattractive rendering and JavaScript errors.

  Note

  Running a Web Dynpro application with this setting is done at your own risk. SAP Support does not provide any help or corrections for Web Dynpro applications that are operated with this setting.

• WDUSEEXTERNALSTYLESHEET=OFF: External style sheets are ignored.

  With this setting stylesheet information passed with this URL is ignored. This means that URL parameters sap-ep-themeroot, sap-cssurl, and sap-theme are ignored. Application parameter WDTHEMEROOT, which corresponds to URL parameter sap-theme in the application, can still be set client-wide and application-wide.

URL parameter WDFORCEEXTERNALSTYLESHEET has been replaced with this new parameter WDUSEEXTERNALSTYLESHEET. For compatibility reasons, the switch WDFORCEEXTERNALSTYLESHEET is still evaluated. The default value WDUSEEXTERNALSTYLESHEET=ON must be set.

For more information, see SAP Note 1679127 ..

WDSIDEPANELCONFIGURATIONID

<configuration id>

Configuration ID of the Web Dynpro component WDR_CHIP_PAGE of type .SIDEPANEL This configuration determines the content of the side panel.

WDSIDEPANELOPEN

• X

• No value specified

Specifies whether the side panel is opened or not when the program is started.

WDSIDEPANELRESIZABLE

• X (default value)

• No value specified

Specifies whether the width of the side panel can be changed by the user or not. If the width can be changed, the side panel is separated from the main application by a splitter control.

WDSIDEPANELREMOTEPRODUCER

• X

• No specification (default value)

Enables sending of tagging data from a Web Dynpro application running in the NWBC content area.

WDSIDEPANELREMOTECONSUMER

• X

• No specification (default value)

Enables receipt of tagging data in the NWBC side panel (for example, for Page Builder or FPM applications running in the side panel).

WDCONFIGURATIONID /

SAP-WD-CONFIGID

<config id>

Configuration ID of the Application Configuration. Passes the ID of the application configuration. Typically, this ID is specified either in the application (various applications are defined for the use of various application configurations) or is defined from the portal as a parameter in the iView.

WDSUPPORTSFULLHEIGHT /

SAP-WD-SUPPORTSFULLHEIGHT

• 0

• 1

• 2

• 3

Web Dynpro application developers must decide whether applications are to always take up the maximum height or not. Depending on your requirements you set this application to one of the following values:

• (standard value)

  If this parameter has value 0, the framework sets the value to 1 in a portal environment, and to 2 in a stand-alone environment. This is the correct value for the majority of applications. This ensures that the automatic height adjustment of the iView is supported in the Portal, and in the stand-alone case the application takes on the full height of the browser window.

• 1

  If this parameter is set to 1, the application does not extend to the full height of the browser. This is the correct setting if applications are running in an iView with automatic height adjustment. If not, UI elements with 100% height are not necessarily displayed in their full size. Some UI elements (for example, InteractiveForm) may not be displayed correctly in Firefox.

• 2

  If this parameter is set to 2, the application can use the full 100% height of the browser. This will avoid any problems with Firefox. It is best though not to use any such applications in iViews with automatic height adjustment, since these can appear overstretched in the Enterprise Portal. To set an application to 100% height, you have to observe the following rules when setting application parameter WDSUPPORTSFULLHEIGHT:

  • The height of container-type UI elements (for example, TransparentContainer, Group, Tray, etc.) must be set to 100%. This applies particularly to ROOTUIELEMENTCONTAINER.

  • Only layouts of type MatrixLayout oder GridLayout are allowed to be used. Toggle the stretchedVertically flag to true.

  • Property vAlign for all instances ofGridData and Matrix(Head)Data must be set to top.

• 3

  If this parameter is set to 3, the framework uses the full height, without a scrollbar. With a value of 3, this parameter behaves as with 2, but with no scrollbar. Content that is too long is cut off. Use the parameter with value 3 if you create a page that uses 100% of the width and height, and has its own containers with scrollbars. This means that the application itself takes care of the scrolling behavior.

See also SAP Note .1266588 .