minvws
We need a clearer Object life cycle, ability to better see where each object came from.
About this feature
Should have for Kennisnet phase: Epic-3 Must have for subsequent phase.
Detailed description
Kennisnet requires an audit trail that stores and informs about the life cycle of objects (when dectected, by what, initiated by whom, when mutated or deleted, etc.)
Feature benefit/User story
As an administrator I want to keep an audit trail from all changes and actions of objects so that I have insight into the history of changes for compliance and security monitoring.
This is important to explain where objects come today, if they are not expected or continue to be wrong. Without this function, it takes a lot of time.
Lets figure out what data we have, and how we can visualize the source for a given object: One or more of he following:
- OOI->boefje->normalizer->$CurrentOOI
- OOI(s)->bit->$CurrentOOI
And also the results for this ooi:
- $CurrentOOI -> Boefje -> normalizer -> OOI
- $CurrentOOI -> Bits -> OOI
I think the design for an object/finding timeline (#3495) will fix these user needs. We discussed the design in stakeholder meetings like the one on 12 march 2025.
