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

Controlling Access on Non-Workspace Objects

Currently, the following object types and their child objects remain as non-workspace objects:

• Table
• Dock Object
• EIM Interface Table
• Repository
• Workflow Policy Column
• Workflow Policy Object
• Workflow Policy Program
• Task
• Task Group
• Project

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.

For changing the existing database schema or adding new tables to the database schema, all users must follow the same process that is currently followed by all development teams; that means, respective teams need to cooperate with the workspace administrators for any change that is required in the database schema of their applications.

For Workflow and Task configurations, developers must ensure that only the 0th version on the master database exists.

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

NOTE:  The project must be locked for non-workspace objects before the object can be modified. The locking and unlocking of projects can be controlled by an administrator.