# Bulk blueprint updates (force) ## Introduction If you manage blueprint installations on behalf of your child companies, you can use the [installs page](https://doc.wearepatchworks.com/product-documentation/blueprints/working-with-private-blueprints/rolling-out-blueprint-updates/viewing-current-blueprint-installations) to roll out an update (forcibly) to company profiles that you manage (including your own). In one, bulk operation, you can perform the following updates (forcibly) for selected installations: | Action | Typical use case | | --------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Promote a specific version | Particularly useful for testing an [update](https://doc.wearepatchworks.com/product-documentation/blueprints/working-with-private-blueprints/updating-a-private-blueprint) in a a single company profile, before making it [active](https://doc.wearepatchworks.com/product-documentation/blueprints/about-blueprint-versions#the-active-version). | | Promote the `active` version | Particularly useful when you've finished testing an update, have [set it to be active](https://doc.wearepatchworks.com/product-documentation/blueprints/working-with-private-blueprints/changing-the-active-version-for-a-private-blueprint), and now you're ready to roll it out for existing installations. | | Demote an existing installation to an older version | Particularly useful if you have promoted the current active version and experiencing issues - you can roll back to the last sound point whilst working to resolve the issue. | {% hint style="info" %} An alternative approach is to allow child companies to [accept/apply updates manually](https://doc.wearepatchworks.com/product-documentation/blueprints/working-with-private-blueprints/rolling-out-blueprint-updates/accepting-a-blueprint-update-manually), at a time that's convenient for them. {% endhint %} ## Need to know * A blueprint installation must exist before it can be updated. Please refer to [Installing a private blueprint ](https://doc.wearepatchworks.com/product-documentation/blueprints/working-with-private-blueprints/installing-a-private-blueprint)for guidance on installing a blueprint for the first time. * Updates can only be applied for blueprints built and publised on or after 5th November 2025. * Any connector instances that you configured [when the blueprint was first installed](https://doc.wearepatchworks.com/product-documentation/blueprints/working-with-private-blueprints/installing-a-private-blueprint) will persist following any update. * When you promote or demote another version of a blueprint to existing installations, you can choose what should happen with associated process flows after the update is installed. * During the update process, existing process flows associated with the blueprint are 'un-deployed' and at the end, only flows included in the update package are redeployed. So, if an existing process flow has been removed from the blueprint version being applied, it remains in place but is not redeployed. * When a bulk update completes, an email notification is generated and sent to the email address associated with the user who triggered the update, confirming successes and/or failures. ## The steps {% stepper %} {% step %} **Access the installs page for the required blueprint** For detailed instructions, please refer to [Accessing the installs page](https://doc.wearepatchworks.com/product-documentation/blueprints/working-with-private-blueprints/viewing-current-blueprint-installations#accessing-the-installs-page). {% endstep %} {% step %} **Select installations to update** In the upper `installs` panel, select any existing installations to be updated. For example:
{% endstep %} {% step %} **Choose which type of update to apply** If you want to apply the current `active` version, click the `install active` button:
If you want to apply a specific version (for example, if you want to demote an installation to an older version, or if you are testing a later published version before it becomes `active`), click the `install active` button:
{% endstep %} {% step %} **Set update options** If you clicked `install active` in the previous step, you're prompted to choose what happens with associated process flows after the update is applied:
These options are summarised below:
FieldSummary
None

Process flows are installed from the blueprint but not deployed. Any existing deployed versions are unaffected.

For existing flows, the blueprint version becomes the latest draft version.

Any new flows are installed but disabled and un-deployed.

Any existing flows that have been removed from the blueprint are disabled and un-deployed.

Package flows

Creates a package containing all process flows in the updated blueprint. The package name is set to the blueprint name, followed by the version and creation date. For example:



When convenient, you should deploy this package to all required virtual environments.

During the update process, existing process flows associated with the blueprint are 'un-deployed' and at the end, only flows included in the update package are redeployed. So, if an existing process flow has been removed from the blueprint version being applied, it remains in place but is not redeployed.

Package and redeployCreates a package containing all process flows in the updated blueprint, then deploys this package to all virtual environments where a previous version exists (for the selected company profiles).

During the update process, existing process flows associated with the blueprint are 'un-deployed' and at the end, only flows included in the update package are redeployed. So, if an existing process flow has been removed from the blueprint version being applied, it remains in place but is not redeployed.
If you clicked `install version` in the previous step, you're prompted to choose what happens with associated process flows after the update is applied - these options are exactly the same as those in the above table:
However for this update type, you must also choose which `version` to deploy. For example:
{% endstep %} {% step %} **Confirm the update** Having made your selections, click `install active` / `install version` at the bottom of the options modal, to start the update. For example:
The update starts, with progress displayed in the lower [bulk installs](https://doc.wearepatchworks.com/product-documentation/blueprints/working-with-private-blueprints/rolling-out-blueprint-updates/..#the-bulk-installs-panel) panel. For example:
When the update completes, an email notification is sent to the email address associated with the user account that triggered this update. {% hint style="info" %} You can check the status for each selected installation during or after the bulk update run. To do this, access the [installs](https://doc.wearepatchworks.com/product-documentation/blueprints/working-with-private-blueprints/rolling-out-blueprint-updates/viewing-current-blueprint-installations) page and use `view` actions. {% endhint %} {% endstep %} {% step %} **Complete post-update actions** The action required after completing an update depends on which post-install action you selected in step 4. Guidelines are below:
Post-install actionStatus after updateAction required
noneThe previous draft version of any existing process flows associated with this blueprint becomes inactive.

The blueprint version becomes the latest draft version.

Any existing deployed versions are unaffected.		Deploy the latest draft version manually, via process flow settings.

For more information, please refer to Deploying a process flow.
package flowsThe updated set of process flows associated with the blueprint are added to a new package.

Any existing deployed versions are unaffected.		Access the new package and then deploy it to all required environments.
package and redeployAny existing deployed versions are un-deployed.

The updated set of process flows associated with the blueprint are added to a new package.

The new package is deployed to all selected company profiles, and all applicable virtual environments for those companies. The latest set of process flows is enabled and deployed. 		Review process flows in your selected companies to ensure the update has been applied correctly.
{% endstep %} {% endstepper %}