Skip to content

Deploying Solutions

You can use the Studio to export a Solution that can then be used on another ThinkAutomation Server instance.

On the ThinkAutomation Studio ribbon, select the Explorer tab. Select the Solution to deploy from the Solution selector. You can choose to export the Solution to a package file, or deploy the Solution to another server. Click the Deploy Solution button.

Save Solution As A Package File

You can export a Solution to a ThinkAutomation Solution Package File. The Solution can then be imported into another ThinkAutomation instance. The solution package file will contain all Message Sources & Automations for the Solution along with any Custom Actions that any of the Automations in the Solution use.

Previously exported Solution files can be imported using the ThinkAutomation Studio - File menu - Import Solution. When a Solution is imported its Message Sources will be marked as disabled so that processing does not start immediately after import. Mark the Message Sources as enabled when you are ready to begin processing.

Solution package files are encrypted and cannot be read outside the ThinkAutomation Studio, so package files are safe to be sent by email.

Deploy Solution To Another Server

This option can be used to directly deploy a Solution to another ThinkAutomation instance. All Message Sources, Automations and any Custom Actions will be saved to the other server. This option is useful if you have different development and production ThinkAutomation instances. You can develop and test your Solution on the development machine and they deploy it to another instance when ready.

You must specify the ThinkAutomation Server, Username and Password of the ThinkAutomation instance you want to deploy to. The Server address can be the IP address or computer name.

If the Enable Message Sources Once Deployed option is enabled then any Message Sources will be marked as enabled and processing will start. Otherwise the Message Sources must be manually enabled using the Studio.

Click the Deploy button to start. If the Solution already exists on the target instance then it will be updated, otherwise a new Solution will be created.

For Message Sources that uses OAUTH authentication (Office 365, Gmail etc) the authentication information will also be sent. This differs from the Package File option which does not save authentication - so users must re-authenticate after importing.