Hello,

For automatic staging deploys, the extension has to be installed once by Q2. Once it has been installed once, it will auto deploy for you. To start this process you need to create your App on q2developer.com here https://q2developer.com/marketplace/myapps/manage then go through the app review process to get your app into the staging environment.

Hope this helps,
Trey Teter

Hello Vivian,

This is dependent on whether you want it inan iframe or as a new tab. If it is as a new tab then definitely an SSO extension. If you want it as an iframe in online banking then here is documentation on that: https://docs.q2developer.com/guides/frontend_development/enhanced_sso.html

For either of them you control the security, so you are required to do your own due diligence. During code review one of the things Q2 looks for is security so we will look at that also and try ...

Hello,

1. The config is the default value. The actual value that your extension uses is from the database of wherever the request is coming from.
2. I wouldn't refer to it as overwriting it, but on install you would ask Q2 to write a particular value to the configuration for a particular extension, but yes you would have to specify the key for each tenant that installs the extension. developer.q2.com has tools built in to make this an easy process.

Hope this helps,
Trey Teter

Hello Subha,

The routing on this becomes pretty complicated pretty quickly. You can do an enhanced SSO style workflow https://docs.q2developer.com/guides/frontend_development/enhanced_sso.html To do this with docusign because you most likely can't change the javascript on Docusign's page. You could do a jumper page that adds the needed javascript to make this work. Once it returns from the overpanel you do get a function call on the javascript. You can see that here: https://tecton.q2devel...

Hello Alan,

Sorry for the delay in responding. To incorporate this into the build I would recommend using the package.json file to define how to build your frontend packages. There is a scripts section with a build section that defines what command gets run at q2 run. If you change that to render the css files from your scss files everything should work.

Thank you,
Trey Teter

Hello,

Based on the information that has been provided my guess is the extension was uninstalled from the Q2_WedgeAddress table. You can reinstall this with q2 install

Thank you,
Trey Teter

Hello,

What a cool use case! When we designed the Audit Action Handler, it was not nearly as flexible as you are looking for here. This is a great idea, and we want to help you solve it, but before we propose an interim solution, we'd like to talk as a team and see if there's a more optimal way of organizing this on our side that saves you some work.

There's a few backend things to think through that aren't obvious from the outside perspective and we want to make sure we're following ...

This actually can be found in a few places. My go to way to find this is https://q2developer.com/dashboard there is a section in the Developer Information card that says "Stack Name" the stack name should also be provided in the welcome email.

Hello Draden,

Currently this is not used and not needed. We will remove this from being required. For now, you can just put a random value in this to cause it to work.

Thank you for reporting this,
Trey Teter
Software Engineer

Hello,

Instead of using SendNotification3WithHtml maybe try SendNotification4WithHtml or SendNotification5WithHtml. They are newer versions of this method and better supported. Might work better and more consistently for you.

Thank you,
Trey Teter

Yes, AccountNumberExternalUnmasked would be the number to use.
-Trey

Hello Subha,
In the navigation, and whether a user can go to a particular form is done via group access. To answer your question, yes you should be able to use isNavigable to determine if the current user can access a particular form and then you could navigate to that form with navigateTo.
-Trey

Hello Tanner,

Great question and thank you for bringing this to our attention. We noticed this issue last week and updated the Gitlab client.

-Trey Teter

It is a privacy and a security concern to pull this amount of data. If you have users from out side of online banking that you want to link through online banking you will need to have them login and navigate to your page so that their user info gets sent over to your side. You could accomplish this through deep linking https://docs.q2developer.com/guides/frontend_development/deep_linking.html

Hello Todd,

We used to support docker dev as a setup option for local dev. For various reasons, we transitioned everyone to instead use caliper_admin instead. Long story short, Docker is not a good way to go anymore. If you used to be on docker dev and you are running into issues; we can still help you out, but would prefer you switch over to caliper_admin local dev.

-Trey

Hello Anan,

