We are pleased to present version 1.8.5 of Dastra! This new update is packed with new features, exciting improvements, and bug fixes that make your experience even smoother. Discover our new side navigation bar and enhanced identity control in the data collection request forms.
🚀 New Features
Redesigned Side Navigation Bar
We have completely redesigned the side navigation bar to improve the user experience and optimize screen space. Now you can collapse or expand the bar according to your needs. Another new feature: the addition of a contextual submenu that appears when hovering over each functionality, making it easier to quickly access different sections without navigating through multiple screens.
Your display preference will be preserved. When you expand the navigation, it will remain expanded until you close the menu, even if you exit the application or change pages.
This redesign makes navigation smoother, more intuitive, and more efficient. It also aims to improve the user experience on smaller screens such as mobile devices and tablets.
Improved Identity Control in Data Collection Request Forms
Currently, the identity of the requester is verified through a link sent by email, which they must click to validate their request. Without this action, the request is marked as "not admissible". This system, effective against spam and guaranteeing the authenticity of requests, has a limitation: some users do not complete this validation, not always carefully reading the invitation message.
Starting from this update, we are introducing a final step of validation by a 6-digit code. This measure, enabled by default and free of charge, will be applied automatically to all accounts using the data collection request forms upon patch deployment.
🔔 Important: Check translations: If you have customized the translations of your widget in a language other than English, French, German, Dutch, Polish, Greek, Italian, or Spanish, we recommend checking the new translations added in the "contact form" section of the translation editor as well as the identity confirmation email (workspace setting > Data Subject Request > Customization of texts and notification email translations)
Change of Default Title for Data Subject Requests Coming from a Form
The titles now include the request ID and the requester's name. Since the type of right may change during the processing of the request, it seemed more relevant not to "hard code" the title of the request with the right's type.
You will still find the type in the displayed columns.
Addition of a New Type of Right: Access to Administrative Documents (CADA)
If you are a public service, you can receive requests for access to administrative documents under the code of relations between the public and the administration (CADA law).
A new right called "Access to Administrative Documents" is now available in the list of rights.
Modification of ID Formatting for Certain API Objects
In order to enhance the consistency, security, and scalability of our API, we will change the internal ID format for the following objects:
- Tasks
- Requests
- Actors
- Measures
- Assets
Until now, these objects used a numeric format (e.g., 10401, 10200...), which will be replaced by a UUID identifier (e.g., 123e4567-e89b-12d3-a456-426614174000). This format is already used for other objects in Dastra (processings, incidents, AI systems...), and this change aims to unify the API functioning.
The impact of this change should be minor if you use API connectors. However, we recommend verifying that your implementation handles IDs as string values, especially if you use strongly typed languages (Java, .NET, TypeScript...).
Manual Triggering of Automated Workflows
It is now possible to manually trigger a workflow directly from the editor, without waiting for a specific trigger to activate it. You can select an existing item and apply the configured workflow scenario. For example, if you have a workflow that automatically adds a "New" tag to a data subject request upon its creation, you can now run this workflow on an existing request to apply the same treatment. This flexibility allows you to test your workflows without having to wait for the trigger.
It is also possible to retrigger failed automated workflows.
Improved Repository Item Merging
Previously, in order to merge items, you had to select all the items to be merged and click on the "merge" action. This could be problematic when you had a large number of items in your repository and you wanted to merge items that could not be displayed on the same page. To address this issue, you can now select the "merge" action and choose, using a selector, all the items to be merged (regardless of them being displayed on the same page).
This functionality is available in list views as well as from the details page of an item in your repository.
Native Mention Integration with Slack
You can now enable native integration with Slack (workspace settings > Integrations > Slack). Once this integration is enabled, when you mention a user in a conversation on Dastra (@userName), that user will receive a message from Dastra on Slack to notify them that they have been mentioned on Dastra (provided that the user exists in your Slack workspace and uses the same email for their Slack and Dastra accounts).
Automatic Pre-filling of Questionnaires
In this new version, we also introduce the ability to pre-fill questionnaire responses. Now, when you associate a questionnaire with an object, such as a data processing, the questionnaire fields can be automatically pre-filled with the corresponding information from the linked object. This feature reduces the risk of errors by ensuring that the information is consistent across different Dastra modules.
You will find the pre-filling option in the "General" tab when scheduling a questionnaire.
✨ Improvements
- You can now select an accent color on the privacy hub configuration page to customize the color of links and buttons.
- Implemented a selector to specify the volume of data concerned by a breach.
- Changed the freshness icons.
- Possibility to automatically configure SAML SSO via XML Manifest.
- Changed the functioning of anonymizing data subject requests: it now uses random strings instead of random names, which could sometimes lead to confusion.
- Display the name of the custom view in filters.
- Added a new role in the stakeholders of a data processing: Operational Data Controller.
- New language selector in the DSR form
- New model for questionnaires: stakeholder creation
🐞 Bug Fixes
We have resolved several reported bugs to improve the stability and performance of Dastra. Thank you for your feedback! 🚀
Thank you for continuing to rely on Dastra for your GDPR compliance management and beyond. We hope this update will further enhance your experience and productivity. Please don't hesitate to share your feedback or suggestions with us.
We are available if you have any questions regarding these changes.
See you soon for more enhancements!
The Dastra Team.