Hi Draden,

The member or user information is available through self.online_user in extension.py file.
so login name, first name ,lastname ,address too available in online_user.

Thanks,
Swarup

Hi Ethan Pittman,

I don't think we can create new html content inside the model. we can use existing capabilities provided by the tecton modal. I think you can go for adding an available js library to use any model if you want to show custom HTML content.

Thanks,
Swarup

Hi Geoff Lo,

if you are using CSR or SSR extension you have following ways to grab URL params

using tecton grab query paramater from html code and send to Q2 extension's route:

  tecton.sources?.paramsChanged((newParams: any) => {
    console.log(newParams, 'newParams');
    cdRenewalExtension = newParams?.access_key;
  });

in python:
self.get_argument('code', None)

Thanks,
Swarup
swarup@nuevesolutions.com

Hi Noah,

No, we don't have the flexibility to run the same Ardent extension by different developers at the same time.

the extension created inside the stack is accessible to other developers within the group. one can run the same extension but all at once cannot run the same extension

Thanks,
Swarup
swarup@nuevesolutions.com

Hi David,

from Q2 extension you can't able to get fI name .however from front app inside Q2 you can access finame from url is the only way in prod env.

Thanks,
Swarup,
https://nuevesolutions.com

Hi Cameron,

Q2 sdk's send notifications hq_api works and sends email .i seen the params are sending in wrong order.can you try adding params in following way.

notification_type = 1 // for email
email = your email
subject = email subject
body = """
<p>Email content <b>[{}]</b></p>
""".format('variablename')
message_params = ParamsObj(self.logger, notification_type, email, subject, body)
await SendNotification.execute(message_params, True)...

Hi,

The extension can be installed to multiple FI's the best way to identify the FI is to add the wedge_config field if it's a client-side extension or vendor_config if it is an SSO extension. the wedge configs /vendor configs will be saved in DataBase .so during deployment you can update the extension-related key and perform business logic over it.

Thanks,
Swarup
htttps://nuevesolutions.com

Hi Steve Hushek,

1. you need to request the Q2 team on the q2 developer portal to create a project under your stack .Q2 creates a repo .and you can switch to the repo in your stack. or else you can clone the project from the git and you need to activate the project env(source .env/bin/activate). you can copy the existing .env folder from the SDK folder in your stack before activating.

2. you need to create a entry point extension using the Q2 command **q2 create_entrypo...

Hi Chris,

If you are using an online client-side extension then you can add a key in wedge_config per FI. if you are using SSO extension you need to add the key in vendor_config.and if suppose your project contains multiple extensions you can also grab the wedge or vendor config details of SSO extension in other extension with the following Q2 methods.

accessing vendor configs of SSO extension in other extensions

from q2_sdk.hq.db.vendor_config import VendorConfig
from q2_sdk...

Hello , can you remove the existing docker image and start a new one it will automatically prompts you to pdate, here are the steps

1. Need to remove the container,image(docker rm <container_id>)
2. Reopen the terminal and run the below command, it will pull the latest docker image
   **./start_dev_machine.sh ** (prompts for new docker update to continue)

HI Dan Collins,
The Q2 vault add cli tool is sufficient for development. development env is actually using filesystem in local dir to store and retrive vault data. comming to stg/prod a real datacenter environment, the Vault service will be running and serving these secrets.
In stg/prod we need to request Q2 team to add secrets in vault because Q2 vault add adds only in devlopment env.

vault also provides access based on institution level and each environment level.

T...

In dev env we can run entrypoint by using q2 command

q2 entrypointname

but in staging or test env .the entry point extension runs in scheduled time like cron job.
and you need add logs using self.debugger instead of Print to actually see the entrypoint flow.
finally Q2 team will get back with logs of entrypoint run.

Thanks
swarup
www.nuevesolutions.com

you can create a new user in dev env with following command:

q2 create_online_user

You can select Group based on your requirement and add user details .once you get prompt in terminal.also you can see list of available Q2 commands using "q2 help"

Select Group

    1) Retail Users
    2) Commercial Users
    3) Merchant Verification
    4) Q2 Test Group - DO NOT DELETE
    5) Q2 Retail Default
    6) Q2 Retail ExternalTransfer
    7) Q2 Retail PositivePay
    8) ...

1. Yes whitelisting can be a domain level names
   for example:

OUTBOUND_WHITELIST = [
    'abc.com', 'bcd.com'
]

2. yes it is based on Domain Name and For access in an environment hosted in the Q2 datacenter.
3. https://docs.q2developer.com/support/index.html?highlight=outbound_whitelist#i-need-to-whitelist-a-url

swarup bangaru
www.nuevesolutions.com