I believe we spoke about this yesterday during Office Hours. As a summary here, the statement image adapter could be used to do this, but it would replace the built in thing Q2 provides, so you would have to also implement monthly again.
As such, I think we landed on building a new form that you own the frontend too as well that deals with yearly statements if you were to do this yourself. Though, there might also be the possibility that Q2 has a way to update its builtin adapter to handle...
Where are you developing from? I would expect local-dev-api.q2developer.com in that list would provide your host. Maybe you're on the shared dev box?
Should be whatever your Q2SDK_VAULT_LOCAL_DIR env var is set to: https://docs.q2developer.com/guides/configuration.html#vault-local-dir
This is a good callout. It's kinda hard to get at this information, since we only have a user_id and login_name from the SSO handler perspective. But we can make it work with a few calls:
async def get_is_commercial(self) -> bool:
customer = await self.db.customer.get(login_name=self.online_user.login_name)
group = await self.db.group.get_by_id(customer[0].GroupID)
return group.IsCommercial
We do not. We've done some work on "take a screenshot of the page and make it a PDF" type stuff in some internal repos, but it's a little weird. It's not exactly a screenshot, but kind of a "pretend you're a browser with selenium and render a React widget". I wouldn't recommend that path.
This should be taken care of. The sdk_DeleteHostAccountClickType is something still for us to work through, but the rest of them have been fixed. Thanks for the bug report!
Unfortunately, it's more complicated than that. xmlsec itself depends on libxmlsec1, which is a C library. These can either be compiled to order or pulled as precompiled wheel (whl) files for python based on each operating system.
On Friday, I uploaded precompiled wheels for all the mac + xmlsec + lxml versions I had access to and reuploaded them. Even so, there's is a segfault potential in the xmlsec package on modern mac versions. As such, since 2.266.1, rather than segfaulting, we try m...
Is this a public gitlab repo or something? In our code.q2developer.com pipelines I would expect the q2-sdk library to be visible.
Hi Bradley,
EDV will be sent regardless to the extension, but one of the properties is is_suspect. You can do with that what you will, either terminate the session, perform step up, or move on. There are of course several other fields passed in with that object for you to action on.
In terms of adding EDV in front of existing extensions, it's possible to configure an SSO to do this in newer version of UUX, but it's just the system's built in step up, not necessarily a custom built thing...
Hi Mark,
Looks like you need to run caliper_admin -> Switch Stack and put in your stack name as per the dashboard on q2developer.com.
That'll set your HQ and all the other variables appropriately.
Brian
Sorry about this, we pushed out a new versino of caliper_admin to update this. You should be set to PIP_INDEX_URL=https://devpi.q2developer.com/root/q2/+simple now.
Running caliper_admin update and then switch_stack will do this for you, too.
The crux of it was pip has changed some of its shapes so we had to conform.
HI Tanner,
Sdk version 2.224.0 had this issue. 2.224.1 should be able to fix this. You can pip install q2-sdk==2.224.1 manually. Or you can work around the issue with pip install setuptools directly. Switching to python3.12 had a few edgecases we didn't catch until the patch version.
Brian
I don't think so. Typically an integration takes either the bank or the fintech to be members of the Q2developer community.
This is tough. We can't provide much feedback through HQ to the frontend unless we return a 200 I believe. But I understand your desire to have the 500 in your SDK backend logs to easily figure out which requests failed. We can look and see if there's a better mechanism in the HQ side for this, but at the moment I think your pattern is the preferred one.
Hi Ethan,
Not really, unfortunately. Dispute information is not logged into our database, so there's no DB object or the like that could pull that info to my knowledge.
Brian
Ryan,
Thank you for your bug report. A service had turned off and changed its docker image location and therefore couldn't automatically restart. This has been updated and service should be restored.
Brian
Regarding #3, it's probably just easiest with the way the product is set up to request the render in new window true/false at deploy time for an FI. The variable in the extension hints to the installer whether to set a database flag as true or not on installation, as you pointed out. But we have the ability to flip that database flag at any time. So while it's listed in the extension for convenience as a way for the dev to message to the one installing the extension later (who might also be y...