Looking at the code, it seems to be requiring both username and customer_id currently. It is supposed to return an error with something like "No username provided" if that is what the problem is. Though, it appears that the way it is written that error might not be making it back to you. You mind making a bug report here: https://q2developer.com/support/create?ticketType=Bug mention my name and I will look into it with you there.

For those looking for proper documentation on hydra codes, we now have a maintained version in the Caliper Api docs: https://docs.q2api.com/docs/uux/u8xmo9xohh5mp-products-and-types
https://docs.q2api.com/docs/uux/bngf0jbihw7sj-retrieve-accounts

Hello Brock,

Certain data is passed along, you can view this by setting a breakpoint and seeing what is inside the self object. For example, the account id is passed back with something like self.form_fields["tct-ctxid"]

Hope this helps

Hello, I will go over this one step at a time, looking at the documentation for get_login_by_id I can see the documentation here : https://docs.q2developer.com/

Inside this docs it is calling stored procedure sdk_GetLoginByUserID Which looking at the sdk code is the file: [code.q2developer.com](https://code.q2developer.com/Q2Antilles/q2-sdk/-/blob/develop/sdk/q2_sdk/sql_scripts/10-get_logon_...

One of two things has happened, either you have selected an account with no transactions. Or the account has transactions they just are too old for Hq to pick them up. If it is the former, select a different account. If it is the latter, you can find the db table(dbo.Q2_HostTransactionHistory), and update those values(PostDate), or you can create a ticket on q2developer.com for someone at Q2 to do it.

The upgrade was a single commit to the default branch. To take advantage you just need to pull that commit to your current branch. To do this open the terminal in the root of your repo and run git pull origin master

Hello Kevin,

The first steps to check is always whether you have access and then whether you have defined access with scopes for the Personal Access Token. I checked all of these for you. You appear to have access and properly defined the scopes for the personal access token. However, I checked on the token. And you haven't seemed to actually successfully called the developer portal using the personal access token to get the jwt. This makes me think there is a bug with q2 login somehow. q2...

PTE or Permanent Test Environment also referred to as Staging environments. The purpose is to be as close to Production environment as possible. So running in the same type of container in the same datacenters with a shared load across both datacenters with access to the same services Production would have access to. The goal with local development is to be as close to Production as possible but running the service locally instead of in the datacenter. So the number of differences between lo...

Hello,

Any specific reason to use navigateTo over submitForm? You can use it like: submitForm("routing_key") see documentation here: https://docs.q2developer.com/guides/online_integration/forms.html

You can still use navigateTo() It would just be quite difficult. You would have to define an entry point for your piece of the code, and do something like: navigateTo(ExtName, entrypoint) It is just using a sledge hammer for a nail.

-Trey

Hello,

Nothing is stopping users from calling submitForm() in the browser, in fact their is nothing keeping the user from running whatever html, css, or javascript on any webpage whether that be online banking or google.com. This is why in the SDK documentation Q2 recommends that developers do python(server-side) validation on the input also.

-Trey

Hello Cameron,

As you know, from the code you can use self.online_user to get all the user details, but based on how you phrased the question I assume you are wanting to know the data outside of the SDK code. Q2 can provide that data given a login name. You could do it via api call using the Caliper Api, or you can just ask for it via ticket on the developer portal: https://q2developer.com/support/create

Hopefully this helps,

-Trey

Hello Ethan,

There are some doc improvements to be made here, but for the most part even though it says optional. In almost all cases AccountsIds are required. The list of AccountIds is expecting something like: account_ids=AccountIds(1, 2, 3) so in your case: account_ids=AccountIds(account_models)

Hopefully this helps,

-Trey

Hello,

We are working to add this to the SDK docs, but for now we have it in the Caliper Api Docs. Please see the following:
https://docs.q2api.com/docs/uux/bngf0jbihw7sj-retrieve-accounts
https://docs.q2api.com/docs/uux/u8xmo9xohh5mp-products-and-types

Side note, bank name doesn't come back with the accounts as far as I know, but you can calculate it off the routing number that comes in from the hq response. Hopefully this helps.

Trey

So there is two methods, on the login page, you can either completely replace the login page or you can add a footer to the current login page. Both require making an unauthenticated Tecton extension. To do that steps are below:

Create a tecton extension(your choice of SSR or CSR).

On the extension.py inside the handler class add IS_UNAUTHENTICATED = True (This should be at the same level i.e. right next to FRIENDLY_NAME

Then you need to install the extension using q2 install N...

Hello Ethan,

For the property to stick you would have to update the database. It isn't very common to update this so you would have to update the property via: https://docs.q2developer.com/api_references/q2_sdk/db/db_objects/user_account_attribute_data.html

Just curious why are you trying to update the label? Updating the account nickname is far more common via: https://docs.q2developer.com/api_references/hq_api/q2_api/ChangeEndUserAccountNickname.html

Thank you,
Trey Teter

Hello,
I have just used hidden input fields(with both hidden and aria-hidden="true"). I have also seen people use the cache to store data between requests.

Hello, there could be a number of things that are wrong, but based on the 404 in the SDK logs, my guess is it is trying to access an entrypoint that isn't there for some reason. I would recommend making a case on https://q2developer.com/support/create?ticketType=Bug with as many details you can give and we will get you working from there. It is quite likely that a quick call with a developer will solve this.

The information I am missing is whether you are working local or on the shared dev...

Hello Justin,

It seems like the answer is unfortunately no. Under the hood, Caliper Api is just calling the Hq method. If you know the device nickname and you pass that along it should return an error if that device doesn't exist.

I talked with the team that maintains the Caliper Api and they are going to take this as an enhancement request. They will do a check before sending the notification to see if a notification will go out and if it will go out then they will send it. If not the...

Hello Chris,

I would need some more informaton. I would need how you are calling self.wedge_address_configs and the full stack trace. I would expect: self.wedge_address_configs['Cognito_Url'] to work.

Looking at the SDK code:

def _validate_db_configs(self, db_config_list: DbConfigList):
        """
        Raises exception if required WEDGE_ADDRESS_CONFIGS are not se...

Hello, there are two options to solve your issue. The underlying issue is safari does not allow mixed content. By mixed I mean http and https together on the same page. On solution is to use the http version of your stack just replace the stackname with your stackname from your dashboard: http://dev-01.q2developer.com/sdk//ardent/uux.aspx#/login This can be a bit tricky as the browser likes to force you to use https. So you need to make sure it is actually loading in http. I normal...

Hello, for security reasons we do not store credit card information in the Q2 Database. You will have to call the core directly to get that information. You can call the core here: https://docs.q2developer.com/api_references/q2_cores/Symitar/index.html?highlight=cards.
To learn how coreflows work, I recommend checking out https://docs.q2developer.com/guides/create_coreflow.html#coreflow

Yes,

The best way to get windowed account history is by using using https://docs.q2developer.com/api_references/hq_api/q2_api/GetAccountHistoryByIdWindowed.html
A great code example of how to use this is from the Caliper API:

get_account_history = GetAccountHistoryByIdWindowedWithUserId.ParamsObj(
            self.logger,
            host_account_id=history_parameters.host_account_id,
            page_size=history_parameters.page_size,
            page_number=history_parameters....

Hello,

In general, there is not a limit on the height of the iframe in any location. Thus having the iframe expand to as tall as it can go doesn't make sense. The iframe should automatically adjust height is needed I recommend reading the documentation here: https://cdn1.onlineaccess1.com/cdn/base/tecton/v1.15.0/Documentation/index.html#/capabilities/resizeIframe

-Trey

This is an area we need to improve our documentation on, but the hydra_product_type_code is a broad category of account types, and hydra_product_code is a more specific type of account. Here is the full list:

• D = Deposit (hydra_product_type_code - Q2_ProductType)
  • C = Checking (hydra_product_code - Q2_Product)
  • M = Money Market (hydra_product_code - Q2_Product)
  • S = Savings (hydra_product_code - Q2_Product)
  • H = HSA (hydra_product_code - Q2_Product)
  • X = Chri...

While it is possible to get user information from the session id. I would reccommend passing user_id instead and then using the User DbObject: https://docs.q2developer.com/api_references/q2_sdk/db/db_objects/user.html

Hello, for your javascript needs I recommend checking out Tecton first. For this specific example:

tecton.actions.scrollToTop();

Should do it. See documentation here: https://cdn1.onlineaccess1.com/cdn/base/tecton/v1.14.3/Documentation/index.html#/capabilities/scrollToTop

Hello,

You could of course manually upload and track it, but if you want to determine that it is relatively universally here:

Q2_CONFIG.filemap['assets/images/logos/logo.png']
Q2_CONFIG.filemap['assets/images/logos/logo_large.png']

From a Tecton app it would be window.parent.Q2_CONFIG

I would recommend some kind of override in like WEDGE_ADDRESS_CONFIGS or something just in case it is not there.

Hello, there is two main ways to add functionality to the login page, one is using a UUX payload, the other is significantly more challenging and that is entirely replacing the login screen. If it is just adding something to the flow, I recommend using the UUX Payload. If you would like to change the behavior of the authentication token you can also use the brand new adapter type extension to add backend functionality on authorization codes here: https://docs.q2developer.com/tutorials/adapter...

This is currently not possible via that method. It is a browser block on that function. Server side it is currently possible, and you can also just throw it in your wedge address config.

There is another method you can check that is available in Tecton v1.10.0 and UUX v4.4.0.122 and higher. Calling window.Tecton.platformUrl should get you the data you are looking for.

Hello, when it says 256px, it is referring to width. The iframe should expand lower as needed to whatever height is necessary.