TM Portal – creating default personalization
In this blog, I would like to provide information about the how An Administrator can personalise TM Portal so that the first time Portal users can see the default personalization set by him.With this Admin can hide the unwanted columns on different screens and also make default setting for the portal users. Please note that the portal users can always change the personalization as per their needs.
As a pre-requisite, you should implement the note 2186138 or implement the relevant Support Pack Level and refer to the attachments of the note for more detailed pre-requisites.
There are 2 options to achieve the default personalization:
Option 1: Change directly in production:
If you want to change the default settings directly in production then you need to have the required Admin Roles and also open the client (SCC4) to save the personalization. This option might not be feasible every time.
Option 2: Change the default settings in Development system & transport:
With this option you can change the setting and personalization in the development system and transport the personalization to further systems. You should have the Portal Admin authorization to do this change (Refer to the note 2186138 for more detailed pre-requisite). Please follow the below steps for option 2:
1. Create a Transport (Customizing) Request and assign to the admin user. Lets say the TR # TMS9999.
2. After this you need to go to SU01 or SU3 to change the user parameter. Then add the user parameter /UI2/WD_TRKORR_CUST and specify the TR number (TMS9999) in the parameter value.
3. After this, with admin user can login to the portal and change the settings and hide/unhide the columns. After you completed the personalization, then you will find the tasks created in the TR (TMS9999).
4. You can transport this TR to further systems
Please note that if you have separate systems for Portal and TM Back end then the above steps needs to be done on the Portal system.
Very useful setting for portal. Thanks Ashish for sharing 😎
one small addition: For the second option, there also has to be portal admin authorization.
Sure, Jan. I'll update. Thanks for pointing out
Thanks for sharing this trick. It will come handy when most needed.