Essentials (Siebel 7.
7)
Module 22: Managing Object
Definitions
Module Objectives
After completing this module you will be able to:
Explain the role of projects
Manage object definitions using Check Out and Check In
Lock projects locally
Why you need to know:
Checking projects in and out are critical tasks that enable
multiple developers to work together on a configuration
effort
Module 22: Managing Object Definitions 2 of 21
Projects
Are named sets of object definitions in a repository
Only one version of a project exists in a repository at a time
Are a mechanism to organize object definitions so that a single
developer can exclusively work on them as a group
Account (SSE) Applets
Screen Account List Applet
Accounts Screen Account Entry Applet
Views
Account List View Manager’s Account List View
All Account List View Account Profile View
Module 22: Managing Object Definitions 3 of 21
Projects Continued
A standard Siebel application is delivered with a large number
of existing projects
New projects can be created by:
Selecting the Project object type, and
Creating a new record in the Object List Editor
Module 22: Managing Object Definitions 4 of 21
Assigning Object Definitions to Projects
Every object definition must belong to one, and only one, project
A Siebel-supplied project
A user-created project
A top-level object definition has a Project property
Child object definitions belong to the parent project
Child object definition
has no Project
property as it belongs
to the parent project
Module 22: Managing Object Definitions 5 of 21
Viewing Object Definitions by Project
View object definitions in a project using the Project drop-down
list
Displays the object types for which there are object definitions in
the selected project
Select **All Projects** at the top of the list to see all projects
Module 22: Managing Object Definitions 6 of 21
Repositories
Master copy of repository resides on server database
Stores tested object definitions for complete developer team
Each developer has copy of the repository on local developer
(client) workstation
Developers perform all editing on their local repository
Server Machine Developer Developer Developer
Workstation Workstation Workstation
Master Local
Module 22: Managing Object Definitions 7 of 21
Copying Projects
Object definitions in one or more projects can be copied:
From the server to the local developer repository (Get, Check Out)
From the local developer repository to the server (Check In)
Overwrites the version in the destination repository
Project
Get, Check Out
Server Local
Check In
Module 22: Managing Object Definitions 8 of 21
Getting Projects
Click Get to populate a newly-initialized local database with a
copy of all projects in the server repository
Click Get to refresh a read-only project in a local repository
Need object definitions modified by other developers to update
your local copy
Module 22: Managing Object Definitions 9 of 21
Check Out
Use Check Out to modify object definitions in a project
Check Out:
Copies all object definitions in project on server to local database
Local copy of project is overwritten by server version
Locks project on server repository
Prevents other developers from modifying that project
Locks the project in the local repository
Permits developer to make changes to object definitions in that project
Module 22: Managing Object Definitions 10 of 21
Check Out Continued
Click Check Out to copy projects from the server to the local
repository
Module 22: Managing Object Definitions 11 of 21
Check In
Use Check In when object definitions in the project have been
edited and tested
Check In:
Copies object definitions from local repository to server repository
Replaces versions of checked out object definitions with new
versions and unlocks projects
Can also check in object definitions in newly created projects
Releases locks on both server and local copies of project
Maintain Lock leaves project locked for further local modification by
current developer
Module 22: Managing Object Definitions 12 of 21
Check In Continued
Click Check In to copy projects from the local to the server
repository
Module 22: Managing Object Definitions 13 of 21
Project Differences
Use Project Differences to view details of changes made to
checked-out projects prior to checking them in
Detect mistakes or omissions before changes are committed to
server repository
Invoke using Diff button in Check In window
Module 22: Managing Object Definitions 14 of 21
Canceling Check Out
Discards changes made to checked-out project if:
Changes are no longer required
Local project has become corrupted
To cancel a check out of a project:
Check out the project from the server again
Replaces modified object definitions in local repository with original
version from server repository
Repeating check out is permitted for person who last checked out
project
Then check in the project to unlock the project on both the local
and server repositories
Module 22: Managing Object Definitions 15 of 21
Undo Check Out
Use Undo Check Out to release lock on a project on the server
without checking in edited object definitions
Makes the original project available to another developer
Can be followed by Get project to restore original object definitions
in local database
Alternate way to cancel check out
Undo Check Out:
Releases lock on server
Retains lock on local database
Developer can continue to modify object definitions but will not be able
to check them in to the server
Module 22: Managing Object Definitions 16 of 21
Locking Projects
You can directly lock and unlock projects
in the current repository (local or server)
Select Tools > Lock Project…
… or click to set
Locked property
directly
Module 22: Managing Object Definitions 17 of 21
Locking Projects Locally
Consider when:
Prototyping your ideas without preventing other developers from
checking out the project
Intending to discard (rather than save) your work
Allows developer to make and test modifications locally
Prevents developer from checking them in to server repository
Server Machine Developer Developer Developer
Workstation Workstation Workstation
Master Local
Module 22: Managing Object Definitions 18 of 21
Locking Projects on the Server
Prevents developer from undoing the changes and restoring the
original definitions
Allows other developers to get object definitions in an
incomplete, inconsistent, and untested state
Siebel Systems recommends that developers never directly lock
projects on the server
Always use Check Out and modify the object definitions locally
Server Machine Developer Developer Developer
Workstation Workstation Workstation
Master Local
Module 22: Managing Object Definitions 19 of 21
Summary
This module showed you how to:
Explain the role of projects
Manage object definitions using Check Out and Check In
Lock projects locally
Module 22: Managing Object Definitions 20 of 21
Lab
In the lab you will:
Explore how projects work in Siebel Tools
Check out a project from the server
Module 22: Managing Object Definitions 21 of 21
