Localization updates made via the Identity Portal Admin UI are saved to the database but do not sync to the physical <language file>.json file, preventing the migration of language settings between environments (Dev, Test, Prod) by copying the file.
When attempting to migrate localization settings between environments, copying the <language file>.json file from /opt/brcm/iga/conf/idp/i18n (v15) does not include recent changes.
Updates made in the Admin UI are visible within the portal and stored in the product database, but the physical JSON file on the filesystem remains unchanged.
This prevents the "Export Localized Pages" workflow from functioning as documented.
Identity Portal 15.0
A product limitation exists where database-stored localization modifications do not trigger an update or export to the local <language file>.json configuration file on the filesystem.
This issue is targeted to be fixed in release 15.0.1.
Subscribe to this article to receive updates regarding the fix status. For instructions on how to subscribe, see Knowledge Article Subscriptions.