Bookshelf Home | Contents | Index | Search | PDF

Siebel Tools Reference > Application Development Projects >

Locking Projects Directly

---

You can lock and unlock projects directly (as contrasted with the check-out procedure, which locks projects as it checks them out).

To lock local projects directly

• All Project object definitions have a Locked property that you can set to TRUE or FALSE in one of two ways:
  • Set the Locked property to TRUE in the Object List Editor by clicking the Locked field (if the Locked field has no check mark).
  • Set the Locked property to TRUE in the Properties window.

    Figure 258 shows a locked project (Account).

    Figure 258.  Locked Project (Account)

You lock at the project level, even though the Locked property is associated with a particular Business, Data, or User Interface Object. That is, when you lock a specific object, the entire project associated with the object is locked.

It might not seem logical to do a direct lock on a local project, because if it is not also locked on the server, other developers might check it out and your changes and theirs might ultimately conflict. Direct local locking does make sense, however, if you are:

• Prototyping your ideas and do not really want to prevent others from checking out the project you are working on
• Intending to discard your work when you are done

Be aware, though, that you cannot change your mind and decide to use your prototype created this way in your application, because:

• You can check in only those projects you have checked out.
• Your local project's definition will be overwritten the next time you get or check out that project.

Locking Server Projects Directly

Although you can do a direct lock on server projects (by changing the Locked property), Siebel Systems recommends that you never do this. Always lock by doing a check-out, instead, because:

• When you lock on the project directly, other developers who do a get on the object definitions in the directly locked project may find that the definitions are in an incomplete, inconsistent, and untested state.
• You, as the project owner, lose your ability to cancel the check-out and restore the original object definitions.

NOTE:  You can check the project back in only in the project language in which it was checked out. If you switch language mode in Siebel Tools, you lose the lock you had with the project in the previous language mode.

Bookshelf Home | Contents | Index | Search | PDF