Question
Strategy to localize ongoing Constellation applications
Hi,
I recently worked on localizing an ongoing Pega application using the Localization landing page in App Studio. Previously, I had experience localizing traditional UI-Kit applications through the Localization wizard, so exploring this new approach was quite interesting. I’m sharing this post to discuss my initial experience and hopefully get answers to a few questions.
My main question is about the strategy for localizing applications that evolve over time. For example, if we localize the application to Spanish (MX) for an upcoming release, and then the next release introduces new screens or case steps, do we need to delete the existing localization and create a new one for Spanish (MX)? If that’s the case, it seems like a lot of rework since we’d have to maintain localization across multiple releases.
Additionally, what happens if, after running a case, we notice some labels weren’t properly localized? How should those be corrected? In Pega 25.1.1, I see the new Inspector toggle (ui_inspector), which looks promising for identifying these issues. But what about those of us still working in Pega 24.2.3?
Thanks for considering my question.
Best regards,
-Jose Navas