The chapter control

Usage

<chapter
  id='id'
  title='title'
  label='label'>
  content
</chapter>

Fields

Field	Description
id	Identifies the control when it is referenced in data-binding queries, reports, and workflow scripts.

Properties

Property	Type	Description
label (read-only)	string	Specifies the text that will be displayed as the label of the control.
title (required)	string	The title of the chapter, rendered above the content of the chapter.

Traits

Trait	Description
validation	A collection of zero or more validation rules (validator elements) that evaluate user input in the control at runtime, and prevent the user from submitting the form if the `cond` of any of the validators evaluates to `false`.
declarations	A collection of zero or more variable declarations (let elements) that can be referenced in solution-wide query expressions.
content	A list of zero or more child controls.

Remarks

A chapter can contain any type and number of controls, including other chapters.

Perhaps counter-intuitively, the chapter control does not define a new scope unless you give it an identifier.

chapterSample.fls.xml

...
<chapter title="Outline">
  <chapter title="Introduction">
    <textview text="Thesis statement"/>
  </chapter>
  <chapter id="chapterZoo"
    title="Body">
    <textview text="Strong argument"/>
    <textview  id="viewLcoo"
      text="Stronger argument"/>
    <textview text="Strongest argument"/>
  </chapter>
</chapter>
<textview label="My personal favorite argument is "
  text='{chapterSample.chapterZoo.viewLcoo.text}'/>
...

Figure 231. The Introduction and Body chapters are nested inside Outline

Sample

chapterSample.fls.xml

...
<chapter title="Optional Questions">
  <radiogroup label="How satisfied are you
                with the examples?"
    choices='{TABLE agreement
                ("absolutely";
                "quite";
                "whatever";
                "not much";
                "meh";
                "not at all")}'
    keyMap='{agreement}'
    textMap='{agreement}'/>
  <textbox label="What would you change
                to make them better?"
    text="" lines="4"/>
  <checkbox text="Yes, please!
                I'd like to subscribe to the newsletter."
    checked='{true}'/>
</chapter>
...

A sample chapter with a number of child elements

Neither the textbox nor the checkbox has an identifier, so a workflow script running in the Mobilengine Cloud would access the submission of the webform above in the format below:

{...
  selectedKey: "quite",
  selectedText: "quite",
  selectedValue: {agreement: "quite"},
...}

See the workflow script reference guide for more details on data type mapping.

Developer Documentation

Controls overview