We recently hosted a webinar on Extending Constellation - Unlock Advanced UI Customization with Constellation SDKs as part of the UX Expert Circle.

We received a lot of great questions from participants. Here are they along with answers from our SMEs:

 

Q: Do we still need the Constellation Static Server in Infinity 25?

A: No, the App Static Server has been removed in Infinity 25. For more details, see the https://docs.pega.com/bundle/platform/page/platform/release-notes/deprecated-features.html.

 

Q: How is localization metadata managed now that the static server is no longer used?

A: Localization metadata is now served directly from Infinity. There is no need for the App Static Service. Additionally, Infinity 25 introduces a single locale file for localization. More details are available https://docs.pega.com/bundle/platform/page/platform/release-notes/user-experience/constellation-25.html#cosmos-react-ref__section_zgg_pry_v2c_title.

 

Q: What are the limitations of applying custom CSS to Web Embeds in Infinity 2025? What can the React SDK do that custom CSS cannot?

A: For visual-only updates, using Web Embed with a specific theme is recommended. If your changes go beyond theme capabilities, use the custom CSS option. SDKs are not optimal for purely visual changes. We are working to improve custom CSS documentation and expand configuration options in theme rules. For advanced customization, see https://community.pega.com/conversations/user-experience/advanced-constellation-web-embed-customization.

 

Q: How do components select themes in version 25?

A: The theme applied at the portal level will be used by all components within that portal.

 

Q: Can I add a label without linking it to a property in Constellation?

A: To display standalone text, use instructions at the form or view level. Constellation’s design system provides configurations for labels, instructions, warnings, and validations. Avoid adding static text outside these configurations to maintain accessibility and responsiveness. More guidance is available in the https://community.pega.com/conversations/user-experience/how-to-display-static-text-in-a-pega-constellation-view%3F.

 

Q: What’s the difference between presentational components and DX components?

A: DX components are out-of-the-box SDK components with built-in runtime behavior, data binding, and configuration. Presentational components are custom design system components focused on layout and styling.

 

Q: Are there resources for using or extending SDK features with frameworks like Next.js?

A: Yes, see the https://docs.pega.com/bundle/constellation-sdk/page/constellation-sdks/sdks/integrating-react-sdk-next-js-applications.html for steps to use Next.js with Constellation.

 

Q: Why use the SDK instead of ConstellationJS (PCore/PConnect) directly from the frontend?

A: Orchestrating your frontend with PCore/PConnect is valid. SDKs provide a starting point and baseline for development tooling.

 

Q: Is the View responsible for wrapping all components in the presentation layer?

A: Yes, the view acts as the container for presentation components.

 

Q: How is accessibility handled with SDK implementations?

A: Accessibility is not provided out-of-the-box by the SDK. It is your responsibility to ensure custom components meet standards like ARIA and WCAG. Extending the UI increases flexibility but also shifts ownership and total cost of UI maintenance.

 

Q: Which React versions are supported in Pega 24.2.x and 25?

A: Pega 24.2.x uses React v17; Pega 25 uses React v18.

 

Q: Can I use React with CSS frameworks like Tailwind or Bootstrap? Can I use both MUI and Tailwind in the same app?

A: Yes, you can use React with other CSS frameworks and combine MUI and Tailwind in the same application. Take a look here for more details: https://support.pega.com/discussion/constellation-flexible-ui

 

Q: Is SDK version 24.2 compatible with Pega Infinity 25.1?

A: SDK 24.2 works with Infinity 25. SDK 25 is expected to be released by the end of this month (October 2025).

 

Q: Is there an optimal way to change the default UI library (MUI) in the React SDK?

A: Component overriding will be demonstrated later in the webinar.

 

Q: Can I use common SSO login for React applications and Pega React SDK?

A: Yes, SSO setup is supported.

 

Q: How does the SDK handle user authentication and operator onboarding?

A: See the https://docs.pega.com/bundle/constellation-sdk/page/constellation-sdks/sdks/authentication-authorization-apis.html.

 

Q: Can I load multiple apps/services in one SDK instance and pass starting field properties?

A: Yes, you can run separate workflows on different routes and pass initial field values using the startingFields option. See the https://docs.pega.com/bundle/pcore-pconnect/page/pcore-pconnect-public-apis/api/createcase-classname-targetcontext-options.html.

 

Q: When should I choose Portal vs. Embedded?

A: Use Embedded for surfacing workflows in existing web apps (e.g., self-service). Portals are for back-office use. For highly customized frontends, use SDKs.

 

Q: Can I adapt my company’s React component library to use the Constellation SDK?

A: Yes, you can create custom components for minor UX changes. Upcoming releases will make mapping easier.

 

Q: Is there value in using GenAI-assisted IDEs (e.g., Cursor AI) for DX component development?

A: GenAI IDEs can speed up development with smart suggestions, but developers must validate logic, accessibility, and platform-specific behavior.

 

Q: Are field validations performed client-side or server-side?

A: Both. Basic validations occur client-side; server-side validations ensure data integrity, security, and business rules.

 

Q: Does GCS support incidents related to SDK custom components?

A: Issues with PCore/PConnect JS APIs are supported.

 

Q: Will Pega publish a course covering these details?

A: The most comprehensive course is the https://academy.pega.com/mission/constellation-dx-components/v1. SDKs are covered in the new SSA course (https://academy.pega.com/topic/constellation-sdks/v2/in/93056). Documentation is also available https://docs.pega.com/bundle/constellation-sdk/page/constellation-sdks/sdks/constellation-sdks.html. The webinar recording will be posted on the UX Expert Circle.

 

Q: Can I use Mashup APIs alone or other PCore Public APIs when initializing the SDK environment?

A: Once your application is configured with the SDK and ConstellationJS is loaded, you can use all available PCore and PConnect APIs. Mashup APIs are accessible through the PCore object.

 

Q: How do I handle onboarding cases and user sessions in the SDK?

A: For unauthenticated scenarios, the Constellation DX API requires OAuth 2.0 authentication. Support for this is being added in future releases.

 

Q: Are existing widgets compatible with SDKs?

A: SDKs currently support a limited set of widgets. You can implement additional widgets as needed, and Pega will provide support.

 

Q: What should I do if I encounter errors with the PConnect API after SDK and Constellation JS configuration?

A: Raise an INC for the issue. The GCS or Engineering team will assist you.

 

Q: Does the Web SDK support responsiveness? Can I use media queries?

A: SDKs are not responsive out-of-the-box, but you can make your components responsive by writing your own CSS media queries or using responsive design techniques.

 

Q: Can I send metadata in allowed starting fields so the frontend knows the required data?

A: Yes, you can pass starting fields as part of the options for the createCase API. See the https://docs.pega.com/bundle/pcore-pconnect/page/pcore-pconnect-public-apis/api/createcase-classname-targetcontext-options.html.