What are Pcore and PConnect API’s?I can see these are the commands that we often give to debug Constellation app,but what do they do?We already work with DX API’s in constellation so why are these required?
Hello @TanyaS58
1)What are PCore and PConnect APIs?
PCore is the global JavaScript API for the Constellation orchestration engine. It exposes capabilities that are not tied to a specific UI component, such as environment info, data page utilities, messaging, and the REST service broker.
PConnect is the component-scoped API (context-aware) used by every rendered Constellation field/template component. It provides APIs to read/write the component’s state, invoke actions, validate, navigate, and interact with the case context.
In short:
PCore = global runtime engine access,
PConnect = per-component access
2)If DX API exists, why are PCore/PConnect required?
DX API is server-side REST, they return case data + view metadata over HTTP. It’s the contract between UI and Pega server.
PCore/PConnect is the client-side orchestration layer.
Constellation is designed so you typically don’t call DX API directly from components. Instead, you call PCore/PConnect, and the engineat the background manages Redux/state, applies field instructions/page instructions, invokes the correct DX endpoints, merges responses back into UI state,
handles errors and validation consistently.
PCore/PConnect are needed even when DX API is available—they provide the “brains” that make DX API usable in a consistent, guardrail-friendly Constellation experience.
In short:
DX API = “what to fetch/update”
PCore/PConnect = “how to run the app” (state, actions, events, orchestration)
One scenario where you would bypass PCore/PConnect - when you are building a fully custom external UI (headless) and choose to consume DX API directly—then you must implement your own state management, validation handling, navigation, and error flows.
Hey @TanyaS58
PCore and PConnect APIs are client‑side JavaScript APIs provided by Pega to support Constellation‑based UI orchestration.
At a High level:
-
PCore is the client‑side state layer that holds case data, data pages, assignments, and UI metadata.
-
PConnect is the binding layer that allows DX (React) components to access PCore data, react to state changes, and invoke Pega actions—without calling backend services directly.
Lets understand it with an example – Appointment Scheduling (Calendar View)
Assume an appointment scheduling use case displayed as a calendar using a custom DX component.
Using DX APIs:
-
Every calendar load or refresh triggers a backend REST call
-
Data is fetched repeatedly from the server
-
Leads to multiple and often unnecessary server hits for UI refreshes
Using PCore + PConnect:
-
Appointment data is loaded once into PCore (via case actions or data pages)
-
The calendar component reads data from PCore using PConnect
-
UI updates automatically when PCore state changes, without repeated backend calls
Here are the primary differences between DX API & PCore / PConnect API
| Aspect | DX APIs | PCore / PConnect APIs |
|---|---|---|
| Primary role | Direct backend data access | Client-side state & UI orchestration |
| Data fetching | On each load/refresh | Loaded once, reused from PCore |
| Backend calls | Frequent | Minimized |
| UI behavior | Imperative | Reactive |
| Constellation fit | Optional | Native & recommended |
In short: DX APIs fetch data, whereas PCore manages the data lifecycle on the client, and Connect seamlessly binds the UI to that state, making them the preferred approach for performant Constellation applications.
If you want to have more overview, there is a detailed documentation provided by Pegasystems that explains in detail how the APIs work in unison with the Pega infinity server - Pegasystems Documentation .
Let me know if this answers your question
Thanks,
Roshan Raj A K
- PCore APIs = Internal backend APIs used by Pega Platform to run rules, manage clipboard data, and process logic.
- PConnect APIs = APIs used for communication between the Pega UI (especially Constellation) and the backend.