Spinnaker
Spinnaker is the code name for the next major version of Skore. Spinnaker brings many additional features to Skore.
Processes in the “legacy” version of Skore will continue to be editable and viewable at least until end 2022.
The migration tool helps you migrate existing content to Spinnaker to make it easy to benefit the new features. That said, for a “perfect” migration, manual review & adjustments are required.
This guide is for workspace administrators to understand the steps to perform
The migration tool helps doing the “heavy lifting”, but a manual review of the migrated processes is highly recommended.
What is new in Skore “Spinnaker” ?
Spinnaker is the code name of the latest major release of Skore.
See this document.
What is migrated ?
Processes
in Spinnaker processes look the same, but, there has been a major transformation under the hood on how all the content is saved and managed, which was the pre-requisite to unlock all the goodness of Spinnaker.
This is the main migration step required.
- Legacy: “monolithic” XML processes & Business tools (reporting, role manager, etc) only one process at a time
- Spinnaker: managed process data and business tools at the workspace level (example: ability to generate role description from all processes in a workspace)
Texts & Links to other processes
Moving away from markdown to a full text editor.
- Legacy: texts could be formatted using markdown and a system of “shortcode” was used to create links between processes
- Spinnaker: we have implemented a full text editor and links can be created with a “picker”
Roles
Post migration step recommended
- Legacy: roles are defined per process, no central reporting
- Spinnaker: roles are created and managed at the workspace level and can easily be reused in all process maps. Role description are created centrally
When migrating to Spinnaker, roles containing the following will be automatically converted to a system : [SYS] (sys) or those with the following icons : gear or gears
Systems
Post migration step recommended
- Legacy: no dedicated system manager (usually the role manager is “extended” to document systems
- Spinnaker: dedicated system manager
Diagram templates
Post migration step required
From xml based templates that are imported once per process, to a true, “active” template manage centrally
- Legacy: diagram template imported once per process, hard to update all processes to match a new template
- Spinnaker: diagram templates are processes inserted in the background of all processes. Can be maintained separately and have their own lifecycle. changing a diagram template is immediately reflected in all processes
Stylesheets
Post migration step required
From definition per process to a centrally manage stylesheet that can be managed (created, updated) for the workspace
- Legacy: stylesheet imported once as part of the template. Hard to maintain if need to make a change
- Spinnaker: stylesheet created and managed at the workspace level. A change to the stylesheet is immediately reflfected in all processess.
Forms
From XML-based form to a more strictly managed format
- Legacy: forms are defined as XML file, hard to create and maintain, “soft link” with the activity box of a process (i.e. changing a form definition is tricky)
- Spinnaker: forms are defined and stored in the database and “hard link” to the actual box activity content. Ability to create custom forms very easily.
Custom field
From per-process definition to centrally managed custom fields
- Legacy: custom fields are created per process and need to be re-created for each process
- Spinnaker: custom fields are managed centrally at the workspace level and can easily be reused