Text in Wedge Config vs UI Text vs Tecton Localization
Text in Wedge Config vs UI Text vs Tecton Localization
4. 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.
1. 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.
2. The dissadvantage of Wedge Address Configs for UI Text is the lack of localization features.
3. 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.
4. 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.
1. 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.
2. The dissadvantage of Wedge Address Configs for UI Text is the lack of localization features.
3. 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.
4. 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.
1. 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.
2. The dissadvantage of Wedge Address Configs for UI Text is the lack of localization features.
3. 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.
4. 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.
1. 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.
2. The dissadvantage of Wedge Address Configs for UI Text is the lack of localization features.
3. 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.
4. 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.
1. 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.
2. The dissadvantage of Wedge Address Configs for UI Text is the lack of localization features.
3. 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.
4. 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.
Text in Wedge Config vs UI Text vs Tecton Localization
1. 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.
2. The dissadvantage of Wedge Address Configs for UI Text is the lack of localization features.
3. 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.
4. 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.