[color=red][size=large]Implicit Customizing[/size][/color]
Implicit Customizing is provided by the Web Dynpro runtime and can be used by everyone having sufficient autorizations.To be able to customize a Web Dynpro application,the application must be started by adding the query string SAP-CONFIG-MODE=X to the application's URL.Customizing is conducted by right-clicking on any UI element.A context menu appears.By selecting the entry Settings for current Configuration the customizing dialog is displayed.
Before the customizing dialog starts,the user's authorization for the authorization object S_DEVELOP is checked.If a sufficient authorization for S_DEVELOP is not found,the autorization for the autorization object S_WDR_P13N is checked.
For each UI element,a predefined number of properties can be changed.Elements that are excluded from customizing by configuration are not available.Selecting the Final checkbox for any property excludes this property from personalization.
The personalization data set are independent of the user.
[color=red][size=large]Explicit Configuration[/size][/color]
To allow an explicit configuration of a component,a configuration controller has to be created.A configuration controller is a special controller.Only one configuration controller may exist for each Web Dynpro component.
All attributes that will be accessible via configuration have to be defined in the context of the configuration controlelr.Using context mapping and data binding,these attributes can then be used to change UI element properties directly in any view.However,any other functional changes based on these attrbutes are also possible,since the attributes are visible to all controllers that declare the usage of the configuration controller.
To create a configuration controller,a custom controller has to be create for the component.From the context menu((Re)Set as Config.Controller) this contrller can then be transformed to the component's configuration controller.
The developer has to decide which attributes are to be defined in the component controller and how changing these attrbiutes will influence the functionality and the UI of this component.
When defining a component configuration.not only predefined UI element property values can be changed,but also the values of the attributes defined in the configuration controller.These attrbiutes are accessible via the Explicit Configuration tab.
Hint: Attribute defined in the configuration controller are not automatically available for customizing and personalization!
Implicit Customizing is provided by the Web Dynpro runtime and can be used by everyone having sufficient autorizations.To be able to customize a Web Dynpro application,the application must be started by adding the query string SAP-CONFIG-MODE=X to the application's URL.Customizing is conducted by right-clicking on any UI element.A context menu appears.By selecting the entry Settings for current Configuration the customizing dialog is displayed.
Before the customizing dialog starts,the user's authorization for the authorization object S_DEVELOP is checked.If a sufficient authorization for S_DEVELOP is not found,the autorization for the autorization object S_WDR_P13N is checked.
For each UI element,a predefined number of properties can be changed.Elements that are excluded from customizing by configuration are not available.Selecting the Final checkbox for any property excludes this property from personalization.
The personalization data set are independent of the user.
[color=red][size=large]Explicit Configuration[/size][/color]
To allow an explicit configuration of a component,a configuration controller has to be created.A configuration controller is a special controller.Only one configuration controller may exist for each Web Dynpro component.
All attributes that will be accessible via configuration have to be defined in the context of the configuration controlelr.Using context mapping and data binding,these attributes can then be used to change UI element properties directly in any view.However,any other functional changes based on these attrbutes are also possible,since the attributes are visible to all controllers that declare the usage of the configuration controller.
To create a configuration controller,a custom controller has to be create for the component.From the context menu((Re)Set as Config.Controller) this contrller can then be transformed to the component's configuration controller.
The developer has to decide which attributes are to be defined in the component controller and how changing these attrbiutes will influence the functionality and the UI of this component.
When defining a component configuration.not only predefined UI element property values can be changed,but also the values of the attributes defined in the configuration controller.These attrbiutes are accessible via the Explicit Configuration tab.
Hint: Attribute defined in the configuration controller are not automatically available for customizing and personalization!