You are actually heading in the right direction. uux_payload is what you are wanting. When you add something to the uux_payload, that adds it everywhere in online banking. Both existing and not existing pages.

Hope this helps,
Trey Teter
Software Engineer

Hello Tanner,

There could be any number of reasons that it isn't working from it not being installed correctly to something in the extension requesting your user to have specific claims to even simply the server isn't running or the db isn't pointed to your machine. Might be best to create a support ticket on q2developer.com. There we can look at your stack with you and help you track down the problem.

-Trey

There was an issue with q2developer.com this is now fixed.

Hello, I can help you by giving you an exact query string if you give me your stack name, extension name, and your tecton config for that extension(would be found in the configuration folder).

Hello,

Without knowing exactly what page/method you are looking at, it is hard to know exactly what you are referring to. If this is your own code that is adding the Recipient, you could just call out to the api with your code. If not, there may be an audit action that you could base this off of see: https://docs.q2developer.com/tutorials/audit_action/index.html

-Trey

Hello,

You might find the following sections of documentation useful:
https://docs.q2developer.com/guides/code_quality/testing/mocking_db_configs.html
https://docs.q2developer.com/guides/code_quality/testing/unit_testing.html

Also, you can poke around the SDK repo as the SDK has very high test coverage:
https://code.q2developer.com/Q2Antilles/q2-sdk/-/blob/develop/sdk/q2_sdk/tools/testing/mock_handler_mixin.py
https://code.q2developer.com/Q2Antilles/q2-sdk/-/tree/develop/sdk/tests/t...

Hello Draden,
Because every FI has their own DB currency preferences cannot overrite another users in a different FI. UserID is unique per FI, but not unique across FIs. Hope this makes sense.
-Trey

There is some development in the works to improve this, but for now that information is available with window.Tecton.inMobileApp

Hello Tanner,

In general, the best practice is to only have things in Staging that is also ready to go to Production. Of course, that doesn't always work and sometimes a release needs to happen when there is something in the staging branch that isn't ready for production. I recommend two routes. One, if it is a bug that needes to be patched Immediately doing a patch release i.e. doing a branch off of production and fixing the bug then doing a merge request straight to Production. Two, gett...

Hello Draden,

The next SDK release this will be fixed, but use:

ssh sdk-shared-dev.q2devstack.com -l <username> -L 1433:<Database Host>:1433 as the command in the terminal. So in your case: ssh sdk-shared-dev.q2devstack.com -l dradeng@finitloyalty.com -L 1433:sdk-db-14.q2developer.com:1433 Also, on that pop up select Enable Trust Server Certificate which you did, but I just want to say that because that is another piece being added to the documentation.

-Trey

To get when a user was created: https://docs.q2developer.com/api_references/q2_sdk/db/db_objects/user.html#q2_sdk.hq.db.user.UserRow.CreateDate

The short_name is not based on the user or customer at all. That is a reference to the data. The purpose of Customer Data DbObject is to allow for DB storage on a per customer basis. Combines the Q2_CustomerData and Q2_CustomerDataElements tables. The idea is you give it a shortname for a reference for a particular kind of data you want to store an...

Hello,

To get the primary cif you can simply do self.online_user.customer_primary_cif You can see other SSO user specifics here: https://docs.q2developer.com/api_references/q2_sdk/hq/models/SSOUser.html

-Trey

Hello, yes it is in seconds. I will look to add it to the response or the documentation.
-Trey

Hello Tanner,

That object is not generally instantiated manually except for tests. In that case, just pass in You should receive a list of these in your extension from hq in self.account_list. There are many ways in python to search for an individual item in the list.

If you are building an extension that is supposed to sit inside the account details page, then on the first call to the extension you should receive the account id here: self.form_fields["tct-ctxid"]

Without knowing e...

Hello Daniel,

Haviing the nav node under Home is a bit less than ideal. I recommend removing from nav and adding it to be under Services or Settings.

Other than that, make sure you start your server with q2 run before clicking on the navigation tile.

-Trey