Hello Bradley,

There is not an example I can share externally with you. That being said, the documentation gives you freedom to do either sending all or parts at a time. I asked the Tecton folks and they said they are also using it in the hidden navigation here that you can inspect. https://tecton.q2developer.com/account-details/#pagination note, because this is hidden, there may be things that are not fully supported in the current version of Tecton. I would expect everything to work tho...

That is controlled by the https://docs.q2developer.com/docs/guides/configuration.html#debug for some reason yours seems set to False. You could try manually changing Q2SDK_DEBUG on your local environment by running export Q2SDK_DEBUG=True

Hello,

A Custom login disclaimer can be created via Central. You can reach out to your CEM if you need help setting it up.

-Trey

Hello,

As far as I know this is not possible. Maybe this will be added in the future.

Hello,

This partly determines on personal preference, and what kind of data it is. For things that need to be configured for each environment. Even if that is generally the same for each environment I recommend using a Wedge Address Configuration(https://docs.q2developer.com/docs/tutorials/online_banking/configuration.html). This will be stored in the database and easy to configure for each environment. If you have a setting that needs to only be on for a particular environment. Say always...

This is a bit complicated for Multitenant use cases or FI cases where they want to be able to easily do a core conversion.

I recommend you look through https://docs.q2developer.com/docs/guides/core_integration/index.html#multitenant-multi-core-extensions to understand how multiple cores is supposed to work. If your extension requires a core call then what that core is needs to be set at install time. Even in the dev environment you are setting a "Core" at install even though the dev envir...

Hello,

Those steps should be complete. I have setup myself and many other people using the exact same steps. What information are you putting into the various fields? Some screenshots with step by steps of what you are doing would be helpful.

-Trey

For both 1, 2 and 3: look at https://docs.q2developer.com/docs/guides/core_integration/index.html#multitenant-multi-core-extensions

For 4 and 5: instead of standing up online banking in your local environment you can connect to a sandbox environment that is running in AWS. To do so follow the guides here: https://docs.q2developer.com/docs/setup/index.html Once you are setup you can log in to your sandbox environment that is listed in your dashboard https://developer.q2.com/dashboard. This ...

Hello,

Calling Caliper API is just a simple set of https requests. See how to call Caliper API here: https://docs.q2api.com/docs/q2-caliper-api/0gozwdc5ipopq-how-to-call-v2. I am not at all familiar with Spring Boot, because we use OAuth which is a very common authentication method there should be plenty of guides on it. A quick google search found this: https://spring.io/guides/tutorials/spring-boot-oauth2 which might be helpful.

-Trey

Hello Jarrod,

You likely need to run q2 setup_db and might need to upgrade your SDK version and run q2 setup_db.

-Trey

Hello,

Create a General ticket on developer.q2.com requesting admin access. We will do some validation and then provide the necessary parties with company admin capability.

-Trey

Hello,

I recommend using https://docs.q2developer.com/docs/api_references/q2_sdk/db/db_objects/user_data.html#q2_sdk.hq.db.user_data.UserData

As a general rule, using the cache to store anything that is user specific between sessions is not recommended.

-Trey

Hello Tanner,

We can configure your pipeline to deploy to that other place on a seperate branch. Make a ticket on developer.q2.com with the branch name and mention my name and I will help you out there. Probably will need to schedule a call.

-Trey

Hello,

Currently there is no way to refresh groups in the session. They would have to log out and log back in.

-Trey

Hello,

Currently how self service vault upload works is it just puts your secrets in a known location in vault for SDK support to then place wherever it needs to be used by your application. Currently for security reasons we do not expose the secrets you have uploaded in the past.

-Trey

Hello, there are three main ways we differentiate in multitenant situations: self.hq_credentials.aba(this is a unique value for each FI, the FI's staging and Prod environments will have this value set), self.hq_credentials.customer_key(This will be a unique value for each environment i.e. the FI staging and Production environments will be different), self.online_user.user_guid(this is a hash of the user_id and customer key so it will be a unique user id for every user assiociated with Q...

Hello Tanner,

I would recommend caching that core call if you are concerned of them hitting it multiple times. Caching it will give you better control of when it needs to be called. I do recommend using a self.session_cache.

To answer your question if the frontend via a href tag or a javascript call submits to the backend then the router will run that method for that page again. It will only display what was in memory if you cache something explicitely and return it.

Note, sandbox...

Hello,

In terms of the list of questions, I would recommend that be stored in the wedge address configs. The form then could be built off that list of questions in the wedge address configs any you could change those when you desire. It would also be easy to test and show off in the sandbox, Staging, and Production through the self service wedge address config changes.

-Trey

Hello,

This generally happens if requirements.txt does not match what you have installed locally in pip install. This can be checked by deleting and rebuilding your python virtual environment off of requirements.txt.

-Trey

Hello,

That generally happens when you have not run q2 setup_db. I recommend updating to the latest version of the sdk and then running q2 setup_db.

-Trey

Hello,

During the used caliper_admin to "Start a New Project" -> section, you are better off cloning from your existing repo you can see this on developer.q2.com/dashboard or in your group on code.q2developer.com. If not you can do q2 setup to generate those files.

You may also want to run:
Install Frontend Dependencies(to install npm and yarn if you don't have those)

-Trey

Hello Ethan,

I don't think I have seen an external developer do this before, and as far as I know there is nothing built into the SDK to build documentation off of your SDK extensions. However, the documentation for the SDK is built using Sphinx. So you are welcome to use the code in the sdk repository and learn how Q2 builds those docs to build your own. https://code.q2developer.com/Q2Antilles/q2-sdk Note if you want this site always up and running somewhere you would have to host it. Mig...

Hello Draden,

There are a few checks that happen. There is an SDK level check through q2 check and then during the dockerize step and the scan step there are dependency vulnerability checks. Also, while the code is running there is a scan that happens periodically on those running services that looks for vulnerabilities in the docker containers.

-Trey

My understanding is that multiple accounts can be listed for the same recipient that is why the account number is also required.

Hello Catherine,

Q2 changes the status on Apps. Please create a ticket on developer.q2.com to request a status change.

This is currently not available for the sandbox. I am curious why you are requesting this for your sandbox?

Hello Ethan,

To navigate to a custom extension you need to use the options signature section. https://tecton.q2developer.com/capabilities/navigateTo/#options-signature

-Trey

Hello, it probably is possible to do that. However, I am not sure the cleanest way. I would probably have a Tecton extension with an account page with account logic and that way you could maybe even have it in a widget. Then the link out be an SSO extension that is called via NavigateTo. Might be best to do a couple quick proof of concepts in the sandbox and see what seems to be working best.

-Trey

Sentinel is a monitor on HQ the backend business logic layer for HQ that Caliper API reaches out to. Sentinel looks at the login and money movement of any kind and maybe a few other things. The endpoints from Caliper API that may invoke some Sentinel calls are the ACH endpoints, the Authenticate endpoint, and the fundstransfer endpoint. It is possible it might be invoked on other calls, but I don't think so.

-Trey

Hello,

We should add some explanation for this, but locked is a state that gets applied after a number of failed login attempts. Resetting the password will unlock the user. Putting a user in a disabled state is a state an admin can put on a login. Resetting the password will not reenable that login.

-Trey