You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Save your changes as a "new version", with a new version number
Notice that the version number in the JSON schema did not get updated --> This is especially relevant for forms you are about to save in your config files, because you can easily end up with many different form version numbers, but they are all the same version in the JSON!
Example in dev3 right now: Laboratory Tests version 2.1 was successfully saved as version 2.1, but in the JSON, you can see it is still written as "version 2".
Expected: Whatever version number the user enters in the Save Details Modal should automatically update the "version" tag in the JSON file, when the user clicks "Save" on the modal.
Let me know if this is not clear :)
The text was updated successfully, but these errors were encountered:
Replication Steps:
Example in dev3 right now: Laboratory Tests version 2.1 was successfully saved as version 2.1, but in the JSON, you can see it is still written as "version 2".


Expected: Whatever version number the user enters in the Save Details Modal should automatically update the "version" tag in the JSON file, when the user clicks "Save" on the modal.
Let me know if this is not clear :)
The text was updated successfully, but these errors were encountered: