Using Siebel Tools > Parallel Development Using Workspaces > Using the Parallel Development Tools for Workspaces >

Understanding Development Workspaces in Siebel Tools

You can create the development workspaces by branching from either an integration workspace or a development workspace at the immediate parent level.

After opening the development workspaces, you can directly edit the workspace-supported repository object and complete the development configurations.

The names of all development workspaces start with the prefix dev_<userid>_.

Working on the development workspaces, note that:

• Administrators can perform these workspace operations on the development workspaces: open, edit workspaces that support repository objects and complete their development configuration, submit for delivery, and rebase.
• All developers can create development workspaces branching from integration workspaces. If you are a new developer, confirm with the administrators to ensure that you have the permissions of a Composer administrator in the production database.
• While creating development workspaces on a specific release, development members should communicate with the administrators to select an integration workspace and define it as the parent workspace.
• Users with the developer permissions can create the parallel-development workspaces by selecting one of their parent release integration workspaces as the parent workspace.

  For example, if the parent release integration workspace is IP20xx_apps, the developer's environment displays the parallel-development workspace trees as the following:

  ip20xx_apps, dev_sadmin_l1, dev_ccheng_l2, followed by dev_cmorris_l3

• Development teams can edit repository metadata or change the repository configuration only through the development workspaces.
• Users with the developer permissions can open the development workspaces that they own to edit the repository configuration, checkpoint the version, revert the version changes, rebase the workspaces, change the state of the workspaces to Submitted to Delivery, and delete the workspaces (that is in the editable state if that workspace does not have a child workspace).
• Users or developers can preview the development workspace in the Siebel application by clicking the Inspect button for the repository changes they made to that version. However, they cannot perform the Inspect task on integration workspaces.
• Workspace developers cannot deliver their workspace changes directly to the integration workspaces after they complete the repository configurations on their development workspaces. In this case, they must change the status of the workspaces to Submitted for Delivery, and then the Siebel administrators approve and perform the deliver process.

NOTE:  Delivering the changes to the parent development workspace delivers the changes and also publishes the changes.