Maintenance releases fix issues that affect customers in production environments. We typically document the release at least twenty-four hours before the deployment. This list documents only fixes to general releases, and the list of fixed issues is not finalized until just before the deployment.
The issues below are now fixed. See the ePRO section on the Known Issues page for page for additional issues that staff and MyVeeva users may encounter.
Last Updated: Oct 4, 2024
October 4, 2024
Release Number: 24R2.0.7
Category |
Description |
Issue No. |
eCOA - Studio |
Sponsor/CRO Staff | Only the latest approved version of surveys are displayed in the Veeva Library. Previously, superceded versions were also displayed to some customers.
|
MYVC-26652 |
September 20, 2024
Release Number: 24R2.0.6
Category |
Description |
Issue No. |
General UI |
MyVeeva Users | Large consent forms function as expected when users minimize the Android app. Previously, the app crashed when a user was viewing a consent form and minimized the app.
|
MYVC-26293 |
September 13, 2024
Release Number: 24R2.0.5
Category |
Description |
Issue No. |
eCOA - Patient Surveys |
Sponsor/CRO Staff | Sponsor/CRO staff can now configure numeric rating scale labels with an empty string to act as a spacer. Spacers will cause other labels to wrap and support specific label width requirements.
|
MYVC-26403 |
eCOA - Studio |
Sponsor/CRO Staff | Sponsor/CRO staff can now start UAT as expected. Previously, complex study builds and repeated UAT rounds were sometimes causing UAT to fail to start.
|
MYVC-25873 |
SiteVault - eConsent |
Site Staff | The In-Person eConsent QR code is generated as expected after site staff confirm eConsent recipients.
|
MYVC-26527 |
MyVeeva for Patients App |
MyVeeva Users | The Enabling Biometrics prompt now displays the expected information on Android devices.
|
MYVC-26063 |
September 6, 2024
Release Number: 24R2.0.4
Category |
Description |
Issue No. |
MyVeeva for Patients App |
MyVeeva Users | Longer placeholder text in number fields is displayed as expected, and users can see and verify the entire entered number when submitting surveys.
|
MYVC-26068 |
MyVeeva for Patients App |
MyVeeva Users | Several small translation-based issues were corrected across web, iOS, and Android apps.
|
MYVC-25459 |
Studio |
Sponsor/CRO Staff | An eCOA collection no longer becomes unviewable when it has moved in and out of UAT many times.
|
MYVC-25812 |
August 23, 2024
Release Number: 24R2.0.3
Category |
Description |
Issue No. |
General UI |
MyVeeva Users | Unsuccessful survey updates and submissions automatically retry as expected.
|
MYVC-25883 |
Platform |
Site Staff | After you activate a study version with a new language on a study that is connected to SiteVault, you can add participants as expected. Previously, you were unable to add participants.
|
MYVC-25822 |
ePRO - Sites |
Site Staff | The audit trail is updated as expected when a participant ID is edited. Previously, three audit entries were added when a participant was edited but only one item was changed.
|
MYVC-25560 |
ePRO - Sites |
MyVeeva Users | The Study tab now loads for a user that is not active in a study. Previously, the tab did not load.
|
MYVC-25387 |
August 16, 2024
Release Number: 24R2.0.2
Category |
Description |
Issue No. |
ePRO - Patient Surveys |
MyVeeva Users | If a survey is canceled while a user is offline and the user submits it, the survey is submitted as expected when they reconnect to the Internet. Previously, the survey was not submitted.
|
MYVC-25826 |
MyVeeva App |
MyVeeva Users | The time of the last update is now tracked correctly to save survey updates on Android devices.
|
MYVC-25788 |
ePRO - Studio |
Sponsor/CRO Staff | In the collection overview document, double number entry fields are displayed as expected for surveys. Previously, only one number entry field was displayed when two were configured.
|
MYVC-25777 |
Platform |
MyVeeva Users | Participants in a different region than the sponsor can view study resource links as expected.
|
MYVC-25739 |
August 12, 2024
Release Number: 24R2.0.1
There are no customer-facing fixes in this release.