Mobile application

The UNICOM Intelligence architecture is not required when you interact with the interviewer to manage projects and start interviews. However, running interviews requires a basic understanding of UNICOM Intelligence questions and routing.

This is a list of the required steps when you run an interview. Each step includes a reference to the XML that is provided in the example MobileSyncWebService.

2 Parse the Question XML for the specific question and display the question, including simple response validation for the data type and range.

For information about the pages and variables to be displayed to the user, see IPage and IVariable in the MDM Object Model Reference.

The UNICOM Intelligence Data Model provides standard access to all UNICOM Intelligence data types. UNICOM Intelligence Data Model provides an overview and might be useful.

5 Using the associated question data, the component can use the native expression evaluator to evaluate expressions in the logic. When provided an expression, and the associated input data, the expression evaluator returns the expression evaluation results. Your mobile application is not required to parse or evaluate expressions.

System variables lists the system variables. The system variables are provided as part of the Question XML and must be included in the respondent data.

Sample management provides options for managing prospective survey participants. When a projects uses sample management, the sample queue must be checked at the start of the interview. This check ensures that the queue is appropriate, and is updated at the end of an interview. The queue checking and sample record updates are run by a user modifiable sample management script. Mobile application developers must define the sample management checks and updates that are run on the device, or provide a method for configuring the checks. A sample history record must also be generated for each sample interaction.

Sample management describes the sample management facilities and how sample management works.

See SampleData XML for more sample data format information. Sample data is also uploaded as part of the RespondentData XML.

Note Sample management also allows authors to access interview sample fields. This access requires Script items, which are not supported.

Quota defines the number of respondents who have certain characteristics, or a combinations of characteristics, that are required for the project. When quota is defined, each respondent must be checked against the quota before an interview is started. If the respondent meets the quota requirements, the quota cell that is associated with that respondent must be pended when the interview starts. The quota cell is then either rolled back, or completed when the interview completes. As with sample, a quota transaction record is required for each quota change.

Quotas describes the concept of quota as it relates to sample.

Quota control describes how quota works in an interview script. The information can prove is useful. However, checking quota from the interview script requires Script items, which are not supported.

See Quota transformation (Quota XML) for more quota format information. Quota information is also uploaded as part of the RespondentData XML.

The disconnected option does not use templates. The layout template is not applicable in disconnected mode because the template must implement functions that are similar to HTMLPlayer. The mobile application can use the layout template if it requires a method for defining layout related functions.