Hello Dario,

I am going to include general information for those that may see this and want more information about how unit testing works. For those that apply to that see our documentation on Unit testing here:
https://docs.q2developer.com/guides/code_quality/unit_testing.html

For your specific application and a lot of other applications where mocking functions, objects, modules, attributes, and many other things see the pytest documentation here:
https://docs.pytest.org/en/latest/ho...

What do you mean exactly? Do you mean through the Caliper SDK? If so there is no helpers, but sure you can build something. If you are talking about through the developer portal or community page, that is currently not something that is supported. You would have to make something that takes in your emails and posts it to Slack. While the software we use theoretically could make that possible in the future it is currently not on the roadmap.

Hello Pawan,

The questions you have asked are a bit to broad for me to be able to answer in any consise manner on this forum. You mind creating a ticket on the support channel here:

https://q2developer.com/support/create?ticketType=General

This probably necessitates a call. For others that may be looking at this and want more information on how SSOs work, see:
SSO tutorial: https://docs.q2developer.com/tutorials/sso/index.html
EnhancedSSO tutorial: https://docs.q2developer.com/guid...

See documentation here: https://docs.q2developer.com/guides/frontend_development/sso.html#sso-guide

Hello, at a glance it looks like you are missing the entrypoint name. By default I believe this is "Main", so it would be something like tecton.actions.navigateTo('MemberRewards', 'Main') To see full documentation on this see the following:

https://docs.q2developer.com/guides/frontend_development/additional_entrypoints.html?highlight=navigateto

https://cdn1.onlineaccess1.com/cdn/base/tecton/v1.13.1/Documentation/index.html#/capabilities/navigateTo

Hello,

I would recommend you store a JSON string as the value. That way you can store and append multiple values under the same short_name. You can do this via the methods outlined here:
https://www.adamsmith.haus/python/answers/how-to-create-a-json-object-in-python
With more of a description on how those functions work here:
https://docs.python.org/3/library/json.html
You could also store values under multiple short names, but depending on the size and use of the data this is not a go...

This is an old issue that is fixed with a newer version of UUX: 4.4.0.130.

The best way to access this information would be to go to the core and get the data directly, for most cores this requires creating a custom Coreflow. While cPFM does look at that data, it isn't readily accessible from the SDK.

It should be possible to retrieve those fields via passthru. You would need to get documentation from the FI on the core, and it would help to have an interface for accessing the core, so you can work on building those core calls.

It appears that the dbplan did not get run. It is possible that it is either not picking up everything quite correctly, or you just need to run q2 run_db_plan.

Hello,

We have documentation on how to do view and see widget's here: https://docs.q2developer.com/guides/frontend_development/widgets.html

Entrypoint documentation is here: https://docs.q2developer.com/guides/frontend_development/additional_entrypoints.html Doing entrypoints for CSR extensions is a bit more complicated as the documentation states. There is an example in the documentation of how to do it.

Hopefully this helps,

Trey

Hello,

Quick answer, update to the latest SDK version and this issue will be fixed.

Why did this happen and why updating to the latest version is necessary?
The q2-sdk library has a few dependencies one of them being Jinja2. Jinja2 has a dependency to markupsafe that is not version locked. Thus when markupsafe updated with a backwards incompatible change this broke on new installs of the q2-sdk. In any version of the SDK newer than 2.120.0 the issue will be fixed.

This did not break...

The tecton team just released a patch, 1.10.8, that fixes this issue. There was an update to our codebase that required an adjustment to our Babel configuration. This issue seems exclusive to 1.10.7.

Dan's answer is excellent. For number 5, I suppose you come from a C# .NET background. Python does support cancellation of async functions. It works a bit different from C#, so I suggest reading up on how aync functions work in Python to understand this, I would start here and continue looking through the documentation to find what you are looking for: https://docs.python.org/3/library/asyncio-task.html

The difference is hq does not deprecate old endpoints. So if you are building something new, unless you have a really good reason to, use SendSecureMessage2.

This is currently not possible through the SDK. Have your FI reach out to their CEM/RM and ask about Patrol.

Unfortunately UUX escapes everything, there is no way to add any formatting.

Anyone that has built a CSR extension probably can give their valuable experience here. The idea with CSR is to use a frontend framework of your choice and then call back to your CSR extension via tecton.requestExtensionData.

1. The Q2 SDK team has extensively documented the React framework and I have seen many extensions use React. It is evident that the team is very familiar with React. There is a first class guide on it with proper support. See the example at https://gitlab.com/Q2Anti...

Yes, this is possible. Our recommendation would be to use the q2-select element with Robust Option Content. This would allow you to display a fully formatted address, then when the user selects an option you can dynamically update the other fields in the form to their respective values. This would also keep the form's appearance cohesive with the rest of the app. This could be...

This is intended behaviour, if you want to uninstall the DBPlan, run q2 run_db_plan -r. we don't do this by default because two extensions could use the same targets or depend on the same database objects. We don't want uninstalling one extension to break another extension.

q2 db update_nav_node is a command that can be used to change a menu item name in the navigation menu. The menu name is just a value in the database, so it just needs to be changed there.

You can definitely implement an SSO without the "official" SSO extension. There is a few helpers most of which you pointed out that help with making an SSO easier to do. The only thing you really lose is the ability to immediately open the SSO in a new tab or in an Overpanel. Some of this you could do anyway, it just would require some extra work.

There is some written documentation that I would recommend you to read before tackling this project. Our Enhanced SSO documentation:
https://do...

There is a large number of icons available through tecton see https://cdn1.onlineaccess1.com/cdn/base/tecton/v1.8.4/Documentation/index.html#/ui/q2-icons

I see two good solutions. Personally, I would make a wedge address config that takes in the FI name. That way you can set exactly the data you want.

The other option is you can use the ABA number, and use that to determine what the FI is. There may be other ways to do this, but this is how I would do it.

Hello Vito,

Sorry for the delay on this response. In general, all deployment questions are answered in the documentation here:

https://docs.q2developer.com/guides/processes/review_and_deploy.html

To answer your specific questions though. You should be allowed to merge to master. However, the branch may not be configured properly yet because you have yet to do a staging deploy. The first deploy and any configuration changes must be done via deployment ticket as outlined in the guide. ...

Responses typically occur within 1 week but it appears there was an error on our side which didn't allow you to get the notification. I sent you a an email with the proper response to circumvent the error.

Currently the only way to update wedge address configs is through creating a support ticket. This does change the values at runtime.

For testing, you can change the values in your dev environment either by stopping the server, and changing a value and then restarting it. You should be able to do that at any point and it should create the same effect as long as you aren't restarting the server in the middle of a call.

How often are you planning on needing to update the wedge address conf...

I would create another route and then just call submitform('thatRoute'); and then have that route just call the default function. It is kinda a roundabout way to do it, but it is the best way to keep all the right values. Hopefully this makes sense.

Hello Vito,

1. I am suprised that the q2 commands are not working. Since you have attached the container I would have expected in that window that opening terminal and running "q2 -h" would have resulted in showing a list of available q2 commands. If this is still the case, make a comment here and I will reach out to you directly and we can setup a call and figure out why what is happening is happening.

2. The URL for "Total Access" will be the same as in the welcome email as well as on...

Hello Vito,

That is indeed a slight bug, however it is in visual only. The functionality is actually fine. There are certain cases that you can trigger a validation message on that field, however you are actually just missing another field and you can submit the form without filling out the External Issue ID. I am doing a patch release on the Portal now to fix this issue.

Thank you for finding this issue,

Trey Teter