Josh Crawford

Added in [2.0.10](https://github.com/verbb/formie/releases/tag/2.0.10)

Is that a problem? The correct behaviour should be that it's `null` when the index has yet to be set. `0` would be returning if say you submitted the form...

All good, just wanted to check! I'll have that fixed up, but might be in Formie v2 with some other changes related to pages and active states.

Fixed for the next release. To get this early, change your `verbb/formie` requirement in `composer.json` to: ``` "require": { "verbb/formie": "dev-craft-4 as 2.0.9", "...": "..." } ``` Then run `composer...

Fixed in [2.0.10](https://github.com/verbb/formie/releases/tag/2.0.10)

Just to be clear, it looks like you're proposing two things here? - Being able to set the status on every page submission (for multi-page forms) - Update the status...

Yeah, the second part might be tricky to manage without a more major change, where we'd need to add status to each page settings, so you could set a status...

The more I've thought about this, the more potential caveat's I'm seeing crop up. For example, if we had a mechanism to set the status based on the value of...

Would this be different to the current "Replies" section, where you can see the replies on a comment? Or more the other way around (on a reply, show the parent...

Should be fixed for the next release. To get the fix early, change your `verbb/field-manager` requirement in `composer.json` to: ``` "require": { "verbb/field-manager": "dev-craft-4 as 3.0.2", "...": "..." } ```...