docs: document how to backfill tracking for legacy BDM data — BPA-441#3300
Open
tmarie-bonitasoft wants to merge 1 commit intodocs/BPA-439-bdm-data-retentionfrom
Open
docs: document how to backfill tracking for legacy BDM data — BPA-441#3300tmarie-bonitasoft wants to merge 1 commit intodocs/BPA-439-bdm-data-retentionfrom
tmarie-bonitasoft wants to merge 1 commit intodocs/BPA-439-bdm-data-retentionfrom
Conversation
|
|
Contributor
📝 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: |
Contributor
|
🎊 PR Preview f5ec5bc has been successfully built and deployed to https://bonitasoft-bonita-doc-deploy-pr-3300.surge.sh 🕐 Build time: 0.011s
🤖 By surge-preview |
tmarie-bonitasoft
force-pushed
the
docs/BPA-441-legacy-data-migration
branch
from
d723c08 to
0893ffb
Compare
Add a 'Handling legacy data' section to the BDM data retention page: - Explain why pre-existing BDM instances are not tracked - Step-by-step migration procedure (identify, insert, verify) - PostgreSQL example query for backfilling the data_retention_bdm_tracking table Cross-link from the GDPR design guide.
tmarie-bonitasoft
force-pushed
the
docs/BPA-441-legacy-data-migration
branch
from
0893ffb to
f5ec5bc
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Documents the manual migration procedure to bring BDM instances that existed before the data retention feature under retention control.
Added to the BDM data retention page:
#legacy-dataanchor)Cross-linked from the GDPR design guide.
Closes BPA-441.
Depends on
Based on #3299 (BPA-439) which creates the BDM data retention page this PR enriches. Retarget to `2026.1` once #3299 is merged.
Test plan