# Accepting a blueprint update manually ## Introduction As the blueprint owner, you can make updates available, but the child company decides when to accept/apply them. This ensures that updates are applied at a convenient time, maintains transparency, and avoids unexpected changes to live integrations. When an existing blueprint is updated and [set to active](https://doc.wearepatchworks.com/product-documentation/blueprints/working-with-private-blueprints/changing-the-active-version-for-a-private-blueprint), an `update available` indicator is added to this blueprint in the private marketplace for any 'child' company profiles where it's installed. Child company users (with [appropriate role permissions](https://doc.wearepatchworks.com/product-documentation/users-roles-and-permissions/roles-and-permissions-summary#private-blueprints)) can then accept the update at their own convenience. ## Need to know * 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 choose to update a blueprint, 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. ## The steps {% stepper %} {% step %} **Log in and switch to the required company profile** Log in to the child company dashboard. {% endstep %} {% step %} **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 from the 'parent' company, or from the child company itself. {% endstep %} {% step %} **Select the blueprint with a pending update** Select a blueprint with an update available flag - for example:

The blueprint manifest is displayed for the version that's currently installed. For example:

{% hint style="info" %} If necessary, you can choose to deselect items shown here. However, keep in mind that blueprints are designed and configured to work with the resources shown - you should only deselect items if you are confident that it's safe to do so. {% endhint %} {% endstep %} {% step %} **Switch to the active version (optional)** If you want to review the contents of the `active` version, click in the version field and select the `active` version. For example:

{% endstep %} {% step %} **Install the active update** Click the `install active version` button at the top of the page. For example:

{% endstep %} {% step %} **Choose install options** Choose what should happen immediately after the installation has completed. For example:

Available options are summarised below:

Field Summary

None

Field	Summary
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 redeploy	Creates 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.

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 redeploy Creates 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.

{% endstep %} {% step %} **Confirm the update** Having made your selections, click `continue` to start the update. For example:

{% endstep %} {% step %} **Review detected changes** Any changes detected as a result of installing this update are displayed for review. For example:

If you're satisfied that these changes are correct, click `proceed` to perform the update:

{% endstep %} {% step %} **Complete post-update actions** Action required after completing an update depends on which post-install action you selected in step 7. Guidelines are below:

Post-install action	Status after update	Action required
`none`	The 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 flows`	The 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 redeploy`	Any 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 %}