Skip to Content
Former Member
Jul 15, 2009 at 11:15 AM

ESS SCs customisation best practice?



I'm customising ESS screens. I want to know what is the standard and best practice to customise ESS components. Lets say after I import in NWDI and start making changes in NWDS, then checkin, then build and test it successfully, this approach is going to overwrite the standard ESS package. Is it possible at some stage if I decide to revert back to original standard ESS BP by redeploying standard ESS packages?

Also, I'm changing one of the personal data screens, would you recommend to create a seperate iview for the customised personal data screen? Or should I use the standard iviews, roles and webdynpro components for customisation? I mean do I leave the existing components untouched and created seperate iviews somewhere in the portal content for customised screen in different PCD folder, is this ok?