This content is dedicated to our next version. It is work in progress: its content will evolve until the new version is released. Before that time, it cannot be considered as official.
Migrate a form from 6.x
Attention: Starting with Bonita 7.8, 6.x GWT forms and case overview forms are not available for both modeling and execution. To perform the operations listed below, you will need to import your processes in a Bonita Studio of any version up to 7.7.x, and build new versions of your processes before migrating to 7.8.0 or above.
There is no specific tooling to assist with migration, and you do not have to migrate all apsects of a process definition at the same time.
You can take a staged approach, testing that your process continues to behave as expected after each change.
The most efficient sequence for migrating a process and its forms to benefit from Bonita 7.x features is as follows:
BDM: create your business data model. If you already have a BDM from 6.x, no change is needed.
Business data: if you have created a new BDM, populate your business data database by importing it from where it was previously stored (process data or external data).
You can do so with a process that uses a connector to retrieve external data and an operation using the REST API to store the business objects.
Process: check that the process runs with the business data, and update it if necessary.
Contracts: define contracts based on your business data, for process instantiation and for each human task.
Forms: generate the forms from the contracts into the UI Designer, then update them as needed.
In the Studio, at pool level and for each human task, go to the Details panel, Execution tab, Form section, and change the option from Legacy (6.x) to UI Designer. You can also generate them in another development environment. In this case, choose External URL option.
When you export a diagram, forms created in the UI Designer are embedded by default in the .bos and .bar files, to share between Bonita Studios (.bos) or install in a Bonita Applications (.bar), so you don’t need to manually export them and import them one by one.