Is default localization broken in B2C custom policies?

Question

Hi

My team and I have found some weird behavior in how localization works for custom policies.
For example, if we use page layout version 1.2.0 of unifiedssp, the page gets correctly translated to the requested ui_locale (in this example da-dk).
If we choose to use the newest version of the unifiedssp page layout which is 2.1.0, the page does not get translated, it only shows in English.

If we explicitly add translation string using custom policy localization we can make it work. But does this mean we have to explicitly add the default user-flow translations for every language we want to support in our custom policies, or is there something we are missing?

Answer 1

@Anders Madsen Welcome to QnA platform and thanks for your query.

I tested setting unifiedssp page contract 2.1.0 in my tenant and found that certain built-in strings such as "Email Address" string on sign-in page is not getting translated. This works with page contract 1.2.0 and 2.0.0 as well.

I will report this issue to the B2C product group. You may also open a support ticket and get a bug raised regarding this issue, so that you can check for the updates as well. Meanwhile this is not fixed, you can use page contract version 2.0.0 for unifiedssp.

-----------------------------------------------------------------------------------------------------------

Please "Accept the answer" if the information helped you. This will help us and others in the community as well.