Best Practices for Work History Forms
This topic describes some best practices to apply when setting up a Work History-enabled form.
Available on the Elite tier:
Contents
Best practices
- Choose entity types that reflect what the work is centered around and map them to questions that capture unique and stable values.
-
Whether your Work History-enabled workflow is initiated from the Forms folder or from a dispatch in the Inbox or Group Inbox
The Group Inbox on your mobile device is a list of records that were sent to a group or FormSpace. If you're available, you can claim a record to work on from the Group Inbox., ensure form questions mapped to an entity are:-
Available to users.
-
Available to answer: Don't apply the Hidden on Device or Read Only restrictions on questions that users answer manually.
-
Available to troubleshoot: Don't apply the Hidden on Device restriction on auto-populated questions, so users can identify the questions that fail to populate.
-
-
Answered.
-
Apply the Required restriction to ensure every entity has a value.
Note:To reduce user error, entity values should come from controlled sources (such as data sources
Data sources, also known as "Lookups", are external sources of data that you upload or connect to TrueContext. You can reference this data in a form to populate answers or answer options. Data sources save typing, reduce errors, and make it easy to provide mobile users with only the relevant, most current data., barcode scanners, or app-to-app calls); avoid free-text fields where users manually enter values -
-
Not referenced by conditional logic that inadvertently clears their data.
-
Review conditional logic for rules that unintentionally override or reset values or restrictions.
-
Avoid conditional logic that sets sections or pages with a mapped entity
A form question mapped to an entity type, used to match other submissions that share the same answer. to Set to Ignored.
-
-