Skip to main content
Version: 6.0

Upgrading and Support Help

warning

This section is aimed at support consultants and ships

Upgrade process​

During the upgrade to 5.2.1 structural changes are applied to how templates are stored, as well as changes to data currently in the database:

  1. Due to a legacy product, the Stargate Portal, numerous references to (irrelevant) templates were stored in the database but were not visible. During the upgrade process those not visible in the current system (not referring to the visibility settings on the template) are deleted.
  2. An external reference is also associated with each template that can be used in template portability to identify a template and prevent duplicates.
  3. Template groups are also now open to be changed.

Suggested actions for Support Ships​

Upgrading the client​

  1. After upgrading the database, it is recommended to install the Special templates. The .cmt file is distributed with 5.2.1 in the CaseManagerTools folder.
  2. Many templates (both Reports and Documents) will be visible in the Configuration Tool after this upgrade. We recommend cleaning up the templates, deleting all not found and not applicable to the client’s business.

Managing templates at a ship​

  1. We strongly recommend that Ships reevaluate how templates will be managed for their clients, since we will not have a single database with all the template references anymore.
  2. Export client-specific templates in CMT files and safeguard.
  3. Evaluate all the reports and documents we have available in general to clients. We should work towards a repository of these per industry.
  4. Keep record of the External references used for templates. These values are used to identify the templates at a client’s site. When importing a template with the same reference it will update the entry and not create a new template entry.

Standardise template packages​

With the new functionality in 5.2.1, we will be able to create packages of templates that address a specific subsection of clients. This can be based on locality, industry, or language. We should organise the available templates in such packages. In a future version of Case Manager, the clean database will no longer ship with any standard references to reports or documents. These packages will be the only way to import content templates in Case Manager.