- So the tecton localization files can be updated through a deployment. These files get put into our CDN but we also have a service called Q2Config that allows you to update the text so that you don't have to do deployments every time. Now I could be wrong on this but, as far as I understand how Q2Config (also known as Experience Builder) works is that it layers 'changesets' on top of what is served in the CDN.
- The dissadvantage of Wedge Address Configs for UI Text is the lack of localization features.
- This is mainly because the older UI Text elements are stored in the DB where Tecton has a harder time accessing said elements so the backend would have to pass them through. With the Tecton localization strings being served through the CDN Tecton has more direct access and can add localization features itself. So DB UI Text is more suited for server side extensions and Tecton Localization is more suited for client side extensions. Another benefit of Tecton Localization is that Q2Config/Experience Builder is to some degree available for partners/FIs to edit text on their own.
- UI Text in the DB would need a q2developer.com ticket and updated by us on the Q2 side. Q2Config/Experience Builder can be self service.
Answered
Text in Wedge Config vs UI Text vs Tecton Localization
Hi,
I am looking for a place where UI text for extensions to be persisted for online extensions (enabling text to be updated without redeploying the extension). We currently do not need anything more than US English language.
I am looking at WEDGE_ADDRESS_CONFIGS (https://docs.q2developer.com/docs/tutorials/online_banking/configuration.html) compared to using Tecton Localization and also UI Text (https://docs.q2developer.com/guides/online_integration/text_localization.html).
Questions:
- To update Tecton Localization language's json files, I think it would require redeployment. True? The text in the link above states, "Using Text Translation and Localization ensures that not only can your extension support multiple languages, but that text customization can be done without needing to modify code or redeploy the extension." Wouldn't we need to redeploy to update the json files?
- Are there any disadvantages to using WEDGE_ADDRESS_CONFIGS to store text? I will be using it to store other extension configurations needed.
- Why does the doc state UI Text is primarily for non-Tecton extensions?
- How do we update UI Text in staging and production environments? Is there self-service, or is it a Q2 ticket - dev ticket or customer portal ticket?
Thanks!
134 Views
1
Answer
one year ago
12 months ago