Building & uploading private blueprints

All pages in the Building & uploading private blueprints section are currently under review.

Introduction

The most typical use case for a private blueprint is when a partner company wants to share a collection of process flows with its child companies.

Having built and tested the required process flows, 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. If yours is a partner company, the blueprint will be available in the private marketplace for any of your linked (i.e. child) companies, ready to install.

If you need to update an existing blueprint, you can make the required changes and publish a new version.

More information

• Building & publishing a private blueprint

• Installing a private blueprint

• Updating an existing blueprint

• Changing the active version of a blueprint

• Viewing & managing blueprint installations