Design Your Reports Before You Build — Introducing the Reports Tab in Blueprint

Reporting requirements are one of the most commonly missed items in a Blueprint. Not any more.

Blueprint now generates reports for each of your Case Types automatically, right inside Workflow Details. You can review, configure, and even preview report outcomes — all before a single rule is written in Pega Infinity.


:television: See It in Action

AI Assisted Reports


What’s on the Reports tab?

When you open a Case Type in Workflow Details, you’ll now see a Reports tab alongside the Case Lifecycle and Data Model. Blueprint generates an initial set of reports based on your Case Type context — and you can take it from there.


The Reports tab in Workflow Details — Blueprint generates reports automatically from your Case Type context


What you can do

  • Edit descriptions — clarify what each report should show and why it matters to the business
  • Change report types — switch between formats (summary, detail, trend, etc.) to match the intended use
  • Add new reports — capture anything Blueprint didn’t generate from context alone
  • Regenerate — as your Case design evolves, regenerate reports to stay aligned with the latest structure

Edit descriptions, change types, and add new reports without leaving the design flow


Preview before you build

Every report can be previewed directly in the live preview — so you and your stakeholders can validate what reporting will look like before the application is built.


Validate report outcomes in the live preview — no surprises in Authoring


Use the AI Assistant to create reports

You don’t have to configure reports manually. Ask the AI Assistant directly on the Reports tab:

“Create a summary report showing all open bookings by status”
“Add a trend report for booking volumes over the last 30 days”
“What reports would be most useful for the Operations Manager?”

The assistant creates reports in the context of your specific Blueprint — informed by your actual Case Types, data model, and personas.


Why this matters

“Reporting requirements discovered late in Authoring are one of the most common causes of scope creep and rework.”

By capturing reporting intent during Blueprinting — where changes are cheap — teams arrive at Authoring with reporting already defined. Reports are included in the .blueprint export, so the Solution Builder receives a complete design, not just workflows and data.


Have you spotted reports on your Blueprint yet? Drop your thoughts below :backhand_index_pointing_down: