Skip to main content
All CollectionsWhat's NewRelease Notes2025 Release Notes
Release Notes | Week of March 10 | Apricot 8.27.3
Release Notes | Week of March 10 | Apricot 8.27.3
Updated over a week ago

Overview

This release includes one enhancement to Draft Records and 6 high-priority defect fixes.

Enhancement:

Draft Records | Advanced Access

We've implemented your feedback since the release of "My Draft Records" and the "Draft Manager" tool to extend access to the Draft Manager outside of the Administrator role. To view the previous release notes, click here.

Advanced Access for Draft Manager now grants non-administrative users the ability to easily see and manage drafts associated with any forms the user has access to.

Notes:

  • Advanced Access for Standard Users includes the ability to archive drafts.

  • Advanced Access for Site Admins includes the ability to archive drafts and send notifications to the user(s) who created or modified the draft.

Enable Advanced Access for Draft Manager

Within the User Details page, scroll down to the "Advanced Access" section. Click the + icon to expand the "Record Manager" item and check the "Draft Manager" box to give non-administrators access to the Draft Manager tool.

Defects:

Login | Session Timeout

We resolved an issue where Apricot logged users out before their session should have timed out.

File Uploads | File Types

In accordance with security best practices, Apricot now checks the MIME type of files instead of the file extension.

Sites & Programs | Program Badge

We resolved an issue where clearing the search in the program badge would not show search results to users.

Performance | Masked Field Value Errors

We resolved an issue where integrations involving Masked Field types did not work properly with performance improvements.

Login | Mobile Capability for CAN/ANZ

We resolved an issue with accessing Apricot on mobile devices for users in CAN/ANZ.

Rules & Alerts | Time-Based Alerts

We resolved an issue that prevented email alerts from sending when using the Date field and establishing a “Days Since" rule. Time-based alerts now behave as expected, including triggering the email alert once conditions are met.

Did this answer your question?