Table of Contents
| Table of Contents |
|---|
Overview
The TrialKit mobile app takes a clinical trial beyond the computer screen. When building forms and surveys for a study, as a form builder, it's tough to create a form that looks good on the various screen sizes that might view it down the road. After all, one size does not fit all.
...
The steps below outline how to target form layout for multiple devices. These steps only apply to study builders.
Device Dictionary
Ensure you have access to the Device Dictionary within the Host Configuration level role security menu on the app. If you don't see it, contact support@trialkit.com to have it enabled.I
...
2. Setup the Targeted Device sizes or PDFs that will be needed in the study.
...
| Info |
|---|
Suggested List:
|
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 and remains untouched by the more expanded functions the TrialKit builder provides. |
In this step, you are merely taking that parent form and creating a mobile/child form from it , which you will use to make layout and field size changesin order to setup a different layout of the same form.
...
Notice in the form above, it was set with a width of 1400. This is likely because other tabs on the form include content that takes up more width on a screen and is designed to be completed on the website.
...
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
...
Review the layout that was generated by the system, change the layout or item sizes as desired, and save the changes.
| Note |
|---|
Important: Do not add new or delete fields on a child form. If a change must be made to the form variables or logic, make the change on the parent form and then re-create the targeted form so the form variables and behavior match. Form Targeting should only be used to alter the layout of forms for different presentation. |
📲 Share or Open in Web
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) | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
| Page Properties | ||
|---|---|---|
| ||
|