Skip to main content

Promoting new releases

When you first import a project to a prod environment you will need to do so manually, in order to allow you to create / select the correct prod authentications.

Imports thereafter can be done programatically via API (unless breaking changes are introduced)

Promoting your first release​

caution

If you are importing a solution which has a Custom service, you will have to modify your exported JSON. Please see the 'Importing Solutions with a Custom Service' section below for more details.

env-promotion-new-release

For testing and publishing the first version of your solution, the basic process is as follows:

  1. Create and test the workflow(s), project and solution you are wishing to publish, using test/sandbox accounts and test data.

  2. Once you are ready to publish the first version of the solution to production, export the json file of the project to your local machine.

    [IMAGE]

  3. Now create a new 'production' project in your production account. You do not need to add any workflows at this stage:

    [IMAGE]

    Once created, you can enter the project from your dashboard, and you will have the option to Import from project and pick up the json file.

  4. When you first import the project you can select pre-existing 'prod' authentications for the services included in the project's workflows (or create new ones on the fly):

    [IMAGE]

  5. Set any necessary prod config data

  6. Publish the new Solution

The new version of your solution will be available for use in your external application

TODO:

Sid:

  • Test importing custom services
  • Test importing custom service environments (OAuth apps)