Switching to the current viflow version
Applies to: viflow ( 8 | 7 | 6 | 5) | Article: 2535808 | Updated on 29.04.2024
viflow is a completely new development from version 7 onwards. Transferring process models from version 6 or earlier to the current viflow format is no longer a conversion, but a migration.
In this article, you will learn what you need to consider when switching from an older to the current viflow version and what effort you should expect.
Upgrading from viflow 5 or earlier
The migration is very complex and cannot be carried out without our support.
Estimate the workload for migration
Depending on the scope and level of customization of your viflow model, the amount of work required for migration can vary. We would be happy to estimate this for you. To do this, we need detailed information about your process model.
Please use the following online form: ››› Estimate the workload for migration.
You should know about these changes in viflow
- SPM (Shared Process Modeling) is no longer available in this form in the current viflow. If you want to work on the process model with several people at the same time in the future, you will need a Microsoft SQL Server on which the process model is stored as a database.
- Graphic templates and shapes are no longer externally connected data, but are now integrated into the process model. If necessary, these must be imported into the process model after the technical migration.
- The short and long names of processes are swapped during migration.
- Areas that were used, for example, as modelers, approvers, reviewers or responsible persons are now managed under users and created accordingly during the migration. This can lead to duplication in the new process model.
- Potentials and measures are now also globally available and part of the process model. They also have the properties Name and Comment.
Switching from viflow 6
The migration is complex, but can be carried out independently by experienced users using a migration guide.
Alternatively, we can carry out the migration for you – you can get an estimate of the effort required.
Download migration guide
To convert your process model from viflow 6 to the latest viflow version, we have developed a guide that takes you step by step through all the necessary work:
››› Download migration guide (German).
Estimate the workload for migration
Depending on the scope and level of customization of your viflow model, the amount of work required for migration can vary. We would be happy to estimate this for you. To do this, we need detailed information about your process model.
Please use the following online form: ››› Estimate the workload for migration .
You should know about these changes in viflow
- SPM (Shared Process Modeling) is no longer available in this form in the current viflow. If you want to work on the process model with several people at the same time in the future, you will need a Microsoft SQL Server on which the process model is stored as a database.
- Graphic templates and shapes are no longer externally connected data, but are now integrated into the process model. If necessary, these must be imported into the process model after the technical migration.
- The short and long names of processes are swapped during migration.
- Areas that were used, for example, as modelers, approvers, reviewers or responsible persons are now managed under users and created accordingly during the migration. This can lead to duplication in the new process model.
- Potentials and measures are now also globally available and part of the process model. They also have the properties Name and Comment.
Switching from viflow 7 or 8
Switching from viflow 7 or 8 to the latest viflow version is easy. When you open a process model created with viflow 7/8 in viflow, a conversion starts. The process model can then no longer be opened with older viflow versions.
From viflow 8 – new system requirements for the WebModel
In viflow 8, the WebModel has been fundamentally revised; a web server is required for display.
The current system requirements for the viflow versions and the WebModel can be found in the following article:
››› System requirements for viflow