Overview
Constellation SDKs enable organizations to seamlessly integrate Pega Constellation workflows into existing web applications while maintaining control over the user experience, branding, and design system.
However, SDKs introduce additional implementation complexity, front-end development effort, and long-term maintenance responsibilities. Therefore, organizations should carefully evaluate whether SDKs are the most appropriate option compared to Native Constellation or Web Embed.
This document provides guidance and checkpoints to help determine when SDK adoption is appropriate.
Understanding the Available Options
Before deciding on SDK adoption, consider the available UI implementation approaches:
| Option | Best For | Effort | Customization |
|---|---|---|---|
| Native Constellation | Internal applications and workflows | Low | Low |
| Web Embed | Simple external journeys embedded into an existing website | Low-Medium | Limited |
| Constellation SDKs | Integrating Constellation workflows into an existing branded application | Medium-High | High |
| Headless / DX APIs | Fully custom applications | High | Very High |
As a general principle:
Organizations should stay as close to Native Constellation as possible and move toward SDKs only when there is a clear business, technical, or UX requirement that cannot be satisfied through standard Constellation capabilities.
Decision Tree
Step 1: Can Native Constellation Meet Your Requirements?
Consider Native Constellation if:
- Your organization is comfortable adopting the Constellation design system.
- Branding requirements can be satisfied through theming.
- Standard Constellation components provide the required user experience.
- Rapid implementation and lower maintenance costs are priorities.
If the answer is Yes, Native Constellation is typically the recommended approach.
If No, continue to Step 2.
Step 2: Is Web Embed Sufficient?
Consider Web Embed if:
- Only a limited number of case journeys need to be exposed externally.
- The embedded experience can retain the native Constellation appearance.
- Deep integration with the host application is not required.
- Development effort should be minimized.
If the answer is Yes, Web Embed may be sufficient.
If No, continue to Step 3.
Step 3: Evaluate SDK Suitability
SDKs are typically a good fit when one or more of the following conditions apply:
Design System Requirements
Your organization must follow an existing design system, and Constellation theming or DX Components cannot fully meet branding or UX requirements.
Existing Application Integration
You need to embed Pega workflows seamlessly into an existing customer-facing or partner-facing application while preserving the current user experience.
Front-End Development Capability
Your team has experienced front-end developers with expertise in React, Angular, Web Components, or similar modern web technologies.
Willingness to Own a Custom UI
Your organization is prepared to invest in the additional implementation, maintenance, and upgrade responsibilities associated with a custom UI layer.
Clear Business Value
The benefits of enhanced UX, branding consistency, or integration justify the additional cost and complexity of adopting SDKs.
If these conditions do not apply, Native Constellation or Web Embed may be a more suitable option due to lower implementation effort and maintenance overhead.
When SDKs May Not Be the Right Choice
SDKs may not be appropriate if:
- Standard Constellation capabilities satisfy the business requirements.
- The organization primarily needs internal user applications.
- There is no requirement for an alternative design system.
- Front-end development expertise is limited.
- Faster delivery and lower total cost of ownership are primary objectives.
In these situations, Native Constellation or Web Embed generally provide better outcomes.
SDK Adoption Checklist
Use the following checklist during discovery discussions:
| Question | Yes | No |
|---|---|---|
| Do you need to preserve an existing design system? | ☐ | ☐ |
| Do you require greater UX control than Constellation provides? | ☐ | ☐ |
| Do you have experienced React, Angular, or Web Component developers? | ☐ | ☐ |
| Do you already have a customer-facing web application? | ☐ | ☐ |
| Is seamless integration into the existing application required? | ☐ | ☐ |
| Are you willing to own and maintain custom UI assets? | ☐ | ☐ |
| Does the business value justify the additional investment? | ☐ | ☐ |
Recommendation
- 0-2 Yes answers → Consider Native Constellation or Web Embed.
- 3-5 Yes answers → SDKs may be appropriate; conduct a deeper assessment.
- 6-7 Yes answers → SDKs are likely a strong fit for your use case.
Conclusion
Constellation SDKs are best suited for organizations that require seamless integration of Pega workflows into existing applications, need substantial control over their user experience and branding, possess strong front-end engineering capabilities, and are willing to accept the additional implementation and maintenance responsibilities associated with an alternative design system. Native Constellation should remain the preferred option whenever it can satisfy business and user experience requirements.