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.
Need to know
A blueprint can have up to ten versions. If you attempt to publish a new version that would exceed this limit, you are prompted to confirm the deletion of the oldest version (first in, first out). For more information, please refer to About blueprint versions.
When updating a blueprint, you can add new and remove existing process flows. 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, apply 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.
Suggested workflow for updating blueprints
The suggested workflow for updating and then rolling out a private blueprint is as follows:
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).
Promote this version for testing Promote this version to one 'child' company (or your own company) for testing.
Test the blueprint Install and test the blueprint. If necessary, make and publish further updates (promoting each one to your test company for checks).
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.
Promote the update to existing installations You can force a bulk update, or allow child companies to accept the update manually.
The steps
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.
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.
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:
Open a new draft
Click the ellipsis icon at the top of the page:
Then select the open draft option:
Make your changes
An empty blueprint manifest opens in draft mode so you can add the required flows and (if necessary) adjust components as needed:
Ensure that all process flows to be included in the blueprint are selected. If a process flow is not selected, it is not included.
Publish the updated version
If you're ready to install/test this version, click the publish button at the top of the manifest. For example:
A blueprint can have up to ten versions. If you reach this limit and attempt to publish another version, you are prompted to confirm that the oldest version can be removed. For example:
If you would prefer to remove a different version to make way for a new one, select cancel and then delete the required version before trying the publish operation again.
Also note that if the oldest version is also the active version, it can't be deleted automatically. In this case, you'll see an error message when attempting to publish a new version - for example:
In this case, you need to change the active version before trying the publish operation again.
Post-publish actions
Next steps are detailed in our suggested workflow, above.
Last updated
Was this helpful?