Hub Docs User documentation
Back to home
Hub Docs

Blueprints

What it is

A Blueprint is a single bundle that defines what kind of product something is. Each Blueprint owns one process and the attribute schemas for the products, subscriptions, and payment line items that use it. Once a Blueprint is published, any Product created against it inherits its process and its attribute fields automatically.

Think of a Blueprint as a template: "Here's how a Salary Sacrifice scheme works — this is the process that runs it, these are the fields a Product of this kind needs, these are the fields each Subscription stores, and these are the fields on each Payment Line Item."

When to use it

Reach for Blueprints when you're an operator setting up a new family of financial products. For example:

  • Defining a new pension product line where every Product on it shares the same process and the same attribute schema.
  • Adding new fields that should appear on every Subscription tied to a particular product family.
  • Splitting a single process into a reusable template that several Products can be created from.

If you're configuring a one-off automation that doesn't represent a Product, use Processes directly instead.

Where to find it

Open the Tenet admin Space, find the Product sidebar items, and click Blueprints. The page lists every Blueprint with the process it owns and the number of attributes it defines.

Processes of type Product don't appear in the main Processes list — you reach them through their Blueprint.

How it works

Creating a Blueprint. Click New Blueprint on the Blueprints index. Give it a name and save. Hub creates the empty Blueprint and opens it for editing.

The editor. Each Blueprint opens in a sidebar layout with the following sections:

  • General — name, description, and basic settings for the Blueprint.
  • Workflow — the one process this Blueprint owns. From here you can open the visual editor and configure triggers, steps, and outputs.
  • Runs — every run of this Blueprint's process, with status, trigger, and start time. Click a row to open the live run view.
  • Attributes → Product — fields stored on every Product created against this Blueprint. The badge next to the link shows how many fields are defined.
  • Attributes → Subscription — fields stored on each Subscription that joins a member to a Product of this Blueprint.
  • Attributes → Payment Line Item — fields stored on each payment line item generated by Products of this Blueprint.

Adding attributes. Inside any of the three Attributes panels, add fields the same way as in the global Custom Attributes page — give the field a name, choose a type, mark it required if needed. Attributes you add here are scoped to this Blueprint only, so two Blueprints can each define their own "Contribution Rate" without colliding.

Publishing. A Blueprint must have a published process before any Product can be created against it. Until then, the Products page won't let you select it.

One process per Blueprint. Each Blueprint owns exactly one process, and a process can belong to only one Blueprint. If you need a different process for a different product family, create another Blueprint.

Related