Feature request: enable `update_data` on footer components

[mickbut-ler]

Current Limitation
Right now, footer buttons cannot invoke a update_data

I’d like to be able to attach a update_data directly to footer buttons.

---

Why This Matters

• Single-Screen, Multi-Step Flows
  We often guide users through a sequence of steps, surveys, tutorials, onboarding using just one screen definition. Each footer click, next advances the user to the next step based on their journey, same screen different data.

If update_data would be possible, we could send the all steps during the initiation of the flow, and use update_data to set the state, without data exchange

---

Simple Example

Today’s Flow (no update_data)

1. User taps “Next” in the footer.
2. Client issues a full data_exchange.
3. Server returns a brand-new screen JSON.
4. Client discards the old view and renders the new one.

Proposed Flow (with update_data)

1. User taps “Next” in the footer with update_data: { step: 2 }.
2. Client uploads { step: 2 } to the server.

[yehuda-lev]

Hi, I am currently using a variable that is set to false, and as long as it is set to false the Fotter is disabled.
And only if the update_data was triggered during the screen does it change to true, then the Fotter is enabled and can move to the next screen...

[mihail-hristov-meta]

Hi @mickbut-ler, thank you for reaching out! We appreciate the time you took to provide this feedback. We'll consider it for future updates, but can't confirm if or when it will be implemented. To stay up-to-date with the latest changes, please keep an eye on our changelog