A “maintenance release” is a release that contains fixes for issues that are affecting customers in production environments. We typically communicate 24 hours prior to the release that we will be applying a maintenance release and that there will be a short service disruption. This list only covers fixes to General Release versions.
The list of fixed issues is not finalized until just before the release occurs. When we identify issues to fix in a maintenance release, we attempt to get them into the earliest release possible. Sometimes, we target a specific release but are not able to deliver a fix early enough for full testing. In situations like this, we postpone the fix for a later release and strike out the description in this list.
We number maintenance releases by appending the number of the maintenance release to the General Release number. Vault uses even-numbered releases, while CDMS uses odd-numbered releases. The most recent Vault General Release is 25R1.0, so our maintenance releases for this version are 25R1.0.2, 25R1.0.4, and so on.
Last Updated: Apr 14, 2025
April 15, 2025
Release Number: 25R1.0.8 | Build Number: TBD
This release only affects PDF renditions.
Category | Description | Issue No. |
---|---|---|
Platform: Documents | In some cases, RIM Validation may fail when a PDF file contains at least one filled signature field and at least one empty signature field. | DEV-854465 |
April 14, 2025
Release Number: 25R1.0.10 | Build Number: TBD
Category | Description | Issue No. |
---|---|---|
Clinical Operations | The Self-Evident Corrections feature may show unchanged fields when configured for text fields. | DEV-855758 |
Clinical Operations | Users may experience issues when selecting or searching for users on the Assigned To field because the list is limited to 100 users. | DEV-856865 |
Multichannel | Users may receive errors when attempting to use QR code links pointing to documents. | DEV-856584 |
Platform: Documents | Under certain cases, users may encounter errors or unexpected behavior when creating documents. | DEV-856723 |
Platform: Performance & UI | Users may experience performance issues while using the job scheduler. | DEV-824853 |
Platform: Reporting | An unintended component may be visible in Config and Compare reports. | DEV-856202 |
April 13, 2025
Release Number: 25R1.0.6 | Build Number: 10436
This release contains no customer-facing fixes.
April 10, 2025
Release Number: 25R1.0.4 | Build Number: 10425
This release only affects PDF renditions.
Category | Description | Issue No. |
---|---|---|
Platform: Documents | Users may experience lost data or failure to render in viewable renditions for some Excel files. | DEV-854826 |
Release Number: 25R1.0.2 | Build Number: 10430
Category | Description | Issue No. |
---|---|---|
Clinical Operations | Under certain circumstances, users may be unable to mark a Milestone as Complete via Workflow. | DEV-844795 |
Clinical Operations | Site Users are unable to see if the documents they have sent or received are restricted. | DEV-848563 |
Clinical Operations | Translations may not appear for some parts of SiteConnect. | DEV-852271 |
Commercial | In rare cases, users may experience file collision across different Vaults during InDesign autolinking for concurrent uploads of InDesign zip files with the same name. | DEV-852221 |
Platform: Documents | In some cases, bringing forward an Auto or Approved Link annotation from a previous document version may create a duplicate annotation if the target version contains an identical Auto or Approved Link annotation. | DEV-842519 |
Platform: Documents | The Where Used view displays brought forward Auto Link and Approved Link annotations as Manual. | DEV-846333 |
Platform: Documents | In some cases, Study Export viewable renditions may not include overlays or signature pages. | DEV-848011 |
Platform: Documents | Under certain rare circumstances, file collision during XFA field extraction may lead to the system using incorrect field names to validate signature and overlay templates and filling a signature page template with the incorrect field names. | DEV-849940 |
Platform: Documents | Under certain circumstances, logos may disappear from from document renditions using the Enhanced Overlay Headers/Footers feature. | DEV-850609 |
Platform: Email & Notifications | Under certain circumstances, users may receive a large number of unwanted Favorite Document Notifications. | DEV-853989 |
Platform: Objects | Under certain circumstances, users may receive a Required field missing error on a picklist field with a visible value while attempting to save changes to a record. | DEV-852751 |
Platform: Reporting | Users may see an unintended value in the Configuration Report Component Types. | DEV-850259 |
Platform: Reporting | In some multi-pass reports that return high numbers of columns but also have a report view with List or Distinct List aggregate functions that do not return any records, Vault displays an error message and prevents report generation | DEV-852699 |
Quality | Users without permissions for the latest version of a document may receive an error when linking the document to the Bidirectional Document Relationship panel. | DEV-847856 |
Quality | In some cases, the Upcoming Periodic Review section of the Document Control Homepage may display documents whose Periodic Review Start Date is greater than 90 Days. | DEV-849755 |
Quality | When attempting to copy a source field on a User record to multiple corresponding target fields on a Person record, the Auto-Manage Persons job ends with errors encountered and does not process any additional records when at least one field does not meet copy criteria. | DEV-851512 |
Regulatory | CA Rule I11 may incorrectly fail for the most recent XML files. | DEV-849134 |
Regulatory | In some cases AU Rule 1.1 may report a false positive for 3.2 published submissions. | DEV-850840 |