on 01-17-2013 8:50 AM
Hi,
i know how disable user personalization from WebDynpro Abap, is necessary set the parameter WDDISABLEUSERPERSONALIZATION in the WebDynpro Application.
But is possible to set it globaly in the portal? i don't want to set it for all webdynpro.
Thanks,
Rocco
Hi Rocco,
WD_GLOBAL_SETTING is a special WD application to set application-parameters globally.
You can activate it in SICF and use it to disable user personalization globally.
Regards,
ismail
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Rocco,
as far as I know, it is not possible to globally "switch off end user personalization for all webdynpros embedded in the SAP EP" (that's what I understood you want to do). Ismail provided the solution for the global setting ERP-System-wide, but you said you don't want this 😕
In my system I did use WD_GLOBAL_SETTING to prevent endusers from crippling themselves and I have no use cases where enduser should have the option to personalize. Can you elaborate why you don't want to globally disable it for all WebDynpros?
Cheers, Lukas
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi there
still not sure why you would want to do this -- If I'm a user and want to make a query I might want a small subset selection rather than a whole huge list from a DB and I might only want to see 3 fields say on a screen rather than the "default" especially when cutting / pasting or downloading into a spreadsheet for emailing.
I think a lot of developers tend to not understand what REAL USERS want or need and try and keep too much of this stuff under lock and key.
POWL is extremely useful and can be used in a lot more cases than it is at the moment --even for "Classical queries " which would normally have been done by older ALV -- advantage also is you can run these from a Portal if the end user doesn't have direct access to the back end system too.
Cheers
When this option was still active, we got billions of incidents "where are my fields/tables" etc. "the aplication is broken" "my computer doesn't work". I never doubted the usefulness of personalization itself, but it always depends on the masses given this 'privilege'. If your "Real Users" are able to comprehend what they do and even are sensibly capable of using this privilege, then god bless you. Do you want to swap positions with me for a week?
Cheers, Lukas
Right... To much privilige is far to much for your "normal" users. A seemingly powerful functionality is mostly a source for more problems... You have to assume that they know nothing.
Keep it simple with the fewest functionality. ... and it will be accepted by a user rather than a more "complex" application.
User | Count |
---|---|
80 | |
24 | |
11 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.