module 22 working with projects

7/30/2019 Module 22 Working With Projects

1/15

1 of 15Working with Projects

Siebel 8.0 Essentials


2/15

Module 21: Working with Projects


3/15


Module Objectives

To understand managing Projects and association of objectdefinitions to them

To understand the process of project/object Check out and Check in


4/15


Project Definition

Are a mechanism to organize object definitions so that a single

developer can exclusively work on them as a group

Are named set of object definitions in the repository Used to group objects based on functional areas

Every object definition must belong to one, and only one project,

either a Siebel-supplied project or a user-created project

Top level object definitions have a Project property

Child level object definitions belong to Parents Project Account BCbelongs to project

"Account"

Child belongs to

parent project. It

does not have a

Project property


5/15


Creating Project

New project can be created by selecting the Project object type

and creating a new record in the Object List Editor

New project


6/15


7/157 of 15

Working with Projects

To Copy Projects

Object Definitions can be copied from

Server to Local repository through Check Out/ Get

Local to Server repository through Check In

Check Out and Check In is a source control mechanism for multiple

developers working in the same repository

Safely manage concurrent usage among developers

When copied, overwrite the version in the destination repository

Server Repository Local Repository

Project

DefinitionCopy using

Get/ Check Out

Modified Project

definition copied in to

server

Copy using Check In


8/158 of 15

Working with Projects

Check Out Projects

Use Check Out in order to edit object definitions in a project

The projects Allow Object Locking property must be disabled

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 and thus avoids conflicts

Locks the project in the local repository

Permits developer to make changes to object definitions in that project


9/159 of 15Working with Projects

Check Out Objects

Allows for checking out individual objects

Quicker than checking out entire projects

Allows multiple developers to work on objects within a single project

To enable object-level Check Out

Add EnableObjectCOCI=TRUE in the [Siebel] section of tools.cfg

Log in to Tools as SADMIN to the server database and enable the projects

Allow Object Locking property

Limitations are, the following tasks are not possible:

Deleting objects

Renaming objects

Assigning objects to a different project



Undo Check Out and Cancel Check Out

Undo Check Out

Removes lock on server objects

Makes the original project available to another developer Objects in the local repository remain locked, and all changes since the objects

were checked out are retained

To Cancel Check Out

Check out the project from the server again

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 serverrepositories

Canceling Check Out

Discards the changes made to

the checked-out local project.

Used when the local project definition

is corrupted or no longer required

To Undo

Check Out



Check In

Is used once the modified object definitions are thoroughly tested

Copies object definitions from your local repository to the serverrepository

Adds any new objects to the server repository

Removes the lock from object definitions

Maintain Lock: Leaves project locked for further local modification by

current developer



Getting Projects

Get populates a local database with a copy of projects from the server repository

Overrides the projects on your local database, whether they are locked ornot locked

Use Get to bring object definitions modified by other developers to your local

database

Use Get with All Projects selected to populate a newly-initialized local database



Locking Projects

Projects can be directly Locked or Unlocked in a repository (Server/Local)

Select an object definition and click Tools > Lock Project Select a Project definition and set the Locked flag to True

Locking projects locally

Allows developer to make and test modifications locally

Prevents developer from checking changes into server repository

Helps when prototyping your ideas

Locking projects on the Server

It is strongly recommended not to lock projects directly on the server

Prevents the developer from undoing changes and restoring original definitions

Allows other developers to get object definitions in an incomplete, inconsistent,

and untested state



Module Highlights

Projects help us in organizing the object definitions so a developer can

work on them exclusively Developer edits a copy of master repository residing on local client

Check Out and Check In are used to modify object definitions

Project locking ensures only one developer can modify a given object



Lab

In the lab you will:

Explore how projects work in Siebel Tools

module 22 working with projects

Documents