Available for production stage at May 11th from 05:40 AM (UTC), 2026 (EU servers)
Watch release highlights video
Summary
This is a minor release containing three fixes.
Bug fixes
When publishing a new eCRF with data integrity, if the new CRF version added an activation rule over an element, it was marked internally as a manually activated element. Although it worked in the vast majority of cases, in rare scenarios it could become an issue if a later change in the CRF rules to activate that same element was introduced, as they would not be recalculated.
In the particular scenario of a CRF with a regular repetition list which contained an ePRO form, any reminders meant to be sent over more than one of these elements were incorrectly identified as the same reminder, and only one of them was sent.
The data integrity step of the publishing process of a new CRF has been moved to a queue after the publication finishes, so it is carried out asynchronously one subject at a time with a blocking feature. It has become a two phase process to enhance and further protect against unexpected concurrent updates of the same record when a new version of the CRF is published. If a record is updated manually whilst the data integrity process is ongoing, the pending migration is always applied before the manual data, to ensure consistency in the changes.