Implementing Change Control

Hi All,

In this post, i am gonna discuss the approach while implementing change control in any of your PeopleSoft application.

Enabling change control from App D is not a big task. However,after enabling this,restrict that no one should be having supervisor access except the admin which is the main security to control.Otherwise, lets say you enable the change control and any developer having supervisor access can disable the settings !!!

Change control, as name indicates , is a way to control the changes done by several developer in the development landscapes.It employs locking and unlocking of objects before modifying them and prevent overwriting by another developer when already one technical is making changes to it.

Change control authority is controlled by permission lists given to a user through roles.There are three levels of authority :

1) Restricted Access : User with this access only, cannot lock an object or change the setting of change control.
2) Developer Access  : User with this access can lock the unlock objects and make changes. They cannot lock or                               unlock objects that are locked by others.Can not change settings.
3) Supervisor Access : User with this can control the settings and lock/unlock any objects.

Here is the approach you should follow :

1) Enable the change control from App D.
2) Note that users could be having tens of permission lists which gives them the supervisor access. Find the list
   of permission lists having supervisor access to change control,which are added to users roles:
  
   SELECT CLASSID FROM PSAUTHITEM WHERE MENUNAME='APPLICATION_DESIGNER' AND BARNAME='CHANGE_CONTROL' AND    AUTHORIZEDACTIONS=4;

3)Revoke the supervisor access from all permission lists and give restricted access:

  UPDATE PSAUTHITEM SET AUTHORIZEDACTIONS=2 WHERE MENUNAME='APPLICATION_DESIGNER' AND BARNAME='CHANGE_CONTROL';
  Note : update authorizedactions as 3 if you want to give developer access to everyone.

4)Now that no permission lists are having supervisor access, create a new permission list and just give     supervisor access to it on change control .No other permissions to be given to this PL.

5)Create a new role, assign the created PL to this role and attach this role to admins user profile .

Result : except admins, no one would be having access to make modifications to change control settings. They can          just lock the definition if given developer access.