Known limitations

  • Published by Viedoc System 2024-10-10
  • Print

Viedoc Clinic

CSV export

  • The export to CSV fails if the same OID was used in Viedoc Designer in different design versions with different casing (for example, an OID defined as AE in design version 1 and AE in design version 2).
  • Labels are truncated to 200 characters when CSV data is imported to SAS using the CSV2SAS macro.
  • The Excel/CSV export does not include items set to “Hide Always" in visibility conditions when a single form is selected for export.

Data export

  • The export preview with graph pages results in a JavaScript error on Internet Explorer 8 on some instances.
  • The export preview is not working with Safari running on Windows OS or older Safari versions running on Mac OS X.

Data review

  • Queries of the type “Required value missing” responded with “Confirmed as missing” and cannot be rejected by the sponsor side.
  • A field that is required for SDV but is hidden on a form (due to, for example, visibility conditions) can normally not be marked as having been verified by SDV. Yet, if the entire form is marked as having been verified by SDV, then even hidden fields are included and marked as having been verified by SDV.

Edit/enter data

  • For scheduled and unscheduled events, when the event date form ($EVENT) is excluded when you use automatic event dates, it still counts. In the signing console the counter (number of forms) for a event includes the $EVENT form. It cannot be selected to be signed but can be signed if you select sign all (for subject or event). If you sign forms on an event individually you will not be able to sign the $EVENT form. This in turn makes it so that the sign symbol that appears on the event when everything is signed does not appear, even though it looks like everything is signed.
  • When populating numeric fields using functions and reference data, they automatically receive the number of decimals configured in the design.
  • It is not possible to delete unscheduled events if automatic event dates are enabled.

File upload

  • For security reasons, uploading executable files is not allowed. The complete list of unsupported file types can be found in the Viedoc 4.34 Release Notes.
  • The upload of password-protected zip files is not supported, as Viedoc is not able to scan these files for viruses.

Issues and task

  • The Issue list will not be visible for sites that have more than 1000 subjects.

Medical coding

  • The Medical coding console is not working with Safari running on Windows OS or older Safari versions running on Mac OS X.

Metrics

  • The number of open queries differs between the Queries page and the Performance page. The Performance page also includes queries with the state “Removed”.

PDF export

  • Visit date form history will not be included in PDF export if no forms were filled in, or if forms were initiated from Viedoc Me.
  • When using Windows 7, file names added to the zip archive during PDF export get scrambled when they contain Unicode characters. The extracted file content is not affected by this. There is a Hotfix for Windows 7 available at: https://support.microsoft.com/en-us/kb/2704299 that addresses this issue.
  • PDFs generated upon form save in Viedoc versions prior to 4.51 were generated and stored based on the role visibility conditions applied to the user that last saved the form. Items that were hidden to the user due to role visibility conditions are not shown/included in such generated PDFs.
  • Fully PDF/A compliant archives are only supported if all the included form PDFs and study event PDFs were generated on, or, after 2017-03-10 (Viedoc 4.33). It is still possible to generate PDF/A compliant archives that contain form and study event PDFs generated before this date, but you might receive warning messages related to PDF transparency issues.
  • In the PDF/A export output, the header, footer, and the text on the respective Contents page are missing for the deleted forms/events/subjects.

Selection page

  • The descending sorting in the subject list view is not working properly.
  • When clicking to sort a column containing dates in the subject list view, Viedoc sorts all dates using a numeric variant of US date representation (for example, 1977-NOV-16 comes before 1967-DEC-16 because the first is sorted like 11/16/1977 and the latter is sorted like 12/16/1967).
  • The event overview page is not working with Safari running on Windows OS or older Safari versions running on Mac OS X.

Viedoc Admin

We no longer support SMS notifications in the following countries:

  • +7 Russia
  • +92 Pakistan
  • +994 Azerbaijan
  • +967 Yemen

Apply revision

  • The affected forms count shown in Viedoc Admin while applying a study design revision is implemented only for production sites. Demo/Training site forms are not included in this count.

Data import

  • It is only possible to import values (choice numbers), not strings (choice labels), when importing data into data fields where multiple checkboxes can be checked.

ODM import/export

  • It is not possible to import an ODM file that was exported from Viedoc including the Event Dates into Viedoc Admin. The following error message is displayed: “An item with the same key has already been added”.
  • Only one (selected) design can be imported from each CDISC ODM file.
  • ODM export fails when subject data contains large, uploaded files.

User management

  • Any of the Organization Administrator, Organization Designer, and Site Manager roles that were removed from a user are not listed in Viedoc Admin, under User Settings > Studies and Roles.
  • When sorting studies by group and generating a “User and Roles” or “User Administration Log” report, the Download link is not exposed for the newly generated file until the page is refreshed.
  • API configuration: After creating new and editing existing Web API clients, it is not possible to save the setup unless the user system language is set to English or German.

