Using Siebel Tools > Using Workspaces in Siebel Tools > Using Workspaces in Siebel Tools >

Configuring Non-Workspace Objects

The following object types and their child objects are non-workspace objects:

• Repository
• Project
• Table
• Task
• Type
• EIM table
• Dock objects
• Schema maintenance
• Server components

Only one single public version of the object is available for all users. Hence, configuration on instances of this object is centrally controlled by the workspace administrator, who can lock all relevant projects and objects. Developers are able to configure the respective objects or projects after their requests to release the locks on these objects or projects are granted by the workspace administrator.

When developers configure non-workspace objects, they must develop and test the non-workspace objects against a dedicated environment and deliver changes (or import using the SIF-OUT/SIF-IN command) directly to the master database by requesting that the workspace administration team unlock the project.

For more information on how to control the access on non-workspace objects, see Controlling Access on Non-Workspace Objects.

NOTE:  In Siebel Tools Innovation Pack 2016, workflow objects were considered non-workspace objects. However, workflow objects are also workspace objects in Siebel Tools Innovation Pack 2017 and the later releases.