| eConsent - Editor |
The spacing and margins of .PDF versions of eConsent forms recently changed. Template .PDF versions and signed .PDF versions of eConsent forms may now have different page counts than they did previously. |
None |
To be determined |
MYVC-9829 |
| eConsent - Editor |
When you copy and paste a bulleted or numbered list from Microsoft Word into the Veeva eConsent editor, the indentation of the list items is not retained. |
Either import the Microsoft Word document or manually add the indentation in the editor. |
To be determined |
MYVC-2508 |
| eConsent - Editor |
Dragging and dropping a content block a long distance in a section or between sections can cause the content in the current section to be reordered. |
Select the up or down arrows to move the block up or down in the Content Blocks list. |
To be determined |
MYVC-2934 |
| eConsent - Editor |
You cannot import .DOCX files to the Veeva eConsent editor if the file contains more than 4MB of media content. |
None |
To be determined |
MYVC-4483 |
| eConsent - MyVeeva Users |
In rare instances when the SiteVault system goes down soon after site staff send an eConsent form to a participant, form response records aren't created for the participant. |
When the SiteVault system comes back up, users can cancel and resend the eConsent form. The expected form responses are created, and they can continue consenting the participant. |
After 23R1.0 |
MYVC-13577 |
| eConsent - MyVeeva Users |
When site staff create an eConsent form template from a Microsoft Word document, approve it for use without editing it in the editor, and immediately send it to a MyVeeva user, the sent document shows an Error status. If site staff cancel the document while it's in an Error status, MyVeeva users can still sign and submit it. |
Users should edit the eConsent form template in the eConsent editor and check in the version they intend to approve to Vault prior to sending it to MyVeeva users. |
To be determined |
MYVC-9332 |
| eConsent - MyVeeva Users |
MyVeeva users can sign and submit consent forms that may not be the latest version if site staff update the consent form while they are reviewing it. |
Site staff should check for users that signed a document shortly after they approved an updated version of a consent form. If any users signed the old form, recomplete the consent process with them as needed. |
To be determined |
MYVC-4784 |
| eConsent - SiteVault Integration |
When you update the study that an informed consent form is associated with, the incorrect document name is displayed in the title bar of the preview opened from the Veeva eConsent editor or SiteVault. |
The incorrect name is not displayed to patients in the MyVeeva for Patients application. |
To be determined |
MYVC-3038 |
| eConsent - Viewer |
When sponsor or site staff create an eConsent form template from a Microsoft Word document that contains images or videos in question or signature blocks and approve it for use without editing the form in the editor, MyVeeva users can't download a .PDF version of the unsigned form. |
Users should edit the eConsent form template in the eConsent editor and check in the version they intend to approve to Vault prior to sending it to MyVeeva users. |
To be determined |
MYVC-9258 |
| eConsent - Viewer |
When site or sponsor staff create an eConsent form template from a Microsoft Word document but don't edit it or check it in to Vault from the eConsent editor prior to approving it for use, PDF versions of the signed form don't display proper HTML styling or section and heading numbering. |
Users should edit the eConsent form template and check in the version they intend to approve to Vault from the eConsent editor prior to approving it for use and sending it to participants. |
To be determined |
MYVC-11436 |
| ePRO - Module |
Sponsor users can't perform UAT more than once on the same sandbox SiteVault study for the same ePRO collection version. |
Sponsor users must create a new study in their sandbox SiteVault environment each time they perform UAT. |
To be determined |
MYVC-12796 |
| ePRO - Patient Surveys |
When a MyVeeva user is answering a date or datetime entry question in Firefox, two calendar icons display in the date field, but only one is functional. |
Users can select the orange calendar icon to enter a date. |
To be determined |
MYVC-12441 |
| ePRO - Patient Surveys |
When a MyVeeva user submits an as-needed survey in the iOS and Android apps, the survey doesn't immediately appear to be available again in their tasks. |
Swipe down on the tasks page to refresh. The as-needed survey appears as available. |
23R2.0 |
MYVC-8454 |
| Platform - Authentication |
When a MyVeeva user enters an unregistered email address on the Global Recover Account page (https://patients.myveeva.com/forgotpassword), they encounter an error and the request is unsuccessful. |
Users should recover their account on the Recover Account page specific to their region (https://patients-us.myveeva.com/forgot-password for United States, https://patients-eu.myveeva.com/forgot-password for Europe, and https://patients-ap.myveeva.com/forgot-password for Asia-Pacific) and confirm that they enter their email address correctly. |
To be determined |
MYVC-8360 |
| Platform - Notifications |
The system groups all urgent Android and iOS app push notifications (such as about several surveys coming due soon) together in a MyVeeva user's device notification center instead of displaying each urgent notification by itself. |
None |
After 23R1.0 |
MYVC-13156 |
| Platform - Notifications |
When a MyVeeva user receives a Survey Available notification and completes the related survey in the Android app, the count indicator on their notification bell doesn't update to remove the notification. |
Users can open their notification bell to automatically clear the notification and update the count indicator. |
To be determined |
MYVC-10997 |