Project cannot be upgraded forms not supported

Summary

Query forms and Management Forms for Parameter entities were designed, up to version 10.5, in Bizagi's traditional design environment.
From version 10.6 these forms are created in the new v10 Forms designer. All new Query Forms and Management Forms for Parameter entities will be created in the new Forms Designer version, in order to benefit from the new version's Forms designer:
- New and modern look of the forms in the Work Portal.
- More powerful and appealing UI for human Activities, which include: a friendly layout distribution, improved actions and validations and support for mobile devices (smartphones, tablets, etc).

When upgrading a project to Bizagi 11 it is necessary to migrate all existing forms built in the traditional forms designer. We recommend requesting our assistance and professional services (creating a ticket), so that we can help by using our internal tools to migrate the forms to the 10.x technology.

If you want to try the procedure b yourself, keep in mind that to upgrade to Bizagi 11 it is necessary to first upgrade the project to Bizagi 10.7 and then use a tool to migrate these forms. Once all forms are in the new forms designer you will be able to upgrade the entire project to version 11.

The upgrade of your project SHOULD be done first in the Development environment through Bizagi Studio.If Bizagi is not able to upgrade one (or more) of the project's forms, you can find the errors in the path: C:\Bizagi\Trace

Applies to

Bizagi 10.x migrating to Bizagi 11.x

Steps

Enable the migration possibility

1. Ensure you have closed Bizagi Studio.

2. Edit the appSettings.xml file located at the default Bizagi Studio installation path.By default this path is set as a hidden folder of the OS, and usually at: C:\ProgramData\BizAgi\BizagiStudio\.

3. Make sure you set the following two keys enabled: <add key="ShowFormsMigrationTool" value="true" /><add key="EnableQueryFormsForMigration" value="true" />

Running the Forms Migration

1. Locate the Tools tab in the Ribbon, and click on the Forms Migration Tool.

You will be prompted will a message, click ok.

2. There are three options available: Process, Entity and Query Forms.

To migrate Management Forms go to the Entity tab and choose the ones you want to migrate. Then click the Analyze button.

Bizagi will start to run the forms migration analysis and indicate the progress status:

3. When finished, export the analysis results and detail log into an Excel file. For this, use the Export results option (requires Excel).

Resolving errors

Resolve any errors shown by the analysis results (marked with a red X icon).

It will not be possible complete migration of your forms if there is at least one error.

The detail log and issue’s message and solution, will allow you to estimate the required effort in your forms migration (should there be any additional configuration or redesign involved in your current controls).

If a form is already in the Production environment, it will not be migrated. You need to go to the Form, create a new version and then migrate it.

NOTE: Warnings are shown with a yellow triangle icon. A Warning indicates that you will need to pay special attention to a given form, in which Bizagi has performed automatic adjustments. It is recommended that you ensure and explicitly review that the form behaves as expected (this includes testing its actions and validations).

Applying changes

Once you have resolved your errors and warnings, run the analysis of the Forms migration again.

When the analysis shows no errors, you may proceed to apply the migration to your forms.

To do this, click on the Apply button in the Apply changes option:

Now your forms have been migrated and you may close the Forms Migration Tool window.

Testing the process

Keep in mind that it is important to carry out the proper tests in order to verify that these Processes and their forms behave as expected.

Carry out strict unit tests and user-acceptance tests, and ensure that the migrated Processes follow the recommended Deployment cycle.