1
Add Versioning of Objects
Source: twentyhq/twenty#19781 · opened by @L00tz1ffer
Scope & Context Every entry in the CRM is a momentary record. This means that if someone accidentally overrides data of any kind, it is effectively gone. The idea is to provide the user with a journaling system, similar to an append-only interface, so that data is never truly deleted but instead flagged as deleted. At the same time, there must be an option to delete certain data when required, for example in response to a "DSGVO request" involving any contained user. Current Behavior • Data is stored only as a snapshot of the current state and does not maintain a history/log as expected. • Once data is modified, it cannot be reverted to a previous state (step n). Expected Behavior • Consistent logging of all changes, potentially implemented via diffing. • An append-only data structure where all changes are clearly traceable, e.g. via UUID + timestamp. • Each object should provide a back button as well as a forward button. • If the b…
No pledges yet. Be the first to back this.
Comments
Similar requests
Extend the Role settings for objects with a flag "access to assigned objects
1 vote · 0 comments
What is the release versioning strategy ? Is there a long-term upgrade path?
1 vote · 0 comments
Feature request: configurable keyboard shortcuts for custom objects
1 vote · 0 comments
Custom images/avatars for People records and custom objects
1 vote · 0 comments
App sync fails when an app declares a relation to a custom object owned by another app ("has no relation target object metadata")
0 votes · 0 comments
No comments yet.