Content Comparison

NOTES:

• Be aware that since there is only one windows installer package, there is no possibility to separately install an additional component on a machine where a Flowster Studio installation already exists. If a situation requires to install several Flowster Studio components besides the Engine Core, the client will have to check all features that they want deployed. The installer UI dialogs will have the respective features' settings areas enabled/disabled depending on the initial selection. E.g. if one decides to install the Additional Engine, Execution Agent and WebApps, their settings areas will be enabled, whereas the Designer and WebPortal settings areas will be disabled and disregarded during the installation. This will also cause dialogs that have become irrelevant to be skipped.
• Starting with Flowster Studio 5.3, the installer will allow the user to change a deployment post install (maintenance mode), albeit with some limitations that will be detailed in its dedicated chapter.
• Launching Flowster Studio Designer with a user that does not have write access on the installation path will cause it to be unable to update the Activity Library from the Centralized Repository Path. In order to prevent this, it is recommended to install Flowster Studio deployments that contain the Designer feature to a path where the users have sufficient permissions.
• Please review the Flowster Studio System Requirements before continuing.

...