Migration from 5.5.x

Data Platform

The Data Platform client-side database is moving to <workspace>/_Data/db-cache.tdb (from <workspace>/Cache/db-cache.tdb)




Job Titles in the Governance Framework:


Phase-out of Job Titles: The EDG Governance Model allows the creation of an organizational structure, and the assignment of users and security roles to the organizational hierarchy. In previous versions, it was necessary to create Job Titles for each organization. Users and security roles were then assigned to those Job Titles. This indirect assignment through Job Titles has proven to be cumbersome and to add little value. Starting with EDG 6.0, Job Titles will be phased out.

In 6.0, there is a setting “Enable Job Titles” in the EDG Configuration. It is off by default, and should be left off for new deployments. In this mode, Job Titles are disabled, and users and security roles are assigned directly to organizations.

If you already have created Job Titles in the Governance Model, you must set this setting to true. In this mode, EDG 6.0 will behave the same as the previous version with regards to Job Titles.

We expect to remove support for Job Titles completely in a future release. Therefore, if you currently use job titles, please contact TopQuadrant support to discuss migration options.


Viewers cannot create working copies:


In some previous versions, permission to create new working copies/workflows was affected by a configuration option: Viewers cannot create working copies. This option has been removed.

If the option was OFF (the default), EDG 6.0.0 will behave the same as before.

If the option was ON, then the following needs to be considered:

  • Any users or security roles that are directly assigned as Viewers on the Users tab of an asset collection will now be able to create working copies/workflows. This is a change in EDG 6.0.0.
  • Users or security roles that have a governance role on the asset collection will now be able to create working copies/workflows. This is a change in EDG 6.0.0. However, this ability can now be disabled for selected governance roles, under: Server Administration > Setup > EDG Configuration Parameters > Governance Roles.

An asset collection is in at most one governance area

Asset collections can no longer be assigned to multiple governance areas. Any collection with multiple areas should delete its area associations, leaving at most one (see collection utilities: Settings > Metadata > subject area).

Manage utilities > SPIN Constraint Libraries and See Customized Forms

From 6.0, these features have been disabled, and users are encouraged to migrate to SHACL. If required, these features can be reactivated locally (contact customer support), but keep in mind that they will be removed in a future release.


Migration of Development Customizations



Ontologies no longer import SPIN by default, neither does the standard teamworkconstraints. If your ontologies have relied on the latter owl:imports (transitively), you need to add the SPIN Standard Library (SPL) to your includes by hand. (cf. Developer Guide: Creating and maintaining new SPIN constraint libraries – DEPRECATED))


The non-SHACL approach for customizing form layouts is now deprecated and will be removed in a future release. Please use SHACL constraints to customize form layouts. See the Developer Guide: Customizing Form Layouts.


Teamwork project type

  • Any custom teamwork:ProjectType should be extended with a teamwork:isReadOnlyTypeFunction triple similar to the value of the original project type that they were cloned from.
  • The teamwork:projectHeaderBar extension point for teamwork:ProjectType has been removed. Contact TopBraid Support for migration advice.


Beginning in 6.0, there is a new mechanism for adding custom tabs to asset collection views.

  • This change affects any 5.x customizations that use teamwork:ProjectTab or teamwork:TagTab. These need to be modified as described in the DeveloperGuide: Adding New Tabs for Asset Collections.
  • Customizations using the swa:TabsActivationScript element or the swa.initTabs JavaScript function might need updating. To retain the SWA-specific styling, add class="swa-tabs" to the tab container. Otherwise, the tabs will use the jQuery UI tabs style. Furthermore, the active tab is no longer remembered between page reloads, and is no longer reflected as a #fragment in the URL.