Working with private blueprints

Introduction

The most typical use case for a private blueprint is if you manage multiple company profiles and need to share a collection of process flows between them.

Having built and tested the required process flows in the 'parent' company, you can add them to a blueprint. When a process flow is added to a blueprint, all associated resources are included - i.e. connectors, scripts, caches, cross-reference lookups, and data pools.

Having built and published a blueprint, it is added to your private marketplace, where it can be installed by any 'child' companies.

If you need to update an existing blueprint, you can make the required changes and publish a new version. Depending how you need to work, this update can be accepted by each child company individually, or you can force a bulk update to selected child companies.

More information

• Building a private blueprint

• Installing a private blueprint

• Updating an existing blueprint

• Changing the active version of a blueprint

• Rolling out blueprint updates