What kind of upgrade are you mentioning here? This blog applies to Siebel 7.8 and above.

Thanks,
Sridhar

Thanks for the valuable information.

I would however not give access to this feature to everyone because you need to understand what you are doing.

Do you see any considerations towards a future upgrade?

Kind Regards,

Michel Nauwelaers

Also I see that with Object locking there are too many restrictions. For example if we need to create New Objects or Copy Objects and assign it a project we cant do that until the project is either locked or checked out. Which is little weird. So every time we realize that we need to create new objects we have to toggle that flag.

We cant also check-in objects if there were no objects in the server.

How is the normal practice that you guys follow?

Regards,
Sridhar

Thanks for the post.
Just to add to the above functionality, Siebel has hard coded the SADMIN value to enable Object Level Check In / Check Out when connected to the server DB.

However if your organization wants to pass the control to another user (probably another admin) you can achieve it with a little bit of configuration.

Here is what we need to do…
With the help of the following configuration, we can provide access to any user other than the default SADMIN. E.g., please follow the below mentioned steps to give access to QADMIN.

Navigate to Business Component “Repository Project”. Expand it to expose its fields. Query for “OL RO” field. Set the Calculated value for this field to

IIF(LoginName() = “QADMIN”,”N”,”Y”)

Then copy the Siebel.srf file in the tools\Objects\enu folder and compile the changes against the copied file.
Launch Tools connected to the compiled srf. The user should be able to modify the AOL flag now by logging to the Siebel Tools as QADMIN.

I have posted the same in my blog.

You can link my blog to yours.

Regards,
NanPats