Key Considerations & Risks: Upgrading Constellation Apps from v24.2 to v26 (Localization & OOTB Components)

User Experience
1

Hello everyone,

We are planning to upgrade our Pega environment from v24.2.1 to v26.

Current Setup:

  • We run a hybrid environment: 2 applications are on Constellation (UI Architecture), while the remaining applications are on Theme Cosmos.

  • Our application is localized in Japanese.

  • Customizations: We have overrides on pyFieldLabel rules and implemented workarounds for portal- and table-level localization in Constellation.

  • Components: We do not have any custom DX components (Custom Web Components); we rely entirely on OOTB Constellation components.

We’d love to get insights from those who have navigated similar upgrades:

  1. Localization & Rule Overrides:

    • Since we modified pyFieldLabel and added workarounds for portal/table localization in v24.2, what risks should we expect in v26?

    • Has v26 native Constellation localization matured to the point where these workarounds might break or become obsolete?

  2. OOTB Constellation Components:

    • Even though we haven’t built custom DX components, are there known breaking changes, deprecations, or behavior shifts in OOTB Constellation components between v24.2 and v26 that we should watch out for?

  3. General Constellation Upgrade Best Practices:

    • Are there specific pre- or post-upgrade steps, UI inspection routines, or Constellation SDK/service updates we must plan for?

Thanks in advance for sharing your experience!