docs: document BDM data retention feature — BPA-439#3299
docs: document BDM data retention feature — BPA-439#3299tmarie-bonitasoft wants to merge 2 commits into2026.1from
Conversation
- Add new page 'BDM data retention' in the Runtime module with: - Overview of retention rules and their scope - Tracking mechanism (data_retention_bdm_tracking table) - Composition vs aggregation tracking behavior - Scheduled cleanup (bonita.runtime.retention.schedule.cron) - Queriable log audit trail (BUSINESS_DATA_CLEANED_UP) - Update the BDM composition section with data retention behavior notes - Update the GDPR design guide with a BDM data retention section - Add release note entry for 2026.1 - Update Runtime navigation
📝 Contribution SummaryTo merge this Pull Request, you need to check your updates with the following URL. 🔗 Updated pagesNote The following pages were updated, please ensure that the display is correct: |
|
|
|
🎊 PR Preview e49c087 has been successfully built and deployed to https://bonitasoft-bonita-doc-deploy-pr-3299.surge.sh 🕐 Build time: 0.01s
🤖 By surge-preview |
abirembaut
left a comment
abirembaut
left a comment
There was a problem hiding this comment.
A few comments (editions are to confirm with Product)
other than that it looks good to me
| If you do not want these entries stored in the database, disable the event in `bonita-tenant-sp-custom.properties`: | ||
|
|
||
| [source,properties] | ||
| ---- | ||
| bonita.tenant.queriable.log.BUSINESS_DATA_CLEANED_UP.INTERNAL=false | ||
| ---- |
There was a problem hiding this comment.
not sure we want to document this
- Use 'Performance, Enterprise and Scale editions only' (not 'Subscription') - Add edition note in release notes entry - Remove feature name and version from main page note - Add '(Subscription editions)' to BDM composition tracking heading
4 participants
Summary
Documents the new BDM data retention feature shipped in 2026.1:
data_retention_bdm_trackingtable)bonita.runtime.retention.schedule.cronpropertyBUSINESS_DATA_CLEANED_UPqueriable log eventCloses BPA-439.
Follow-up
A companion PR (BPA-441) adds a procedure for backfilling the tracking table for legacy BDM data. It is based on this branch and should be merged after.
Test plan