Release Notes

See what's new and coming soon, known and fixed issues, and release archive

MyVeeva for Patients Fixed Issues in 23R3

Release Date: December 01, 2023

The issues below that affected previous versions or the pre-release are now fixed in this general release. See the MyVeeva for Patients Known Issues page for additional issues that staff and MyVeeva users may encounter.

Component Users Description Issue
eConsent - SiteVault Integration Site Staff A site staff user is able to view a global preview that has several images or videos. MYVC-17501
ePRO - Patient Surveys Site Staff, Sponsor Staff, MyVeeva Users Optional answers are displayed as expected when a site or sponsor staff member adds a paragraph tag when using the JSON editor in MyVeeva Studio. Previously, text in paragraph tags was indented when it was displayed in a web browser. MYVC-16238
ePRO - Reporting Site Staff A study participant's ID is displayed as expected in the Item Data column of the site's audit trail data export for several audit actions. Previously, a participant's unique MyVeeva ID was displayed instead. MYVC-15943
ePRO - Reporting Site Staff The Vault ID is now included in the audit trail data export for patient survey question responses. MYVC-15942
ePRO - Site Surveys Site Staff Site staff can now view the list of surveys for an event as expected when that event only includes an as needed survey that is scheduled in the future. Previously, the status was changed to Pending and the user was unable load the list of surveys for an event in Study Connect. MYVC-17181
General UI MyVeeva Users If a MyVeeva user (User A) is logged in on an open tab in a browser session, and a different MyVeeva user (User B) opens an email notification link in the same browser session, User B has to log in to be able to view the notification. Previously, User B was able to open the tab that User A was viewing and access User A's account page until the page was refreshed. MYVC-17263
General UI MyVeeva Users The timed break between login attempts is functioning as expected on Samsung Galaxy S21 devices. Previously, when a MyVeeva user entered an incorrect personal identification number (PIN) five times, they were unable to attempt to log in again after waiting for ten minutes. MYVC-16069
Platform - Authentication MyVeeva Users When a MyVeeva user (User A) is set up to use biometrics on an Android device, and then another user (User B) uses a PIN to log in on the same device, User A has to set up the biometrics again the next time they log in. Previously, the app re-registered the biometric use for User A. MYVC-15512
Feedback