With Siebel versions 7.8 and above, project checkouts have been disabled by default. Instead we have object checkouts which are more flexible and allow multiple developers to work on the same project. So if you go into Siebel Tools and navigate to Tools-> Check Out and select any project, the Checkout button will be disabled.
But sometimes it might be required that a person needs to checkout the whole project. For example while creating objects using the New Object Wizard it would normally ask you to pick the list of projects that are only locked. If projects are not locked then you wont be able to use the wizard. So to enable project checkout we have to disable the individual object locking capability. So for every project we can either have object locking or can have the whole project to be checked out.
Follow the below steps to disable Object locking or to allow the whole project to be checked out.
- Login as SADMIN into Siebel Tools connecting to the Server. If you do not login using SADMIN you won’t be able to do this.
- In Object explorer select Project and on the right panel select the Project for which you want to allow full project check out. Notice that “Allow Object Locking” is checked for that project.
- Right click on the project and select “Toggle Allows Object Locking”
- You will notice that the object definition “Allow Object Locking” will be unchecked.
- Now go back to your local Tools and try to check out and you will see that the checkout button is enabled for that project.
Hope this helps. Leave a comment.
If you have more tips like this and would like to contribute please feel free to send it to me using the participate form. Thanks.
Related posts(Auto Generated):
July 14th, 2008 at 4:14 am
hi All,
This is really good and tells the advance features in siebel upgraded version object locking is new features in siebel.
July 18th, 2008 at 6:08 am
Hi 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
July 18th, 2008 at 10:44 pm
Hi NanPats,
Thanks for the nice Tip. With this we could have multiple users to modify the AOL flag.
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
August 4th, 2008 at 6:21 am
Hi All,
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
August 4th, 2008 at 4:51 pm
Hi Michel,
True that not everyone should be given access.
What kind of upgrade are you mentioning here? This blog applies to Siebel 7.8 and above.
Thanks,
Sridhar
August 29th, 2009 at 6:59 am
Thank you..this was useful