What's new in version 6.26

This update introduces improvements to pre-filling processings via Privacy by Design, bulk conversion of processings to a custom regulation, and new bulk actions. Additionally, processing duplication now includes impact analysis details.

Content

• Improved pre-filling of processings via Privacy by Design

• Bulk conversion of processings to a custom regulation
• Bulk actions on processings

• Processing duplication - Impact Analysis step

• Fixes
  
  • [Action plan] - No notification sent when deploying the action plan
  • [Accountability] - Document export issue in the Anticorruption module
  • [Privacy by Design] - Incorrect user initials
  • [Processings] - Creating a processing with an assigned department
  • [Analytics] - Duplication o the number of processings
  • [Processings] - Domain change function unavailable

 

Improved pre-filling of processings via Privacy by Design

---

 

We have enhanced the pre-filling functionality of processings from Privacy by Design to include new custom fields.

• New pre-filled elements

  • Custom fields: Auto-filling of custom fields defined based on the custom mode of the selected entity.
  • Retention date: Auto-filling of the retention date field in the Data Category section of the processing.
  • PIA analysis criteria: Inclusion of the 9 PIA evaluation criteria to ensure better risk assessment when creating a processing.

 

Bulk conversion of processings to a custom regulation

---

 

You can now convert all existing processings in an entity to a custom regulation.

On the entity configuration page ("Entity Assignment" page, accessible by clicking the gear icon at the top right when in the "Processings" tab), an action is available to convert all existing processings in the entity to the selected custom regulation.

• If all processings are already in the selected regulation or if no processings exist, the action will be disabled.
• From the processing list, you can convert a processing to the custom regulation applicable to the entity. If the processing is already in this mode, the action will be disabled.
• Only processings with a status other than "Validated" or "Archived" can be converted.

 

Bulk actions on processings

---

 

It is now possible to convert multiple processings to a new regulation directly from the processing list. Unlike the existing functionality in the processing settings, this version allows you to select only specific processings and convert them in just a few clicks.

You can convert any processing to an active regulation for the entity, as long as it is not "Validated" or "Archived." More bulk actions will be available in the coming weeks! 🎉

 

Processing duplication – Impact analysis step

---

 

When duplicating a processing, the question "Have you conducted an impact assessment?" from the Impact Analysis step, along with the text entered in the "Remarks" field, will now be duplicated. Attachments associated with this step will not be copied.

 

---

 

Fixes

 

[Action plan] - No notification sent when deploying the action plan 

Notifications were not triggered when an action plan was deployed. This issue has been fixed.

[Accountability] - Document export issue in the Anticorruption module

Fixed a bug preventing document exports in the Anticorruption module.

[Privacy by Design] - Incorrect user initials 

Users were sometimes displayed as "Unknown User" instead of their correct initials. This issue has been resolved.

[Processings] - Creating a processing with an assigned department

Fixed an issue preventing a department from being assigned when creating a processing.

[Analytics] - Duplication o the number of processings

The Analytics module incorrectly displayed twice the actual number of processings. This issue has been fixed.

[Processings] - Domain change function unavailable

A bug prevented users from changing the domain of a processing. This issue has been fixed.