Before continuing, please review the Flowster Studio System Requirements.

Additional note: this chapter describes the upgrade from Flowster Studio 4.8.47 Main Engine + All features selected. It is highly recommended to backup the existing databases prior to the upgrade.
UAC Enabled
If UAC is enabled on the machine, when starting the EXE, credentials for a privileged user will be required, in order to properly install Flowster Studio.

In order to start the upgrade of the Flowster Studio Main Engine, run Flowster Studio Setup.exe.
The UI application will detect that a previous version of Flowster Studio exists and will retrieve the previous settings used for the installation.
If you're upgrading from a Flowster Studio versioned lower than 5.0, you will first be informed that the persistence status of any persisted workflows will be lost:
Clicking Cancel will stop the installer, allowing the user to manually stop any persisted workflows, while the OK button will continue to the Flowster features dialog:

Please note that all features have been selected. The Features dialog will reflect the feature selection from the Flowster Studio version that you are upgrading from. E.g. if a client only has the Flowster Studio Engine Core feature installed on a machine, the other features would be unchecked.

Check/uncheck the features you want deployed during this upgrade, keeping in mind the first two bullets in the notes at the beginning of the chapter.
Make sure the location where Flowster Studio will be deployed is correctly retrieved and update if necessary.
Click Next. The Database settings dialog will be displayed:

The Values in the MS SQL Server Instance, Flowster Main database and Flowster Tenant database have been prefilled with the values used in the deployment of the previous version. It is recommended you continue with these values.
Select the SQL Server authentication type. In case of SQL Server authentication, provide the user and password for the SQL Server connection.
Press Next. The installer will take several seconds to contine, as it will be retrieving data from the existing database to prefill the fields of the upcoming dialogs. The Flowster Studio users dialog will be displayed:

Please note the Use LDAP Connection checkbox is disabled, because changing its setting during upgrade scenarios would cause Flowster Studio functionality issues.
The LDAP server will have its value prefilled with the LDAP used by the previous Flowster Studio version, with the Secure LDAP port appended. It is recommended to continue with this value.
Check/uncheck the Use SSL checkbox.
Add a value for the AD Site to be used by the Active Directory entry used by Flowster Studio (optional).
The value for the AD User will be prefilled with the user that was previously used for AD operations (Service user before Flowster Studio 5.2). It is recommended to continue with that value and fill the password for LDAP authentication during the installer.
Select the Domain format for portal authentication:
- NetBIOS domain name (the adjacent edit box will be prefilled with the system one, but can be customized)
- Fully Qualified Domain Name (the adjacent edit box will be prefilled with the system one, but can be customized).
The Service user field is prefilled with the identity that's currently executing the installation. Please update it to the identity that will be running the Flowster Studio services (if the prefilled one is incorrect) and provide the Password and Password confirmation.
Note that the System superadmin area is disabled, as one already exists.

Press Next. The Flowster Studio engine settings dialog is displayed:

Note the RestAPI client settings and Default Flowster Instance settings areas being disabled, as one of each already exist in the database.
The Tenant name, Number of votes to turn a task active and Communication ports fields have already been prefilled with existing values.
- Exception: The upgrading from a Flowster Studio version lower than 5.0, the Compatibility service will have its value prefilled with the default value, as the service did not priorly exist.
Select the Default tenant language from the adjacent combobox (available values are en-US and de-DE)
- This setting will set the default language for all tenants and, if selected with the main engine upgrade – the scenario presented here -, the Flowster Studio WebPortal's login page. Installing Flowster Studio WebPortal as a separate component will have the login page set to English.
- This setting will only be enabled for main engine upgrades from Flowster Studio versioned lower than 5.2.
Check/uncheck the Update existing centralized repository files option. If no custom activity libraries exist on your system, it is recommended leaving the option checked.
The Centralized repository path field will be prefilled depending on what Flowster Studio version you are upgraded from:
- Lower than 5.0: it will be an installer-defined default value. It is recommended to update the value to a valid path. If the deployment plan calls for Designer/Execution Agent components connected to this Flowster Studio Engine to be deployed on other machines, it is recommended to use a network share.
- 5.0 and up: it will be the path used for the previous installation. It is recommended to use the prefilled value.
Press Next. The Flowster Studio Components settings dialog will be displayed:

The fields are prefilled with previously used values. It is recommended you continue with the prefilled values.
- Exception: As of Flowster Studio 5.0, the Execution agent name is no longer customizable, and is hardcoded to the value of the current machine hostname.
Press Next. The second Flowster Studio Components settings dialog will be displayed:

The fields are prefilled with previously used values. It is recommended you continue with the prefilled values.
Press Next. The second Flowster Studio SSL Certificate settings dialog will be displayed:

Select the desired SSL certificate options and press Next. The Ready to install dialog is displayed:

Under the Engine selection area, tick the checkbox if the engine selection should be enabled for Designer and Portal logins. Once checked, the Use DNS records for engine server selection will be enabled.
- If the environment is setup as such, check the Use DNS records for engine server selection option and enter the DNS Records address.
In order to start the installation, click Install.
A progress dialog will be displayed (windows installer), followed by a Result.
The installer will create shortcuts for Designer, WebPortal and WebApps on the AllUsers desktop and StartMenu, if the features were selected.

Browser not supported