Show TOC

Naming Rules to Ensure PersonalizationLocate this document in the navigation structure

Procedure

The Web Dynpro Framework enables portal administrators and users to configure Web Dynpro iViews, including hiding UI elements and setting the values for UI elements, such as the text in an InputField .

This implicit configuration is provided automatically by the framework, and no additional programming is required.

Redeploying Applications

When redeploying an application, do not change the names of the following objects:

  • Component usage

  • Interface view

  • Component controller implementing class

  • View

  • UI element ID

  • Role created via API for view or component usage from within a view or component controller class.

    A Web Dynpro role is an alternate name for a view or component usage, and is unrelated to a portal role.

If the names are changed between deployments, existing personalization settings may be lost.

If you are programming dynamically, there is no need to assign IDs to the UI elements. These are assigned automatically when an instance is created. But do not change the order in which the UI elements are instantiated, as this would change the names of the elements and cause the loss of personalization settings.