General Description of the Feature
The feature focuses on enhancing the system’s data anonymization capabilities, specifically tailored for Dacia’s requirements under GDPR. The feature ensures that sensitive customer data is anonymized efficiently and in compliance with legal standards. This process involves several key updates to the database structure, user interface, and the data processing workflow.
- GDPR Report Generation: Users can now generate a GDPR report that includes all data linked to a specific business partner. This report consolidates information across various entities and file paths. The action is subject to a cooldown period, which is managed by a setup key (
AllowGDPRReportHoursAfterIssueDate
), ensuring the report can only be regenerated after a specified time frame.
Anonymization Process
Manual Anonymization
A new action allows users to mark a business partner for data anonymization. Once marked, the business partner is processed in a job, which can run monthly, that anonymizes all relevant data fields and entities linked to the BP. This process ensures that data is anonymized according to GDPR standards, protecting sensitive information from unauthorized access.
Automatic Anonymization
- The system automatically triggers the anonymization of data based on specific business rules. These rules consider various factors such as the age of invoices, offers, or contracts associated with the business partner. The anonymization process is executed by a scheduled job (OneFire) that updates the status of the business partner to “To be Anonymized” once the process is finished.
- Then, a second scheduled job is triggered (DB Jobs) anonymizing all the configured fields from all the entities of the respective Business Partner and updates the status of the business partner to “DB Anonymization Completed” once the process is finished. Fields that should be anonymized are configured directly in the database from the relevant team.
- After the database anonymization is complete, the system initiates a final step to delete all associated file paths in DSW, marking the business partner as “Anonymization Completed.” This ensures that no recoverable data remains within the system.
Rules for Automatic Anonymization
The update introduces several hardcoded rules that automatically trigger the anonymization process for business partners. These rules ensure that data is anonymized at the appropriate time, based on the type and age of related documents. The rules include:
Invoice-Related Rule:
- If a business partner has an invoice linked to a Retail Lead or Multi-Unit Sales Lead, the system schedules anonymization 86 months after the document's creation date. This extended period allows for the retention of data as needed for business operations while ensuring eventual compliance with GDPR.
Marketing Opt-In Rule:
- If a business partner has opted in for marketing communications (
Marketing Opt-In = YES
), the system identifies the latest Retail Lead or Multi-Unit Sales Lead and schedules anonymization 36 months after the creation date of the most recent document. This rule balances the need for retaining customer engagement data with the requirements for data minimization under GDPR.
- If a business partner has opted in for marketing communications (
Offer and Test Drive Rule:
- For business partners with an Offer or Test Drive Contract related to a Retail Lead or Multi-Unit Sales Lead, the system schedules anonymization 3 months after the creation date of the most recent document. This shorter retention period reflects the typically transient nature of these interactions.
Disinterest and Marketing Opt-Out Rule:
- If a business partner is marked as not interested (
Not Interested
) and has opted out of marketing communications (Marketing Opt-In = No
), the system identifies the most recent entity (Retail Lead, Multi-Unit Sales Lead, or Inquiry) and schedules anonymization 1 month after the creation date. This rule ensures that disinterested customers' data is promptly anonymized, minimizing unnecessary retention.
- If a business partner is marked as not interested (
Glossary
Terminology | Description |
---|---|
Business Partner Interested | A business partner is considered "Interested" if they have active or potential engagement with the business, meaning they have not only lost retail leads or multi-unit sales leads and do not have only disqualified inquiries. This status indicates that the business partner may still be a viable customer and requires careful management of their data. |
Marketing Opt-In |
|
Fields to be Anonymized | All fields related to the business partner that are subject to anonymization are configurable within the system's database tables. This flexibility allows the system to adapt to changing legal requirements and ensures that only the necessary data is anonymized |
Logging and Monitoring
The system includes comprehensive logging mechanisms that track which specific rules were applied during the anonymization process. These logs provide transparency and ensure that the anonymization process is fully auditable, allowing quality assurance teams to verify that the correct procedures were followed for each business partner.
Business Benefit
This update ensures that Dacia’s data handling practices are fully compliant with GDPR, enhancing customer trust and reducing the risk of data breaches. By automating the data anonymization process, the system minimizes manual effort and ensures that sensitive information is anonymized in a timely and consistent manner, thereby improving overall data security and compliance.
Configuration
Business Cases
- 14010 - GDPR Report
Setup Keys
- AllowGDPRReportHoursAfterIssueDate: Indicates after how many hours the creation will be available again. The default value is 1 hour.
Services
- OneFire: ~/BusinessPartner/InitializeDataAnonymization
Additional Information
New Entities
@IDMS_GDPR_REPORT
Name | Type | Notes |
---|---|---|
Code | NVARCHAR 50 | |
Name | NVARCHAR 100 | |
U_IDMS_BPCode | NVARCHAR 50 | OCRD.CardCode |
U_IDMS_Status | NVARCHAR 50 | New Enum GDPRPrintStatus 0: ProcessStarted 1: ProcessCompleted -1: ProcessFailed |
U_IDMS_IssuedDate | DATETIME | The Date that the zip file creation ended |
U_IDMS_CreateDate | DATETIME | DateTime of the process initiation |
U_IDMS_UserID | INTEGER | OUSR.USERID |
Update Entities
OCRD
Name | Type | Notes |
---|---|---|
U_IDMS_AnonymizationStatus | SHORT | New Enum AnonymizationStatus 0 or null present nothing. 1 - To be Anonymized. 2 - DB Anonymization Completed 3 - Anonymization Completed |
U_IDMS_AnonymizationDate | DATETIME Nullable | Date that the Business Partner got anonymized |
@IDMS_INQUIRY_BUFFER
Name | Type | Notes |
---|---|---|
U_IDMS_CreateLostLead | INTEGER | Store the value of AutoDisqualify property that is exposed in our Inquiry Creation API |
@IDMS_WHOLESALELEAD
Name | Type | Notes |
---|---|---|
U_IDMS_Progress | INTEGER | Marks if the whole-sale lead is Open, Won, Lost. 0 or Null: Open 1: Won 2: Lost |
Add Comment