The Data & Integrations step in Pega Blueprint™ has been completely redesigned — and it’s a game changer for high-fidelity design.
@trems1 has put together a quick 4-minute walkthrough showing the new Integration Designer in action. Whether you’re working with REST APIs, legacy databases, or just trying to map out what connects to what before the build starts — this one’s worth your time.
Watch the Walkthrough
What’s new?
The redesigned Data & Integrations page is now a full visual designer — not just a data entry form. Here’s what it gives you:
Three-panel layout
Everything in one view:
- Left — User Identity & Events: Configure authentication (OpenID Connect, MFA) and inbound triggers including Pega DX API, Desktop, MCP Service, Kafka, A2A, and more
- Centre — Application Data: Your local data objects on the left, external on the right. Drag any local object across to map it to a system of record
- Right — Integrations: Add and manage your external systems — with full resource and action visibility
AI-powered integration import
The part that saves the most time:
- Upload an OpenAPI / YAML spec → Blueprint analyses it and auto-generates the integration system complete with all resources, field counts, and descriptions
- Upload a SQL / DDL file → same thing for database schemas
- AI Assistant → ask it to map a data object to a resource in plain English and it updates the Blueprint immediately
Fidelity indicators on every data object
Each data object now shows a colour-coded completeness indicator — the same system used across Workflow Details:
| Colour | Meaning |
|---|---|
 Grey |
Name only — not yet configured |
 Yellow |
Partially configured |
 Green |
Fully configured and import-ready |
The goal: get everything to green before you import.
MCP Service support (new in Infinity '26)
Enable and describe your MCP Service directly in the Integration Designer — exposing your Case Types as AI-ready services from day one of the build.
Why does this matter?
“You can’t easily retrofit plumbing into a finished house.”
Defining integrations at design time — before a single rule is written — means the Solution Builder receives a complete Blueprint on import. Every integration you specify here generates the data layer automatically. Every one you leave blank becomes manual work in Authoring.
The higher the fidelity in this step, the stronger your starting point.
Try it
Have questions or want to share how you’re using the Integration Designer on your projects? Drop them below 