We have an application that uses a hybrid approach that mentioned here, with a Constellation case type within a Traditional UI application. We would like to enable localization for the Constellation case type.
However, I do not see the Localization option under Settings in App Studio. Could you please confirm whether localization is supported for Constellation case types when they are used within a Traditional UI application?
Is localization available only for fully Constellation-based applications, or is it also supported for hybrid applications that contain both Traditional UI and Constellation case types?
I believe this is a OOTB limitation when using constellation in traditional UI. See below documentation.
Localization.
Labels and messages from Constellation Case Types created in the traditional application are not localized.
In general, this hybrid or blended approach seems to be interesting and compelling, however both approaches have their own challenges/limitations during setup and later during usage as well.
Before you delve into any of the approach, be sure to read through the limitations highlighted by Pega and see to it that those limitation are/are not affecting your application.
If you see that you hit the wall because of any of these mentioned limitations, then go with blueprint approach and run it through the blueprint estimator to see for yourself how much time it takes for you re-imagine the same application with modern features.
I initially thought that using Rule-UI-Localization would allow us to move forward, but it appears that this is not feasible.
Additionally, with this approach, the static content does not seem to be stored in the app-static service, which means localization cannot be implemented.