Check in locally locked object.

Some times before we "Check Out" some objects or even a whole project we want to play around it locally, so we just click right mouse button on object and select "Lock" to start modifying it (and if something goes wrong you can just do "Get" on object to get definition from server). It is good choice if on one, really hard to solve, requirement (some difficult change request) are working two or more people in team (two heads better than one). Then every body can "Lock" project locally and work with it. But what to do when some one find the solution and want to "Check In" it? Yes he can't because the objects he changed must be "Checked Out" from server and locked on the server. So if we "Check Out" object it will overwrite any changes we made and we need to do it all again, but what if it was really hard solution and depends on lot of configuring? So there is a solution! Of course it is not good to do it too much! The member who solved the problem log in to the "Siebel Tools" on server (first better close local "Tools" (I don't know if it is needed, but better to close)), then lock the object, objects or projects, that are changed locally, on server "Tools" so that they are locked by that member who have locally solved solution. Close the server "Tools" (this is mandatory) and then member who solved solution can do "Check In" to check in modified objects. As I sad, it is not advised to do it too much, because it is not advised to log in to server "Tools" to much, or if you do so then think about every step you do on server.

Hope it helps teams.