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 - Editor	Site Staff, Sponsor Staff	When site or sponsor staff set an eConsent form to require an unlock code and hand-drawn signature and then export the document as a .DOCX file, the settings requiring an unlock code and hand-drawn signature are now applied when the .DOCX file is re-imported. Previously, the settings weren't applied when the file was re-imported.	MYVC-6345
eConsent - MyVeeva Users	MyVeeva Users	If a MyVeeva user serves as a witness for two or more participants and receives tasks to review eConsent forms for both participants, they now see separate task descriptions for each participant. Previously, multiple tasks to review eConsent forms for more than one participant shared the same task description.	MYVC-8507
eConsent - MyVeeva Users	MyVeeva Users	When a MyVeeva user using the iOS app taps or clicks on a hand-drawn signature block but doesn't drag to draw, a single dot now appears and can be submitted as their signature. Previously, a single tap or click in the signature block didn't create a dot and the user could submit a blank signature.	MYVC-7206
eConsent - MyVeeva Users	MyVeeva Users, Site Staff	When site staff disconnect a sponsor-shared document, remove the hand-drawn signature requirement, and send the document to a subset of the possible signatories, the MyVeeva user is now able to submit their signature. Previously, the MyVeeva user wasn't able to submit their signature and received an error.	MYVC-7105
eConsent - MyVeeva Users	MyVeeva Users	When a MyVeeva user clears their signature or toggles between tap-to-sign and a hand-drawn signature, the Submit button is now disabled. Previously, the user could potentially select Submit before the button disabled and submit a blank signature.	MYVC-7046
eConsent - MyVeeva Users	Site Staff, Sponsor Staff	When site or sponsor staff create an eConsent form that contains a signature block in the eConsent editor, exports the eConsent form as a .DOCX file, and then deletes the signature block from the eConsent editor, the signature block is retained when the .DOCX file is reimported in the eConsent editor. Previously, the signature block re-imported as a table.	MYVC-6276
eConsent - MyVeeva Users	MyVeeva Users	Thumbnail images for videos now display on consent forms if you're using Google Chrome or Apple Safari on an iOS device or Safari on a MacOS device.	MYVC-2460
eConsent - SiteVault Integration	Site Staff, Sponsor Staff	When an eConsent form with at least one question block is upversioned, a new version of the question object is now created and linked to the upversioned form. Previously, a new version of the question object wasn't created when an eConsent form was upversioned, and the question object remained linked to the old version.	MYVC-8183
eConsent - Viewer	MyVeeva Users	When two guardians attempt to answer the same question on the same eConsent form at the same time, the second guardian now receives an error message explaining that the question has already been answered. Previously, the second guardian received a generic error message that didn't explain that the question had already been answered.	MYVC-6513
General UI	MyVeeva Users	When a MyVeeva user times out while entering a valid two-factor authentication code, they will now see a message directing them to refresh the page and try again. Previously, no error would appear and users wouldn't be informed that they timed out.	MYVC-7876