Passing Query Parameters to S3 Upload Component From Page Flow?

Wappler General Need Help
1

Is it possible to pass parameters from a page flow to the S3 Upload Component in App Connect?

Description:
I'm using a page flow from a dmx-on:click event on a button (type=button) to call an S3 Upload Component on the page.
Page Flow Snippet:

if: "{{formUpdatePage.file_header_img.file.size>0}}",
        then: {
          steps: {
            run: {
              output: true,
              outputType: "text",
              action: "{{s3UploadHeader.upload()}}"
            }
          }
        }

The S3 Upload calls my API to get a signed URL.
Snippet:

<div id="s3UploadHeader" is="dmx-s3-upload" url="/api/zone/pages/pages_S3SignedURL" accept=".jpg,.jpeg,.png,.webp" dmx-on:success="formUpdatePage.inp_header_img_url.setValue(s3UploadHeader.file.dataUrl);flowSaveBackground.run()" dmx-on:error="notifiesMain.warning('Header upload failed')" dmx-hide="true">
</div>

The signed URL API however needs two params ($_GET.foldername, $_GET.filename) to create the Key (remote path). How can I pass these params from the page flow to the S3 Upload component, and then into the API from the S3 Upload component?

Sometimes I feel like I make up how Wappler works. This may be one of those cases so perhaps there's a more "native" way to accomplish this?

2

You can't pass params in the upload method. You can define your params in the s3 component UI:

Screenshot 2026-01-20 at 8.49.46
Screenshot 2026-01-20 at 8.49.46361×419 18.6 KB

It works the same as if you simply call the upload method via a button click event.

3

After applying the Params through the UI, what does the code in the s3 component look like? My application still uses wappler v6.8 and I don't have this option in the UI.

4 
 dmx-bind:params="{foldername: dynamic_value_1,filename: dynamic_value_2}"

It's 2026 already, maybe simply update Wappler, so you can do this using the UI.

5

Thank you for the code view.

As for updating Wappler, these are the main reasons:

  1. Regression testing the entire app is time-prohibitive,
  2. Since v7's release, there have been too many critical issues I've seen reported, making an update far too risky still,
  3. I've had to modify some of the source within lib/ to close some feature gaps I needed implemented.

If a document exists or can be produced showing app connect and server connect behavior changes between v6 and v7, to help guide what regressions might exist in a project following an update, I would be more than happy to read it.

Wappler is so good, it supports critical web applications. The owners (like me) of these web applications cannot simply update to a new version every release because the application itself must be resilient. My choice to not update to v7 is no different than the choice any system admin would make for an application that is trying to maximize uptime and meet SLA's. If Wappler were merely an IDE, I would "simply update Wappler" far more often. But it is also a deployment and execution framework and therefore plays a much bigger role in the stability of the application it supports. I hope you come around to my view of how critical Wappler is to anyone choosing it as a major part of our tech stack, and what it would mean to any small business to simply update Wappler only to have the live site no longer work.

1 Like