Configuring Non-Workspace Objects
The following object types and their child objects are non-Workspace objects:
-
Dock Objects
-
EIM Interface Table
-
Project
-
Schema maintenance
-
Server components
-
Repository
-
Table
-
Type
-
Workflow Policy Column
-
Workflow Policy Object
-
Workflow Policy Program
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 the 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 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 standard database exists.