Advertisements

SIEBEL: Allow Object Locking Property

AllowObjectLocking

For each project you can specify either developers are allowed to check-out/ check-in individual objects within the project or not. To allow developers to check out and check in objects, you set the project’s Allow Object Locking property to TRUE.

To modify the Allow Object Locking property, you must use the SADMIN user ID to log in, and you must be logged into a server data source.

You cannot set the Allow Object Locking property in your local repository.


To set the Allow Object Locking property
1. In the Object Explorer, choose Project.
2. In the Projects window, choose the desired Project object, then right-click and choose Toggle Allow Object Locking.
NOTE: You can only change the Allow Object Locking flag on the Server database using the SADMIN login ID.
The Toggle Allow Object Locking menu option is enabled in below case.

  • In a configuration file, parameter is TRUE for the for a property.
  • The user is logged in to the server using the SADMIN user ID,

When the SADMIN user chooses this option for a project that is already set to allow object locking, a check is performed to determine either any objects are locked on the server or not within the project. If there are objects locked within the project, SADMIN will receive an error message. If the project is locked on the server by someone else, the menu option for Toggle Allow Object Locking will not appear.
To make it true use the solution given by Siebel. But it will not allow to modify the more than one project same time. To do this set the OBJ_LOCKED_FLG in table S_PROJECT on server as ‘N’ using following query.

update S_PROJECT set OBJ_LOCKED_FLG=’N’ where OBJ_LOCKED_FLG=’Y’ and NAME in(‘Contact’,’Account’,’Acd’)

Advertisements


Categories: Siebel

Tags: , , , , , , , , , , , , , ,

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: