Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Info

Suggested List:

  • iPads or Tablets: 800

  • Large phones: 400

  • Small phones: 320

  • PDF: 800

  • Targeted Languages: 300

When defining the screen width value of different devices, TrialKit uses what is called UIKit sizes (or points), based on pixel mapping used by iOS. You can read more here on that.

...

Language-specific devices can also be targeted, whereby the form will open based on the user's device-level language settings (on the app), or browser language settings (on the web). For example, If a French user has their device settings in the French language, and the study they are doing data entry on has a form targeted to French, the user will see that version of the form. Any data variable queries will also be presented in the device language, but the query text itself in the queries report will be stored in Englishwhatever language edit checks are created in.

To create targeted language forms, continue reading below.

PDF Targeting

Lastly, the device type "PDF" can be used to create paper versions of the electronic forms. This version will never be displayed to end-users. Instead, it's specifically a tool for form builders to create paper CRFs for printing.

...

How to Create Targeted Forms from the Device Dictionary

Now you have a list of targeted After defining your target device sizes and languages that can be used on any study within the hosting account.host:

In the Form Builder, open a form that you would like to target for various screen sizes. Then open the form properties for that form (highlighted below).

Note

Important Point: The form you are opening is referred to as the Parent form. It's best if this form is originally built on the web so that the web version of the form displays well on that platform.

...


In the background, the system will instantaneously re-arrange the form layout to fit the device width being targeted. The new form referred to as a child (targeted) form, that was created can be accessed in the Form Manager screen. It will have the same name as the parent form followed by a number. You will also see a description of the device it's targeted for, based on how you defined devices in the device dictionary.

If a different language was targeted, this process will also use Google’s Translate API to interpret all the text and labels on the form. Further revisions to the translations can be made as needed.

...

Open the child form in the forms list

...

Text labels and text within choice fields can be updated in batch, as applicable when doing form translations for different languages. This is done in the Form Properties.

Testing for language forms

When testing to make sure a targeted language is opening, its important to have your device language or browser language set to the same language which the form(s) have been targeted to. If the system continues opening the parent form, its either because the language doesn’t match the device or the form width can’t be used.

Tip

To display targeted language forms on the web, set the device dictionary width to 300.

Related articles

Filter by label (Content by label)
showLabelsfalse
max5
spacescom.atlassian.confluence.content.render.xhtml.model.resource.identifiers.SpaceResourceIdentifier@275314
showSpacefalse
sorttitle
typepage
labelsconfiguration
cqllabel in ( "study_building" , "form_builder" , "form_design" , "epro" , "econsent" , "ediary" ) and type = "page" and space = "TKSP"labelsconfiguration
Page Properties
hiddentrue

Related issues