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
{{ message }}
This repository has been archived by the owner on Feb 21, 2024. It is now read-only.
Cases should behave a little like immutable data in a sense that each time a change to a case is made it is saved as a new record in the database instead of updating the previous record. With this we can build a history of changes on a case and can jump back if necessary. For this the cases (aka records) needs another field to save a unique identifier per individual case (not to be confused with the human readable identifier as it's not uniq or the uuid with is uniq for each version of each case). Then all saving etc needs to be adjusted accordingly and a case history view needs to be build
The text was updated successfully, but these errors were encountered:
Cases should behave a little like immutable data in a sense that each time a change to a case is made it is saved as a new record in the database instead of updating the previous record. With this we can build a history of changes on a case and can jump back if necessary. For this the cases (aka records) needs another field to save a unique identifier per individual case (not to be confused with the human readable identifier as it's not uniq or the uuid with is uniq for each version of each case). Then all saving etc needs to be adjusted accordingly and a case history view needs to be build
The text was updated successfully, but these errors were encountered: