What is a Preset?

Presets store configuration settings for a Tracability Browser setup.

Why migration is required?

Presets were introduced in 9.5. Later in 10.0 the functionality was totally rewritten and enriched in 10.0 which backward compatibility issues: Presets that were created in 9.5 did not show up in releases after 10.0, because of compatibility issue.

This is why an upgrade script added to Carmen which updates presets of 9.5 release to Carmen compatibility one during the upgrade process.

Permission changes during migration

Previously presets were created by the system admin and they were accessible (read) to all project users.

In the new version, each preset has its own permission settings: The owner can set read/ write privileges to each role one-by-one or simply create a private one.

During migration Project Admin gets read and write permission to each preset that is newly imported, while all other roles get read-only access.

Project Admin can update each permission of a given preset after import.

Migration limitation

Initial level with views and branches:

• Branch information is thrown away.
• Each default view is converted into 'All Item'.
• Views created by the user:
  • If only one view is in use, then it is imported, else all view information in converted into 'any', so all element is loaded for the belonging tracker type(s).

And - Or logic:

• And - Or logic is thrown away if it is used in the old preset configuration.
• If And-Or logic was used in a view. see view limitations under (Initial level with views and branches).