Workspace Types and Inheritance

This topic describes the different types of Workspaces. Workspaces inherit the object definitions from their ancestor Workspaces (parent, grandparent, and so on).

• MAIN Workspace. MAIN is the root Workspace and it contains the current master version of the Siebel Repository (which includes all object definitions). The configuration in MAIN typically mirrors the current production environment.

• Integration Workspace. Integration Workspaces (IWS) are created under MAIN or another IWS, and typically represent the configuration changes needed for an upcoming release or (for an IWS that is a child of another IWS) some feature that is being developed for a future release. The purpose of an IWS, as the name suggests, is to allow testing of features and bug fixes from different developers integrated with each other.

• Developer Workspace. Developer Workspaces are the only editable Workspaces, where developers can build and unit test repository changes. Individual developers will make their changes in a personal Workspace that they create under some IWS. The content of this Workspace might contain a bug fix or some other contribution to a larger feature represented by the parent IWS. Developer Workspaces can be inspected by any user to validate functionality. When a Developer Workspace is delivered to its parent:

  • The original record is still maintained (you still have the old version).

  • A new record will be created with an increment to the version number.