iView personalization example needed!

[justin_kemp]

Hi guys,

I need an example of iview personalization. I know about the personalization of the pages and i can add iviews to it at the runtime.

I tried using iview personalization for a SAP Webdynpro Iview and SAP Transaction iview as well, however the only option coming at the time of personalization is to change the logon language, how can i add more options to it.

Or if someone can provide an example of iview personalization that would be really great. I do not want to edit portalapp.xml file right now. There must be some other options available.

regards

Justin

[carsten_buechert]

Hi Justin,

even if you think that there must be some other options available - there aren't.

This is because iView personalization follows no generic approach as page personalization does. Every iView type is different and only the iViews implementation (coding) and technical description (portalapp.xml) define it's personalization possibilities. If you're iViews do not offer personalization beyond the logon language, you loose. Please have a look at the technical description of your iViews to determine what personalization options are avaliable.

HTH (or come back for further questions),

Carsten

[justin_kemp]

Hi Carsten,

Thanks for the reply,

Does this means that I can design a webdynpro application which will be having editable properties at the runtime? (I still do not want to edit portalapp.xml) If Yes, can you suggest a small application which have these properties. I am so concerned because I have to deliver it in an SAP EP Training.

Secondly, u said that "have a look at the technical description of your iViews to determine what personalization options are avaliable" there is no mark which shows that the option is editable at runtime or not. I only know of a property which is to enable the personalization option i.e. YES/NO.

What are the other options available?

Regards,

Justin

[carsten_buechert]

Hi Justin,

first: every WebDynpro iView has excactly one property that can be read by the WebDynpro application. All the parameters you want to send to your WD must be stored in this property. It's the property "Application Parameters". Your WD may need some values in here to change it's behaviour. The possible values depend on your specific WD application and may vary. Check the documentation of your WebDynpro application.

Second: What exactly is your business case? What do you want the user to personalize?

Third: As a complex work-around you may use PCD API from within your WD to change the properties of the WebDynpro iView. But I think you shouldn't do so.

Fourth: It is NOT possible to make the standard properties of a WebDynpro iView personalizable by configuration. You'll need to change the portalapp.xml of the wrapped around portal application.

HTH,

Carsten

P.S.: If you could post what your specific requirements are, maybe the community may have some more ideas.