For the complete documentation index, see llms.txt. This page is also available as Markdown.

Blueprints

A template sets the rules. A blueprint is where the work happens.

Each blueprint combines a template's structure with selected ServiceNow elements, future-state planning, canvas layout and compliance context.

Blueprints are ServiceNow records under the x_inpi_ydbp scope. What you can do in the Blueprint Editor depends on your role. See Roles and Permissions for details.

Create a blueprint

On Home, click New Blueprint to open the Select a Template dialog. Then:

  1. Search by name or filter by Category to find the right template

  2. Click the chevron on a template to inspect its tables, relationships, and rules first if you want

  3. Click the template to create the blueprint

The app opens the new blueprint in the Blueprint Editor.

Blueprint Editor layout

The Blueprint Editor has the same basic working model as the Template Editor, but the purpose is different.

The header shows the blueprint name, a details action, the current compliance score, Save/Update, a menu for blueprint actions, and Commit (when there are pending publishable changes).

Left: Data Hub

Use the Data Hub to load records from the tables already defined in the template.

You can choose a source table, search and sort records, expand hierarchies where available, and drag or double-click records into the blueprint.

Center: canvas

The canvas shows the table cards defined by the template and the elements you have added.

Use it to arrange the layout, inspect relationships between tables, and review where data is present or missing.

Right: Data panel

The Data panel shows blueprint details when nothing is selected, table-level rules and filters when a table is selected, and field or relationship details when an element is selected.

Blueprint details

Blueprint details include the template it is based on, the blueprint name, description, status, target date, owner, and the last update timestamp.

These fields help other people understand the blueprint without opening every element.

Save/Update versus Commit

These two actions are intentionally different. The header button shows Save for new blueprints and Update after the first save.

Action
Use it when
What it does

Save/Update

You want to store working progress without publishing it back to ServiceNow yet.

Saves blueprint metadata, canvas layout, staged future-state work, relationship staging, and blueprint-specific view or organization choices.

Commit

Approved blueprint work should be published back to ServiceNow.

Runs the controlled commit workflow that publishes approved changes beyond the working draft.

This is a controlled workflow and is separate from normal saving.

Commit Progress dialog

When you commit, the app opens a Commit Progress dialog that tracks the operation in real time.

The dialog shows a progress bar, the count of successful operations, the count of failed operations, and a list of any issues detected with the specific elements or relationships involved.

When the commit finishes, dismiss the dialog with Esc or the Close button. Failed items remain in the working draft so you can fix them and try again.

Working safely

The Blueprint Editor protects unsaved changes.

If you try to leave with pending work, the app asks whether you want to stay on the page, leave without saving, or save and leave.

Refreshing or closing the browser tab can also trigger a native unsaved-changes warning.

Blueprint actions

Depending on your role, the blueprint actions menu can include:

  • Copy link

  • Share via email

  • Duplicate

  • Delete

The Home page blueprint menu also includes Present, Compliance Overview, and role-specific commit actions.

Open versus View

What happens when you open a blueprint depends on your role:

  • Blueprint Template Editors, Blueprint Editors, and Blueprint Committers open the Blueprint Editor. Blueprint Viewers open Presenter Mode.

Tips for working with blueprints

  • Save early when you are changing layout, metadata, or staged future-state content

  • Review the compliance score before sharing or committing

  • Use Presenter Mode when the goal is discussion rather than editing

  • Keep the blueprint name and description current so other teams can understand the intent quickly

Last updated