Hi Brian!
The only way to group now would be through arrangment of the data before passing it to the table element. I see you're an internal user so we'll reach out to get more information on what you're looking to accomplish and we can open up an enhancement case for the element that we can review.
Thanks!
Hi Bina!
Are you having an issue getting translations to show or are you just trying to resolve the 404 error you are seeing? You could be running into a known issue laid out in the FAQ linked below. This should be resolved for less noise in the browser console in more recent versions of the UUX platform (4.6.1.11+).
[Why am I seeing 404 errors in the developer console from q2-tecton-sdk?](%20https://tecton.q2developer.com/faq/why-am-i-seeing-404-errors-in-the-developer-console-from-q2...
Hi Courtney!
We just added a link to access the Tecton Figma Design Library file onto our docs site in the latest release.
https://tecton.q2developer.com/design-system/
Here is that file as well: 📎 Tecton Design Library.fig.zip
Yes, with widget content it is possible to display conditionally. Your extension will still be rendered, so it will just be up to you to render or not render display content and control the vertical height taken. The platform should minimize any screen real estate taken up by widgets without content. If you are doing Dynamic Content blocks for the Composable Dashboard, those can only display conditionally in the frameless target area as to not impact the layout of the rest of the content bloc...
If you've successfully gone through enabling External MFA in the sandbox and setting up your user group I would suggest opening a ticket through the Developer Portal and we can take a look at your specific setup in your sandbox and help debug.
https://docs.q2developer.com/tutorials/external_mfa/index.html#setting-up-sandbox
Application outlets would be the recommended way to provide an alert and redirection post login. This is possible with UUX Payload as well. You have the ability to conditionally open a modal using Tecton's showModal capability and then redirect to the loan payment form using the navigateTo capability.
https://docs.q2developer.com/guides/frontend_development/application_level_outlets.html https://docs.q2developer.com/guides/frontend_development/uux_payload.html
https://tecton.q2develop...
Hi Kyle!
The moduleId is a combination of the extension's feature name and module name.
FeatureName.ModuleName
It is only an optional parameter for the getTectonCacheObject capability. setTectonCacheObject will set the cache under the FeatureName and ModuleName it is called from and by default getTectonCacheObject will retrive cache for the module in use. Passing a moduleId in will allow you to grab the cache from a sibling extension.
Hi Subha,
For the Composable Dashboard, the Content Blocks don't get any indication that content is not rendered into the extension frame therefore they cannot self-collapse.
https://tecton.q2developer.com/guides/composable-dashboard/
Currently, the composable dashboard design guidlines request all content blocks have an empty or completed state.
If there is no relevant, timely information; the content block should incorporate an appropriate "empty state".
I believe the curr...
The modal is meant to be a blocking UI element that requires user interaction to bypass. It isn't currently designed for auto-closure. For that, we have showAlert which can show a non-blocking "toast" style notification to the end user. showAlert can be configured for closure or to auto-close after a set duration.
Here is an example of how you would call that today:
tecton.actions.showAlert({
toastHeader: 'Verify Action',
message: 'You have 10 seconds to cancel. Would you ...Hi Josh,
If you are redirecting to another URL within the iframe and want to still communicate with the platform via Tecton, you are correct that you will need to add the additional domains you are calling from and connect from there. This can be configured in the FeatureName.py file located in your extension's configuration directory.
Hi Swarup!
Currently, the extensions are responsible for providing any necessary translations for alternate language files. Q2 doesn't provide tooling on this at the moment. You are free to use any translation software or translation services that suits your needs.
Hi Todd!
Is this a server-side rendered extension or a client-side rendered extension?
With a server side rendered extension I would expect to see entrypoint urls like these for Main and a secondary entrypoint based off the python route setup:
"url": "./sdk/authenticated/{featureName}",
"url": "./sdk/authenticated/{featureName}/hyc",
With a client side rendered extension using hash routing I would expect something like these:
"url": "{BASE_URL}/index.html",
"url":...Hi Draden!
This issue was reported through our support portal and corrected. You should no longer need to comment those lines out.
Hi Draden!
Thanks for your reply on the other post. I did a little digging with the Q2 Dev mobile app and found an issue with the pickContact api that needed to be resolved. Got that in yesterday and it should be released on Tuesday (5/16) in the Tecton 1.26 release.
Hi Draden!
Which mobile app are you using for testing? Apple and Google are very strict in making sure only the permissions used are enabled, going as far as to remove apps that are not set with with the correct permissions. I believe contact access is defaulted to off on mobile app builds and may need to be configured on.
Hi Michael!
Not sure if it would work for your particular use-case, but Tecton exposes the setTectonCacheObject and getTectonCacheObject capabilities in order to store and retrieve data from the platform cache.
https://cdn4.onlineaccess1.com/cdn/base/tecton/v1.25/Documentation/capabilities/setTectonCacheObject
https://cdn4.onlineaccess1.com/cdn/base/tecton/v1.25/Documentation/capabilities/getTectonCacheObject
Hi Jason!
This error reads like your module parameters are either not configured correctly or the updated configuration is not being picked up for use when running locally.
So once you've added the module paramaters your configuration should look something like this:
"NewFeature": {
"overpanel": False,
"primary": False,
"navigable": True,
"formPostAuth": True,
"url": "./sdk/authenticated/{featureName}",
"meta": {
"type": {
"shape": "Content",
"context": "...Hi John,
It looks like we've had a change in the platform that now requires a new property to be passed into the quick-transfer overpanel and requires a change to our documentation.
This should allow you to open the quick transfer overpanel correctly without the to or from account prefilled.tecton.actions.navigateTo('application', [], { overpanel: 'quick-transfer', 'overpanelId': '{}' });
You also now have the option to pre-select a to or from account with the account id.
`tect...
Hi Brock!
If I am understanding you correctly, you want to read the Tecton params on init of your SSR extension and re-route to a different routing key inside your extension accordingly.
To navigate from a button click to another SSR extension passing a configured query param, you would do something like below in your template:
<script>
document.querySelector('#my-button').addEventListener('click', function() {
tecton.actions.navigateTo({
featureName: ...While Tecton does provide a grid system, nothing prevents you from consuming and using Bootstrap Grid in your extension. We would also welcome feedback on our grid system if you have certain functionality you are looking for. Thanks!