On big projects it is quite likely that large numbers of developers have access to a many environments. Occasionally they can have access to environment which is quite important, for instance one that the customer is using for training or testing.
To reduce the likelihood of developers accidentally deleting some data that they shouldn’t it would be quite normal to remove their access to the environment altogether. However if they need access for troubleshooting purposes then (at least on projects I’ve seen) it’s quite normal for developers to be told “OK, you can have access, but be careful not to do anything destructive”. Occasionally - as with everything - things can go wrong. Either someone forgets which environment they’re in, or does something with unintended consequences. An alternative to the “just be careful” approach would be to create an entirely read-only user profile (i.e. one that has display only privileges to every component system-wide).
Read-only user profile is where no fields are editable and the save button is inactivated.
Also, on Run Control pages the ‘Run’ button is inactive. It’s going to be pretty difficult to alter data in this environment.
First, craft your perfect ‘read/write’ user profile. I’ll call this ‘SIMER’. Now clone it using the ‘Copy User Profile’ functionality in the PIA. This creates a new user profile (in my case ‘SIMER_R’) with the same Roles, and this is the one we’re going to turn read-only.
First create the Permission Lists by cloning those that are currently against the User Profile:
We add the pages to the new permission lists, but set Display Only to 1:
And that’s it, although you may well also need to perform the following:
* Run Portal Security Sync (to sync security up).
* Bounce the App Server and clear cache (my App Server didn’t pick up the signon times from the cloned permission lists until I did this).
* Run SJT_OPR_CLS (Refresh the Security Join Table that contains the Operator and Classid data)
* Close and reopen your Web Browser and clear it’s local cache.
Title | Under | Posted on |
---|---|---|
Component interface Error: no rows exist for the specified keys | PeopleSoft Technical | 03/15/2019 - 3:54am |
ADD 24 months starting from current month.(peoplesoft) | PeopleSoft Functional | 07/29/2018 - 8:44pm |
TRC values dropdown | PeopleSoft Technical | 04/04/2018 - 12:54am |
how to find missing sequence in GRID and print the mising sequence number while saving through peoplecode | PeopleSoft Technical | 09/11/2017 - 4:49am |
Recent comments
2 years 16 weeks ago
2 years 21 weeks ago
2 years 21 weeks ago
2 years 23 weeks ago
2 years 23 weeks ago
2 years 24 weeks ago
2 years 26 weeks ago
2 years 27 weeks ago
2 years 30 weeks ago
2 years 36 weeks ago