What's new in version 6.34

Summary

• New in the Privacy by Design module: update an existing processing directly from a project

• Bug fixes

You can now update an existing processing directly from a Privacy by Design project review.

What’s new?

When reviewing a PbD project, you now have two options:

• • Create a new processing (as before)

  • Link and update an existing processing using the questionnaire responses

The system automatically suggests updates based on matching fields between the questionnaire and the processing.
You can then validate or adjust each proposed update before applying them.

Benefits

• • Time-saving: Avoid manual copy-paste between questionnaires and processings

  • Data consistency: Reuse information already collected in the PbD project

  • Improved collaboration: Delegate project input without losing automation

  • Traceability: All changes are logged and recorded

Permissions & Controls

• • Only users with the "Edit a processing" permission can perform this action

  • If the processing is in a “Validated” status, it will automatically switch to “Update pending validation” after changes

  • Users can preview all proposed changes before applying them

Repositories

If a questionnaire response refers to an item that doesn’t yet exist in the relevant repository (e.g. third parties, data categories), the user will be prompted to create it before completing the update

Correctifs

• • [Processings] Bulk edit not working
    The bulk edit feature in the processings list was not working correctly. This issue has been fixed.
  • [Processings] Latency issues
    Performance issues and delays were experienced when loading or interacting with processing records. The system has been optimized.
  • [Third Party Repository] Delay in third-party creation
    Creating a new third party could take several seconds. The response time has been improved.
  • [Campaigns] Unable to submit an opinion
    Some users could not submit feedback on ongoing campaigns. The issue has been resolved.
  • [Actions] Error when removing a responsible user
    An error page was displayed when deleting an action owner. The deletion now works properly.
  • [Accountability] Unable to download document
    Document downloads in the Accountability module were failing. The bug has been fixed.
  • [DSR] 500 error on the form after user deletion
    If a user linked to a DSR was deleted, the form could no longer be accessed. This has been corrected.
  • [Record] Data category search not working
    Searching by “Data Categories” in the register returned no results. The filter is now functional.
  • [SSO Login] Error message on direct URLs
    Users accessing the platform via direct SSO URLs encountered an error. The redirection flow has been fixed.
  • [Privacy by Design] Only last 10 comments were saved
    Only the 10 most recent comments were being retained in PbD projects. All comments are now properly saved.
  • [Entities] Column sorting unavailable
    Sorting options were missing from the entities and affected directions tables. Sorting has been restored.
  • [Record] Incorrect column display in customization
    When selecting a single identification column (e.g. “Internal reference”), all ID fields were still displayed. This behavior has been corrected.
  • [DSR via API] Duplicate DSR reference numbers
    When creating a DSR via the API, the same reference number could be assigned to multiple requests. Uniqueness is now enforced.