Views node

The Views node is used to define the views that make up the UI of the mobile app. The Views node can have one or more Category nodes and one or more View nodes as children.

Category

You can use Category nodes to organize your views. Each Category node can have one or more View nodes and one or more other Category nodes as children. Each Category node can have these attributes:

Attribute	Description
AccessItem	List of permissions in Access Control that control access to this category. Specify one or more access IDs in a comma-separated list.
Description	Description of the category.
Id	Identifier for the category.
Profiles	List of profiles that have access to the views in this category. Specify one or more profile IDs in a comma-separated list.

View

A View node can be a child of a Category node or of the root Views node. Each view defines a page or part of a page in the mobile app. A View node can have these attributes:

Attribute	Description
AccessItem	List of permissions in Access Control that control access to this view. Specify one or more access IDs in a comma-separated list. Users must be assigned each of the specified permissions to have access to the view.
ActionBar	ID of the view used to show the action bar for this view. The action bar is usually displayed at the top of the view, and includes one or more action buttons.
Id	Unique identifier for the view.
Model	ID of the model that the view uses. The value must match the ID of a model defined under the Models node.
Profiles	List of profiles that have access to this view. Specify one or more profile IDs in a comma-separated list.
TemplateId	ID of the template that defines the view.

Each View node can have two children: Controls and ViewActions.