Elements and Relationships
Structure first, then content.
Elements and relationships live inside a blueprint, which is a ServiceNow record under the x_inpi_ydbp scope. What you can do depends on your role. See Roles and Permissions for details.
Once a blueprint exists, this is where you add, edit, review, and remove elements, and where you work with the relationships between them.
Add elements from the Data Hub
The Data Hub is the source list for the records you can place into a blueprint.
To add an element:
Open the Data Hub
Select a source table
Search or browse the available records
Drag a record to the matching table card or double-click it
The app only accepts records in the matching table card, which helps keep the blueprint aligned with the template.
Understand current-state and future-state items
Blueprints can contain two kinds of content.
Current-state elements
These are based on records that already exist in ServiceNow.
Future-state elements
These are planned items that do not exist yet.
Future-state items are useful when the blueprint is being used for planning, target architecture, migration preparation, or change design.
The app marks future-state content visually so it is easy to distinguish from current-state data.
Edit element fields
When you select an element on the canvas, the Data panel opens element-level editing.
The Fields tab can show text fields, choice fields, date and date-time fields, boolean values, numbers, and reference lookups.
Which fields appear depends on the template configuration for that table.
Review required information quickly
The element Fields tab highlights missing required information.
If there are issues, you can use the issue counter to filter the view down to missing fields only.
This is useful when a blueprint has many editable fields and you only want to see what still needs attention.
Work with relationships
When you select an element, the Relationships tab shows its incoming and outgoing relationships.
You can use it to review what is already connected, stage additional relationships, mark current relationships for removal, and inspect which relationship rules are currently satisfied or broken.
The tab also shows totals and issue counts so you can focus quickly on non-compliant connections.
Understand relationship rules
Relationship rules come from the template.
They describe which relationship type is allowed, which direction the rule applies in, the minimum number of matches required, and the maximum number allowed if there is one.
This is why two tables can be connected visually but still show a compliance issue: the problem may be the count, not the existence of the relationship itself.
Suggested relationships on the canvas
The canvas can show suggested table-to-table relationships based on ServiceNow metadata.
These suggestions help users understand how the selected tables can connect before they start editing element-level relationships.
Suggested relationships can come from direct matches, inherited matches, and related-list metadata.
Remove elements
Removing an element from a blueprint is not always isolated.
If the selected item has dependent items or connected content, the app can prompt you before removing it so you do not break the working blueprint by accident.
For future-state elements, removal is simpler because the item only exists in the blueprint draft.
Organize the canvas
You can keep the blueprint readable by dragging table cards into a clearer layout, resizing them, using grid and snap settings, and using the canvas zoom and pan controls.
The blueprint stores its layout, so you can reopen it later without rebuilding the visual arrangement.
What changes in Presenter Mode
In Presenter Mode, Blueprint Viewers can still inspect elements and relationships, but they cannot:
drag or resize table cards
change fields
stage relationship edits
save or commit
Last updated