v0.04

Major version bump with unicity management in DB to ensure adequate performance of agregates.
First release with a decision to case automation

Frontend :

• fix: error in decision tab of a scenario
• feat: improve user auth error handling
• feat: improve data formatting (date, number, links…) in decision viewer and case manager. You can now add an clackable URL to each object, for use in the decision viewer and case manager (helps sending the operators to the right page on your back office for eg).
• feat: better instruction on how to deploy a scenario following the v0.03 performance refacto
• feat: add role in user info (top left of the interface)
• feat: new logic when opening an existing scenario (live if any, or most recent iteration)
• data model tab: tables appear collapsed by default

Backend :

• feat: automate decision to case creation (new field decision_to_case_inbox and decision_to_case_outcomes on the scenario (models, dto, db).
• feat: unicity management : to ensure performance and consistency, you can now define "unique" fields within each table. Those fields can be used to create link between tables and avoid duplicates.
• feat: store hashed value of generated api keys
• fix: bug fixes on DB field read
• reduced sentry sampling rate (backend)

If you are self-hosting Marble, you may have to run a migration script to ensure unicity for object_id and all other unique fields before this version bump.