Moving Derek's comment to an answer:
Hey Chris,

Yes — non-visible Application-Level Outlets are a fully supported option in the q2 tecton CLI. The walkthrough is at https://docs.q2developer.com/guides/frontend_development/application_level_outlets.html.

That said, your q2 check failure is likely unrelated to your outlet work. Configuring an Application-Level Outlet via q2 tecton does not touch INSTALLED_ENTRYPOINTS.

To diagnose, could you share:

The contents of INSTALLED_EXTENSIO...

Hello,

Sorry for the delay on this, Q2 is the IDP by definition alone. In the extension code and your service is defining the relationship and how to login to your external service through the Q2 login. So the answer to your questions is dependent on how you write your code and generate these values.

-Trey

Hello,

You can follow the guide here: https://docs.q2developer.com/guides/mobile_dev/index.html Plugging in http://demo.q2.com/experimental/ for the Base URL. To get just a mobile app working. If you need a more full featured app then you will have to make a support case for that.

-Trey

Hi Christopher,

The old extension was doing something we don't really recommend now which is modifying q2 styling from an extension. This likely won't work with the future SDK accounts extension with composable dashboard. You can make this work with the currrent dashboard though and we would likely approve this with a uux_payload: https://docs.q2developer.com/docs/guides/frontend_development/uux_payload.html

If your FI plans on moving to Composable Dashboard in the near future you may l...

Please sign up with your companies email address.

Bradley's answer is excellent, a bit more color. On top of being able to turn on or off extensions at the group level. You can also use wedge address configurations to turn on and off features within a feature if you write it in the code during development time and then control that per environment. You can control this in the developer portal.

Hello,

Currently there is no Caliper API endpoint for this. I don't really have a good answer for any of the other questions other than it seems specific to your organization so it would be best handled in a ticket either to Q2 Support or Developer Support.

-Trey

I believe it will not accept name. If you would like this to happen externally you could use Caliper API's Get Vendors call to grab the id from the list of vendor names. Then use that to make your deep link.

Finding via Consul or Central might be version dependent. In the SDK there is a db object to get this information: https://docs.q2developer.com/docs/guides/notifications/secure_message.html using the message recipient group db object: https://docs.q2developer.com/docs/api_references/q2_sdk/db/db_objects/message_recipient_group.html#module-q2_sdk.hq.db.message_recipient_group However, this is not currently not available via Caliper API. You could make a custom endpoint to do this functionality...

Hello Edward,

Your thought process is correct. The exact paths to make this work might not be what you are expecting though. At least initially I recommend making the folder location a configuration so that you can control where it is landing more properly, it would also allow you to have say a different location for Staging testing and Production live reports. It would also allow you to better test your periodic job locally.

-Trey

Hello Christopher, I am surprised a bit, because it definitely should have something that hits the backend. The code example here has code hitting the backend: https://code.q2developer.com/Q2Antilles/sdk-examples/sdk-tecton-examples/-/tree/master/Vue?ref_type=heads

Once you get through the initial setup, I recommend using a different short name for each person working on the extension. In fact, when you go to install a second of the same extension it will prompt you to give it a different short name.

While we have in the past, and will likely in the future create additional branches that can deploy to an additional environment. Very rarely does this extra environment actually give the intended additional benefit. The few cases where it has added additional benefit is where it is for a migration from one core to another or something like that where it is a short lived additional environment and branch. Instead I recommend to research branching strategies and how to make your given environm...

Hello Jenny,

We recently made a change to try and prevent you from adding an extension under a nav node that is not intended to be one used as a drop down. Maybe that is what you are experiencing? I would also double check your q2 inspect details to see if that looks correct.

What are you trying to accomplish that you can't?

-Trey

Hello,

It slightly depends if the button you are pushing is Q2 Console or Q2 Central. For Q2 Console, you could try and reproduce in the sandbox with: https://docs.q2developer.com/docs/tutorials/backoffice/console/index.html for Q2 Central you can try: https://docs.q2developer.com/docs/tutorials/backoffice/central/index.html if you can reproduce the experience in the sandbox then the shape should be the same between the sandbox and Staging/Production. If you cannot reproduce in the sandbox...

That is our internal testing site, it is on the public internet so that we can confirm it is working as intended.

Hello,

