One option for you. In the outermost container of your widget, you can apply a negative margin that should cancel out the tecton applied margin:

So in this example it would look like this in the widget html / css:

<div class="widget-container">
	<div>Q2 Account Group Widget Content</div>
<div>

div.widget-container {
    margin: -15px;
}

I hope that helps.

Hi Tanner,

The tecton input doesn't come with any builtin validation (see the docs for more info).

However, this allows the devs to validate it to match our use case using JS. You can use the format modifier to help the user identify the expectation as well. See [format docs](https://cdn1.onlineaccess1.com/cdn/base/tecton/v1.14.0/Documentation/index.html#/ui/q2-input?secti...

Hi Rocky,

There is definitely a lot here to cover. To start, take a look at https://docs.q2developer.com/guides/networking/web_requests.html#third-party-services .

I will address most of your points with my understanding of using the Q2 ecosystem thus far. Heads up, lots of docs incoming...

1. Yes, the docs linked above are a great starting point, then https://docs.q2developer.com/tutorials/online_banking/q2_requests.html?highlight=q2_requests for an implementation example, and fina...

Hi Negar,

What we do is we add a nav node for the new developer and then install individual forms under it. This allows us to work simultaneously.

So for example in the CLI you would do the following:

> q2 db add_nav_node
Which Type of Nav Node?

    1) Route
    2) DirectLink

Please make a selection and press Return: 1
Route

Which menu should this nav node live under? (Leave blank to insert at top level nav)
    --Online Top Level Navigation Menu--

    1) Home
   ...

Hi Khalil,

It sounds like you have a good grasp of what to do, already. You are correct, you do need the repgen name and the procedure. In order to do good testing in dev, you probably also want to build and pass a mock string to the function as well so that you can handle a complete flow, even in development. If your repgen takes other parameters, you can pass those as well. Here is an example of a what a more complete call might look like:

mock_str = """RSRG~2f5342b6-c5f7-4...

Hi Vito,

Is it a specific ticket type that this is happening for? We are able to file tickets without that external ID field filled. Is it possible that another field is actually triggering the requirement? Here is a screenshot of what I get when going to file a ticket:

Here is a good article that goes into some techniques for writing dynamic data to a fillable PDF in python: https://medium.com/@vivsvaan/filling-editable-pdf-in-python-76712c3ce99 . I have not done this in the SDK but assuming that the library passes Q2's QA and Vulnerability checks, you should be able to add the library to your extension with the q2 add_dependency pdfrw and hit the ground running. I hope that helps.

Thank you Clay. I think that I have found the issue based on your comment. There are technically two extensions at play here because of the widget fence and one had the localization file while the other does not. I think that is the issue.

The way that I accomplished this, was to use the q2 db add_nav_node endpoint:

> q2 db add_nav_node
Which Type of Nav Node?

    1) Route
    2) DirectLink
		
Please make a selection and press Return: 1

Which menu should this nav node live under? (Leave blank to insert at top level nav)
    --Online Top Level Navigation Menu--

    1) Home
    2) Home
    3) [redacted]
    4) [redacted]
    5) [redacted]
    6) [redacted]
    7) not used
    8) [redacted]
    9) [re...