Migrate from Flow Classic
Last updated
Last updated
You can import workflow archive files (wap-files) from Flow Classic into an Application Package in Flow Connect.
Begin by exporting your workflows, along with all dependencies, from Flow Classic.
To do this, navigate to Flow Classic Studio. From the server content view, choose the folder containing the workflows you wish to export. Then, save the wap-file to your disk.
The workflows contained within the archive will be imported into an existing package. You have the option to use an existing package or create a new one if needed.
Open the Flow Connect Designer and select Import Archive from the File menu.
The import wizard is started:
Select file to import.
Choose Organization.
Choose destination Application Package.
Map the connectors used in the workflows to then ones you have in the organization.
Confirm the content preview.
Done.
Open the package you selected during import. You should now see your imported applications and components. These items will initially be in an error state, requiring you to open and review them in the Designer.
If your application contains components, you need to make your first committed version of each component before they can be used by applications.
Locate your component and right click and select Edit Component to open.
Check the Problems tab to check for errors.
Typical errors might be that we are referencing a global Flow property that is not yet created in Connect or errors that wasn't possible to fix automatically in the new version of FlowScript.
When there are no errors left in the component, commit your first version.
When components are committed, refresh the components in your application. Components will be refreshed and display the current version of the component.
Review and handle errors in the application. Dubbel click on the the error and the step will be highlighted.
Run your app in diagnostic mode to verify that it works .
