SBWP global layout problem

Schmidt, Jake (SN) jake.schmidt at spiritaero.com
Wed Feb 6 12:55:44 EST 2008


Andy,
I had this problem several months ago.  We had security default the
user-specific box to "checked" and then completely "grayed out" the
field.  Only certain users now have the security to make a global layout
or change an existing global layout.  Hopefully this helps you.
Jake Schmidt
Spirit Aerosystems

---------------------------

Hi all

In these days of Portals & UWL, this query may be a blast from the past,
but we've come across an interesting little problem. In fact, I'm
surprised we've not encountered this before, given the system has been
live for years. Oh well, that's complacency for you...!

The other day, a user decided to update the layout of the business
workplace, changing the columns etc. However, they were on the default
global layout and hence when they saved it, they updated the appearance
for nearly everbody.

Some people did not like this new design (especially as they had moved
some dynamic columns into prime position, which appeared blank to most
users) and so felt that they had a better approach. It's quite
interesting to see quite what 'useful' information the users believe
they really can't live with.

However, since then we've found ourselves in a losing battle. Everytime
we try to correct the layout, another user decides they don't like
what's happened, and modifies it again.

Of course, there are 'user specific' layouts, but when a user modifies
the default layout they are on and elects to save it, the 'User
specific' flag is not set. They just update the global layout as that's
the easiest. Worse, the file naming convention for 'User Specific'
requires the user to clear the '/' and add a 'Z'. Not something they're
going to do by accident.


* Is there a way to permit users to update their user-specific layouts,
whilst locking down the global ones? Are we missing some basic security
settings?

* Has anyone else suffered from this? Or, how have you avoided it?

* Is there a technical solution, or will this just come down to user
training in some way (eek!)? We have many hundreds of users, dotted
around the world, so we can hardly just ring each of them and slap their
wrists!

All suggestions gratefully received :-)

Cheers
Andy Catherall 




More information about the SAP-WUG mailing list