Release 263 (24.03.2025)
Release Notes
Version: 263
Release Date: 24.03.2025 5:00AM CET
Overview
This update introduces new features like the SCIM PUT method for updating user records, improved assessment permalink settings, and enhanced workflow management. System reliability has been increased with automatic Go pod deployment, and Filerskeeper retention updates now support standardized values. Additionally, logs are now sorted by newest entries first, and a new endpoint allows quick change detection. Several bug fixes improve overall stability and user experience.
Contents
What's New
New Features
- SCIM – Add PUT Method
- Description: The PUT method has been added to the SCIM API, following the RFC 7644 specification. This allows updating entire user or group records in the system. If an entry already exists, it will be overwritten with the new data.
- How to Access: IT Settings > Identity & Access Management
- Assessment Permalink
- Description: Several enhancements and UI updates have been made to the Assessment Permalink settings, improving visibility and user experience when accessing assessments:
- Added a toggle button to enable/disable the assessment permalink.
- Added a “Submissions” toggle to set the maximum amount of submissions
- The general view now displays how many assessments have already been created from the permalink.
- If the maximum number of submissions is reached, users will see a notification.
- How to Access: Document > Assessments
- Description: Several enhancements and UI updates have been made to the Assessment Permalink settings, improving visibility and user experience when accessing assessments:
Improvements
- Workflow flags
- Improved the workflow settings to make it easier for users to identify and edit notifications-related workflows
- Corrections
- Various corrections were made to the terminology and translations.
- Ensure the Go pod is always deployed
- This improvement ensures that the web-go pod is deployed automatically every time, alongside other components like the DPMS and workflow pods. It streamlines the process and removes the need for manual deployment control through the portal, which increases reliability and consistency. The Helm configuration will be updated to reflect this change.
- Filerkeeper Responses Update
- Filerkeeper is changing the retention and period values, effective March 7, 2025. The previous "0 Days" retention periods will be replaced with more precise, standardized values:
- Retention values:
unspecified
,indefinite
,permanent
. - The Period value can now be left empty.
- Retention values:
- Filerkeeper is changing the retention and period values, effective March 7, 2025. The previous "0 Days" retention periods will be replaced with more precise, standardized values:
- UI update for periods
- Users now have a toggle (switch) to choose between two types of definitions in the UI—either a Definition (with values like
unspecified
,indefinite
,permanent
) or a Timeframe, which helps set up the retention and period information more clearly.
- Users now have a toggle (switch) to choose between two types of definitions in the UI—either a Definition (with values like
- Update Sort on Logs
- The default sorting for Identity & Access Management logs has been updated. Now, logs will be displayed in descending order, meaning the most recent entries will appear first.
- Simple endpoint for checking changes on elements
- A new lightweight endpoint has been implemented to check if an element has changed.
Bug Fixes
- Issue ID [#3769]: Fixed the white screen issue in the assessment template.
- Issue ID [#3783]: Resolved the Audience and Org Unit permissions error.
- Issue ID [#3801]: Removed unreferenced conditions in the Assessment module.
- Issue ID [#3810]: Corrected the design error in the menu.
- Issue ID [#3837]: Fixed error when filtering data on the asset-linked screen.
- Issue ID [#3857]: Corrected spacing for the Assessment name.
- Issue ID [#3905]: Updated the "Link All Relevant" tags.
- Issue ID [#3906]: Resolved the login assessment permalink and assessment issue.
- Issue ID [#3926]: Migrated bad types from created at and updated at fields.
Known Issues
- No known issues.
Feedback and Support
We value your feedback. If you encounter any issues or have suggestions, please contact our support team:
- Email: hello@priverion.com
- Schedule a Meeting: Via the Help Widget
- Give Feedback with Screenshots: Via the Feedback Button in the Help Widget
- Schedule a Support Call: Here
- Schedule a Technical Support Call: Here