...
| 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 whatever language edit checks are created in.
...
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 | ||
|---|---|---|
| ||
|