What's new in version 6.24

Convert processing activities and simplified access to the Compliance Cockpit

 

Content

• Convert processing activities to a custom regulation mode

• Access Compliance Cockpit from Provacy Cockpit
• Bug fixes

  • [DSR] - Missing responsible in the "Responsibles" column on the DSR homepage

  • [Actions] - No access to the Actions module if the user doesn’t have access rights to processing activities

  • [Record] - Excel export generation is not working

  • [Record] - Extended mode data appears in the Article 30 export (Standard mode), even though it shouldn’t

  • [Processing] - "Oops" error page appears in processing models

  • [Analytics] - "No result" is displayed for PIAs even though PIAs exist in the entity

     

---

 

Convert processing activities to a custom regulation mode

Entities that have created custom compliance modes can now convert their existing processing activities to these new regulation modes. When converting, the processing activity will automatically adapt to the new fields defined in the target mode.

📌 How to convert a processing activity?

1. Go to the processing activity you want to modify.
2. Click on the "three dots" menu at the top right.
3. Select "Convert Compliance Mode".
4. Choose the desired mode and confirm.

⚠️ Currently, conversion is only available at the individual level. The option for bulk conversion will be available soon.

 

Access Compliance Cockpit from Privacy Cockpit

You can now access Compliance Cockpit directly from your Privacy Cockpit space.

• If you already have access, you will be redirected to the login page.
• If you don’t have access yet, you can explore the platform and request a demo.

 

---

 

🐞 Bug fixes

[DSR] - Missing responsible in the "Responsibles" column on the DSR homepage

This has now been fixed, and responsibles are correctly displayed.

[Actions] - No access to the Actions module if the user doesn’t have access rights to processing activities

The fix ensures that users with the correct permissions can now access it without error.

[Record] - Excel export generation is not working

The export was failing due to missing data in security measures. This has been corrected, and exports now work as expected.

[Record] - Extended mode data appears in the Article 30 export (Standard mode), even though it shouldn’t

 The export was incorrectly including data from the extended mode. This has been fixed, and only relevant data is now included.

[Processing] - "Oops" error page appears in processing models

A missing value in the model data was causing the error. The issue has been fixed to ensure models load correctly.

[Analytics] - "No result" is displayed for PIAs even though PIAs exist in the entity

The system was not correctly fetching the existing PIAs. This has been addressed, and the correct results now appear.