What's new in version 6.32

Improve your workflows and data repositories: discover the new pre-approval step for processings and the multi-location management for third parties.

These features will be available starting October 28, 2025 at 6:30 PM.

Summary

New optional pre-approval step in the processing workflow
Multiple address management for your third parties
Bug fixes

New pre-approval step in the processing workflow

To improve content quality and support collaborative workflows, we’re introducing a new optional pre-approval step in the validation flow of processings. This allows teams to review and confirm a processing before sending it into the formal validation step.

Why this new step?

This feature answers a need expressed by many teams where several contributors work on the same processing or when drafters are different from validators.
It brings more control, clarity, and flexibility to internal workflows.

How it works:

The user submits the processing for pre-approval
A pre-approver reviews and either approves or rejects it
Once pre-approved, the processing continues through the standard validation flow

This step is optional: if the feature is not enabled, the default flow remains unchanged.
👉 If you're interested, reach out to your CSM!

Multiple address management for third parties

It is now possible to associate multiple addresses with a single third party, to better reflect the structure of large organizations operating across multiple sites. This feature avoids the need to duplicate third parties and offers improved traceability of service locations.

Why it matters:

Allows grouping of all locations related to the same legal entity
Helps manage complex processings, especially with cross-border flows
Improves data quality and reduces errors or duplicates

What changes in the app:

Third-party detail view
You can now add multiple locations to a third party (e.g., HQ, branch office, data center).
Processing activities
When linking a third party to a processing activity, you can now select the specific location involved. The third-party selection step in a processing has been adapted accordingly.
Import / Export
Import/export templates for third parties now support multiple addresses.
Each address is uniquely identified in the export files.

Correctifs

[Processing] Duplicate entries: Some processings appeared twice in lists.
[Processing/Templates] Update not applied: Changes made to deployed processings were not reflected.
[Processing] Crash on update step: A technical error prevented access to the update step.
[Processing] White screen on duplication: The app crashed when duplicating a processing immediately.
[Processing] General data step error (AI Assistant): A crash occurred during the “General data” step.
[Processing] Security measures displayed as code: Measures appeared as technical IDs instead of labels.
[Processing] Duplicated measures on duplication: Security measures were duplicated twice in copied processings.
[Homepage] Infinite loading: The homepage remained stuck in a loading state.
[Record] Sorting issue on “Internal reference”: Sorting the column didn’t work as expected.
[Assigned directions] Incomplete list: Some processings didn’t appear when filtered by assigned direction.
[Data Categories] Crash from a processing: Accessing the data category list triggered an error.
[Data Category] Translation issue in child entity: Translations could not be edited for inherited categories in child entities.
[Privacy by Design] Save error: A technical issue blocked the save function for requestors filling out a PbD form.
[Document deletion] Residual link: Deleting a document left a residual link in the DSR, causing incomplete deletion.