Discussed with Laurens and Dimpact beheer. To avoid questions about why importing a form generated in a newer version of OF doesn't work, it would be nice to show a warning if you are trying to import such a form where the major+minor version is different.
Case was a situation where OF 2.3 was still running and the user attempted to import a form which was built in OF 2.5.
We discussed that the warning wouldn't block the user, it's just a 'YMMV' for the situations where the delta between two versions of OF becomes significant. This will most likely become more relevant with initiatives where forms can be reused between municipalities.
Added value / Toegevoegde waarde
Less questions from formbuilders on why the importer is raising a HTTP 500
Additional incentive to ensure test+acc+prod remain on the same major+minor version
joeribekker
commented
4 months ago
Thema / Theme
Admin
Omschrijving / Description
Discussed with Laurens and Dimpact beheer. To avoid questions about why importing a form generated in a newer version of OF doesn't work, it would be nice to show a warning if you are trying to import such a form where the major+minor version is different.
Case was a situation where OF 2.3 was still running and the user attempted to import a form which was built in OF 2.5.
We discussed that the warning wouldn't block the user, it's just a 'YMMV' for the situations where the delta between two versions of OF becomes significant. This will most likely become more relevant with initiatives where forms can be reused between municipalities.
Added value / Toegevoegde waarde
Less questions from formbuilders on why the importer is raising a HTTP 500 Additional incentive to ensure test+acc+prod remain on the same major+minor version
Aanvullende opmerkingen / Additional context
No response