Editing a page with a fork invalidates all the subsequent data

[barbaracassani]

When, from the confirm page, you edit a datum that could potentially trigger a fork, all the subsequent data are invalidated, and the user must redo the form from that point onwards, which is inconvenient if it was at the very beginning. This has been raised again and again as a bug from RT-GE management: see https://jira.digital.homeoffice.gov.uk/browse/RTP-1317 as the most recent iteration of this "bug" that keeps popping out.

I guess it could be possible to invalidate the data only if

• datum could trigger a fork
• datum has been effectively changed OR has been changed in a way that effectively triggers the fork

[joefitter]

Hi @barbaracassani which version of hof, and hmpo/hof-form-wizard are you using? The intention of this was to invalidate unreachable steps/fields when a fork is taken - if you complete a form, then edit it taking a different fork, any steps/fields no longer reachable as a result of forking are removed from the sessionModel. I know there were previously some issues with this in a previous version but they should be fixed in latest.

[barbaracassani]

@joefitter we use hof 8. It seems like the mere act of revisiting a page with a potential fork causes everything that follows to be invalidated.