The Vendor configs are a per FI installation config(so a config for staging and production if the extension is installed more than once into the same environment though you could have 2 or more configs for the same environment), you can still have the ability to update them via self service(depending on the FI, but almost always the answer is yes). There isn't really a global service config for SDK services currently. Though, that would be an interesting idea.

Hope this helps,
T...

Hello,

It depends on how your extension is set up, but my guess is that the get method doesn't exist in your extension.py file for the AccountDashboard extension. All standard SDK traffic uses post methods when coming from Online Banking for online extensions, so it's possible that you can't navigate directly to it. However, once you install it into your sandbox environment, everything should work correctly.

Best,
Trey

Hello,

Generally you would find your Sandbox Online banking environment on your dashboard on https://q2developer.com/dashboard if you have access to a sandbox. Otherwise you can request access to a sandbox on that same page.

-Trey

Thank you for your interest in Ready Remit by Brightwell, eMailacheck, Derivative Path International Payment, and Merchant Service - Deluxe.

When you sign up using your Financial Institution email address, you will either:

• Immediately gain access to view and request the application(s), or
• Be prompted to request access to view and request the application(s), depending on your institution’s current configuration.

If you have any questions or need assistance during the process, fee...

According to the documentation here: https://docs.q2developer.com/api_references/q2_sdk/ardent/index.html#q2_sdk.ardent.file_upload.File.upload_from_file
The data parameter either takes a BytesIO object or a string, but it specifies that the string is a path to a file not the file itself. If the data is a string datatype then you need to convert it to a BytesIO object.

-Trey

Hello,

There isn't a way for the Caliper API to subscribe to events like that. You would have to build an SDK Audit Handler Extension to do this. https://docs.q2developer.com/docs/tutorials/audit_action/index.html

-Trey

Using Global in quotations here for ease of understanding. Global will be in context of the running service in Staging or Production.

Anything stored in the repository will be global and anything stored in the database will be per environment. Vault can be either per environment or global. For custom messaging, I recommend either Wedge_address_configs or UI_Text(https://docs.q2developer.com/docs/guides/online_integration/ui_text.html)

-Trey

We are working on a better process, but right now presuming you are a multitenant service, you simply create a ticket requesting a deployment and then that update will go to your multitenant service which will automatically update for all your FIs. This follows the ideal of everything being an evergreen service.

Hello,

I typically don't recommend generating reports on button push. We have a proper concept of jobs via https://docs.q2developer.com/docs/tutorials/periodic/index.html

There is a possibility of using the on_finish but you don't have visibility into it's progress very easily without building something very custom:
https://docs.q2developer.com/docs/api_references/q2_sdk/http_handlers/base.html#q2_sdk.core.http_handlers.base_handler.Q2BaseRequestHandler.on_finish

This will also stru...

Hello Jenny,

For rich client side development like this, I generally recommend using local development as the compute required for building and running this is higher than server side rendering. Doing this on a shared resource will not run near as smoothly compared to running it on your local computer. See docs on setting up local development here: https://docs.q2developer.com/docs/setup/local/index.html

To answer your question though, the command to use node 14 is in package.json file ...

Hello Fabio,

Those ids seem to vary from db to db so I would recommend Wedge_address_config or vendor_config(for SSOs). See the documentation here:
WEDGE_ADDRESS_CONFIGS: https://docs.q2developer.com/docs/tutorials/online_banking/configuration.html
VENDOR_CONFIGS: https://docs.q2developer.com/docs/tutorials/sso/index.html?highlight=vendor_config#example or in code form https://code.q2developer.com/Q2Antilles/sdk-examples/sso-example/-/blob/main/ExampleSSO/extension.py?ref_type=heads
For...

Hello Emanuel,

Currently there is no external visibility into what is stored in memcache in Staging or Production. It is possible we will add this functionality in the future, but it is currently not on our roadmap. Q2 can see what keys are being used in the datacenter, but we cannot view the contents of the values or edit the values. We can delete based on the keys or delete everything under a certain extension. This works exactly like it works in the local environment via the /cache endp...

Hello Justin,

The endpoint you are looking for is here: https://docs.q2api.com/docs/q2-caliper-api/153e2d7ebf397-get-usage. Also, this is data that we populate for you in a widget on q2developer.com/dashboard.

-Trey

Hello Steve,

This is a great idea and we will probably accomplish it at some point, but this is currently not a capability of console and not currently on the roadmap as far as I am aware.