Introduction
The purpose of the AnonymizationTask manage the anonymization process.
| Value |
|---|---|
GUID |
|
Scheduled by default |
It is scheduled by default but to actually do something - it has to be enabled How-to configure Anonymization |
Interval in seconds | 60 |
Concurrent |
|
Parameters | uint[] with CoreIdentity Ids |
Anonymization Process
The anonymization process is the part of GDPR capability. After the Core Identity is deleted - system can delete the Personal Data that is in CoreIdentity+CoreIdentityAttributeValues and Identity+IdentityAttributeValue and in change entries.
The process involves a few tasks and is illustrated by timeline below:
ID | Action | Description | Core Identity Anon-State | Identity Anon-State |
|---|---|---|---|---|
- | There is some happy Core Identity | NotAnonymized (1) | NotAnonymized (1) | |
1 | Delete Core Identity | Core Identity state changed to Deleted | AnonymizationNeeded (2) | AnonymizationNeeded (2) |
2 | AnonymizationTask runs | Core Identity + Core Identity Attribute Values are anonymized Core Identity change entries are anonymized | HistoryAnonymized (5) | |
3 | UpdateIdentityTask runs | Identity Attribute Values are anonymized | AnonymizationStarted (3) or HistoryAnonymizationNeeded (4) | |
3B | ProvisionIdentityChangesTask runs (fastracked) | Anonymized changes are provisioned to Target System | HistoryAnonymizationNeeded (4) | |
4 | AnonymizationTask runs | Identity change entries are anonymized Clear | Anonymized (6) | Anonymized (6) |
You can see what is the action taken by each step and also what is the Anonymization state that is set at the end of the step on Core Identity and Identity.
You can diagnose process looking at anonymization states of Core Identity and Identity. You will recognize which steps were run and which are still to be run.