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 | When site staff send an eConsent form to multiple MyVeeva users, the form statuses in SiteVault now say Delivered and the forms can be signed by MyVeeva users as expected. Previously in rare instances, MyVeeva users could sign the form, but the form statuses showed as Processing in SiteVault. | MYVC-11055 |
eConsent - MyVeeva Users | MyVeeva Users, Site Staff, Sponsor Staff | .PDF versions of signed eConsent forms no longer display a null value at the top of the document when site or sponsor staff create an eConsent form template from a Microsoft Word document without editing it or checking it into Vault from the eConsent editor prior to approving it for use. For the best experience, we continue to recommend that users check in or save the version of the form that they intend to approve for use to Vault prior to sending it to participants. | MYVC-9214 |
eConsent - SiteVault Integration | Site Staff, Sponsor Staff | When an eConsent form with a blank Signature Name on a signature block is approved for use, the Signature Name form responses for all signatories now display accurate and unique values in SiteVault and Clinical Vault. Previously, the Signature Name form response values displayed as Signature_1. | MYVC-10349 |
ePRO - ClinOps Integration | MyVeeva Users, Site Staff | When site staff approve an upversioned ePRO collection containing new languages and a MyVeeva user changes their preferred language, surveys that the user received prior to changing their preferred language now reflect their new preferred language as expected. Previously, the surveys continued to reflect their previous preferred language selection if one of their surveys were in progress. | MYVC-8941 |
ePRO - Module | Sponsor Staff | ePRO Audit Trail Data exports for sponsor staff now show accurate datetimes for ePRO collection approved_datetime entries. | MYVC-11247 |
ePRO - Module | Sponsor Staff | Sponsor staff can now successfully generate an ePRO collection overview as expected. Previously in rare instances, generating an ePRO collection overview failed and users were unable to try again. | MYVC-11020 |
ePRO - Patient Surveys | MyVeeva Users | When a survey is due in less than three hours, the exact due datetime is now displayed in a MyVeeva user's tasks. | MYVC-11289 |
ePRO - Patient Surveys | MyVeeva Users | MyVeeva users taking a survey with back-and-next buttons can now proceed after skipping a question, answering the next question, and changing their response to make the skipped question required. Previously, the question after the previously-skipped question displayed an inactive Next button and the user couldn't proceed. | MYVC-10530 |
ePRO - Patient Surveys | MyVeeva Users, Site Staff | When site staff edit the datetime of a participant event which is the start event for an as-needed survey schedule, MyVeeva users now continue to receive the survey as expected. Previously in rare instances, MyVeeva users stopped receiving the survey. | MYVC-10289 |
ePRO - Patient Surveys | MyVeeva Users | MyVeeva users can no longer submit a survey after quickly clearing the last answer and selecting Submit when the last question is a number, date/time/datetime, or text entry question. Previously in rare instances, a user may have been able to submit a survey with an empty final response field if they selected Submit quickly after clearing the field. | MYVC-9669 |
ePRO - Patient Surveys | MyVeeva Users, Site Staff | When site staff select the Enable ePRO action for a participant multiple times in quick succession, they are now successfully enabled with ePRO and their surveys are available as expected. Previously, selecting the Enable ePRO action many times too quickly may have failed to enable the participant with ePRO. | MYVC-13432 |
ePRO - Patient Surveys | MyVeeva Users | Submitted surveys no longer appear in a MyVeeva user's task list in the iOS app. Previously, a user may have seen an already-submitted survey reappear in their tasks after submission. | MYVC-13111 |
ePRO - Patient Surveys | Site Staff, Sponsor Staff | The QSDTCST column in Survey Data exports for sponsor staff and the Start Time column in Survey Data exports for site staff now display the exact datetime at which a MyVeeva user starts a survey. Previously, the columns displayed the datetime at which the MyVeeva servers registered the user starting a survey, which may have differed slightly from the exact datetime. | MYVC-12532 |
ePRO - Patient Surveys | MyVeeva Users | When a MyVeeva user enters the current datetime as a response to a datetime entry question with a maximum value of the current datetime and any amount of time passes, an error saying their response is invalid no longer appears. | MYVC-12135 |
ePRO - Reporting | Site Staff, Sponsor Staff | When sponsor users edit an event's name or sequence in an upversioned ePRO collection, the new event name or sequence value is now reflected in Survey Data exports for site and sponsor users. | MYVC-13890 |
ePRO - Reporting | Sponsor Staff | ePRO Adherence Data exports for sponsor staff now display accurate datetimes in the Database Entry Datetime (UTC) column. Previously, all entries reflected the datetime of the first entry. | MYVC-13478 |
ePRO - Reporting | Sponsor Staff | When sponsor staff export ePRO Audit Trail Data, events relating to languages and translations now include the affected language's locale in the Old Value and New Value columns. | MYVC-12069 |
ePRO - Reporting | Site Staff, Sponsor Staff | Timestamps in ePRO Adherence and Survey Data exports for sponsor and site staff now reflect 24-hour time. Previously, they reflected 12-hour time. | MYVC-12022 |
ePRO - Reporting | Sponsor Staff | ePRO Adherence Data exports for sponsor staff now display Study Number values as they appear in Clinical Vault. Previously, Study Number values reflected the Study Name in SiteVault. | MYVC-11965 |
ePRO - Reporting | Sponsor Staff | When sponsor staff edit an existing survey's JSON configuration while creating a new version of an ePRO collection, ePRO Audit Trail Data exports now only show one audited event for CREATE_SURVEY_TEMPLATE as expected. Previously, the system created audited events for both CREATE_SURVEY_TEMPLATE and UPDATE_SURVEY_TEMPLATE. | MYVC-11489 |
ePRO - Reporting | Sponsor Staff | ePRO Audit Trail Data exports for sponsor staff now include two rows for ADD_EXISTING_TRANSLATION entries, with one entry showing the survey name as it appears in the library and the other showing the survey's patient-facing name. Previously, both entries reflected the survey name as it appeared in the library. | MYVC-10320 |
ePRO - SiteVault Integration | MyVeeva Users, Site Staff, Sponsor Staff | When sponsor staff upversion an ePRO collection to include adding an end event to a survey schedule and site staff have already entered a participant event datetime for the end event in SiteVault, the survey schedule now ends for the MyVeeva user when the upversioned ePRO collection document is approved in SiteVault as expected. Previously, the survey schedule didn't end upon approval of the upversioned ePRO collection document. | MYVC-11509 |
ePRO - SiteVault Integration | Site Staff | When site staff connect a study to ePRO or enable a participant with ePRO and the processing fails before the study or participant record is created in the MyVeeva database, error audit trail entries are now created with unknown values for study or participant as appropriate. Previously, error audit entries failed to be written to the audit trail database. | MYVC-11280 |
General UI | MyVeeva Users | MyVeeva users who log in to the Android app and reset their password after another user logs out now receive a password reset email as expected. Previously in rare instances, the first user who logged out may have received the second user's password reset email. | MYVC-13724 |
General UI | MyVeeva Users | MyVeeva users who change their password in the web app can now use square brackets ([ or ]) to fulfill the special character requirement. Previously, square brackets weren't recognized as special characters. | MYVC-11194 |
General UI | MyVeeva Users | When one MyVeeva user logs into the iOS app after another user logs out, the second user's multifactor authentication code now successfully logs them in as expected. Previously, the second user may have had an error after entering their multifactor authentication code. | MYVC-11440 |
Platform - Authentication | MyVeeva Users | MyVeeva users whose sessions become invalid in the Android app are now logged out and returned to the login screen. Previously in rare instances, the system may not have shown the user their tasks due to an unknown session timeout, instead of logging them out and returning them to the login screen. | MYVC-13354 |
Platform - Notifications | MyVeeva Users | MyVeeva email notifications now display proper HTML styling and expected images when MyVeeva users read them in Microsoft Outlook. Previously, emails may have displayed improper HTML styling and images may have been missing. | MYVC-12477 |