Updating a private blueprint

Introduction

As a user associated with the company profile that built a blueprint, you can make changes to the blueprint and publish an updated version. This guide walks through the steps required to achieve this.

Suggested workflow for updating blueprints

The suggested workflow for updating and then rolling out a private blueprint is as follows:

1

Make changes to the blueprint and publish a new version Make your required changes in a draft, then publish a new version (as detailed below).

At this point, the updated version is not active - i.e. it will NOT be installed if someone chooses to install this blueprint from your private marketplace. For more information about the active version of a blueprint, please refer to What is the 'active' version of a blueprint?

2

Promote this version for testing Promote this version to one 'child' company (or your own company) for testing.

For testing purposes, you may choose to install a new blueprint in your own company, or to have a dedicated 'child' company for testing.

3

Test the blueprint Install and test the blueprint. If necessary, make and publish further updates (promoting each one to your test company for checks).

4

Set the final version as active When you're satisfied that a published version is ready for general use, set it to be the active version.

5

Promote the update to existing installations You can promote the update to any existing installations as a bulk operation, or choose to promote the update to individual installations.

Need to know

  • You can add new and remove existing process flows when updating a blueprint. When an existing blueprint installation is updated to this version, all associated process flows are 'un-deployed' first. If you have removed a flow from the updated version, that flow remains in place, but it is not redeployed for the company.

  • You can change the component parts of an existing process flow in a blueprint - for example, applying different connectors, cross-reference lookups, or scripts. When an existing blueprint installation is updated to this version, the new components are installed; the old components stay in place but are not referenced in the updated flows.

  • Each time a draft is published, a new version is generated. All previous versions are retained, so you can demote to an older version in future, if required.

The steps

1

Log in to your own company profile

Log in to the dashboard and (if you're managing multiple company profiles) ensure that you've switched to your own profile.

2

Access private blueprints

Select marketplace from the left-hand navigation menu, then select blueprints and private tabs. Here you will see any blueprints that have been built by users associated with your company profile.

3

Access the manifest for the required blueprint

Click the blueprint tile that you want to update. For example:

The blueprint manifest is displayed. For example:

4

Open a new draft

Click the ellipsis icon at the top of the page:

Then select the open draft option:

5

Make your changes

The blueprint manifest opens in draft mode so you can adjust flows and (if necessary) components as needed:

Remember that adding a process flow to a blueprint also adds its components (such as connectors, scripts, cross-reference lookups, etc.).

6

Publish the updated version

If you're ready to make this version of the blueprint active, click the publish button at the top of the manifest. For example:

7

Post-publish actions

Next steps are detailed in our suggested workflow, above.

PreviousInstalling a private blueprintNextChanging the active version for a blueprint

Last updated

Was this helpful?