Viedoc Designer

Alerts

  • If the condition for an alert is set within a form for which the option to auto-update functions is enabled, and the alert is triggered, the alert message will be sent twice.

Edit checks

  • Edit checks are not triggered on dates when the event date is used as default value, and the calendar picker is used to choose the date.
  • Using $THIS inside a form to refer to an item within a different instance of the same form, does not work, as it always refers to the same form instance. This is true when referring to an item in the same form within another activity, or when referring to another form instance within the same activity (applicable for repeating forms).
  • If two scheduled events have the same event date, and both events contain a form with a function or data check that uses the $PREV function, the $PREV functions in these two events refer to each other as the previous event, and not to the event that occurred earlier in the study workflow. This creates a circular reference and makes it impossible to refer to earlier event(s).

Form and workflow PDF

  • If, in the Study Workflow, there are more activities with the same activity name within the same event, then the forms in these activities are incorrectly displayed in the Bookmarks list in the study workflow PDF. Please note that only the Bookmarks list is affected, the events/activities/forms are correctly displayed within the document.
  • The PDFs generated as Empty CRFs will not display all code list items for radio buttons, drop-down lists and checkboxes if these have been configured with many code list items in a vertical layout.

Item settings

  • For the code list items (checkboxes, radio buttons, dropdown), it is possible to set the same code list values for multiple choices within the same item. This is not recommended. Unique code list values should be used for each of the choices within the same item.

JavaScript

  • The setMonth function with negative values is not supported. The date is not saved into the system correctly when the function is run on the server-side.

Roles and permissions

  • If the role that has the permission for Emergency unblinding also has a role visibility condition that makes the blinded outcome hidden for this role, the outcome gets hidden for all roles after unblinding, and not just for the role specified in Viedoc Designer.

Study workflow

  • When the Event ID for the Study Start event contains the word “START”, including combinations with other words and punctuation, and scheduling other events based on the Study Start event, this results in an error. The workaround is to use a different ID for the Study Start event, one that doesn’t contain the word “START”.

Validation of study design

  • Validation of alerts, selection view settings, event visibility, subject status condition, common event summary format and subject ID generation settings for deleted items is not performed.

Visibility conditions

  • When creating forms for Viedoc Me, visibility conditions can only include variables that have already been introduced, and that are in the same form and on the same page. This behavior differs from the one in forms for Viedoc Clinic.

Design configuration report

  • When using Chinese or Japanese characters to label sites in Designer, the name of the design configuration file report will display an incorrect string of text.

Viedoc API

  • The API method SubmitData allows submitting data into a form that exists in the effective design but does not exist within the respective event according to the study workflow. In such a case, a new form is created and added to the event.
  • When using the WCF API to push data into forms, if there are items that have functions setup to calculate data from other items, or item groups, those calculations will not be automatically updated. However, if an item that relies on a function is added to the same item group it relies on, it will perform the calculation.

Viedoc Me

  • In the UI-optimized version of Viedoc Me, when a simple visibility condition has been set to make a form item show depending on the selection of a radio button, and a subject selects the radio button, an error message is displayed.
  • If additional languages are imported (to be used in Viedoc Me) and after that code lists are combined via “Formats” (for example for SAS export) then the imported languages are lost. The workaround is to import the languages again after the code lists have been combined.
  • For Viedoc Me translations, if any of the translated values in the file to be imported is a number, the file import fails without prompting any feedback to the end user. The workaround is to remove the numbers from the columns in the translated file that correspond to the translated content before importing the file in Viedoc Designer (the numeric values will be kept in the original English version and will be displayed as such in the translated Viedoc Me form).
  • The drawing pad item is not working on IE 11. For Safari it only works on Safari 12+ versions.
  • Viedoc Me does not support forms with form link items.
  • The PDF export containing form PDFs submitted from the new Viedoc Me application in Japanese Kanji will not be generated correctly if embedded fonts are included.
  • Long option labels for radio buttons and check boxes do not have line breaks.

Viedoc Logistics

  • In the exported stock list, the audit trail shows one row for the create action for older kits. For more recently uploaded kits, the audit trail shows two rows for the create action.

Viedoc Reports

  • There are some graphical limitations of the interface on mobile devices.
  • Variables/fields that have an output field ID defined will be identified with this ID in the Data Browser and Reports pages, whereas they will be identified with field ID in the Dashboard, Demographics, and AE pages.
  • The Overdue Events Report does not include any Viedoc Me events. Events without a proposed date are not included in this report. Events that have been planned or initiated are not included in this report, even if the planned/initiated event is outside of the event window.

Viedoc TMF

  • Viedoc TMF is only running in Production mode.
  • For security reasons, the document preview in the Trial Master File view does not support ActiveX components.
  • The search for document content is disabled on the training server.
  • Viedoc TMF does not work on Safari 16.3 and later.