Defining the UI Logic 

Purpose

When you define the UI logic of an iView, you select UI elements that enable you to answer questions like the following:

·        What UI elements are presented to the user at runtime?

Example: Should the iView provide a form for the user to enter search parameters and should the output of the search be displayed in a table view or a chart? These UI elements are the Interactors displayed in the Elements task panel.

·         How should the user interact with the UI components?

Example: Should the data displayed in the iView be static, with set components for starting the search, or should the user be able to enter data in order to launch a search for a specific sub-set of data? These components are the Flow Control elements in the Elements task panel.

·         What are the underlying data queries?

Example: How exactly should the information be retrieved from the back-end system, and should the data be manipulated in any way prior to display, for example with a filter or a sort operator? These elements are the Data Operators displayed in the Elements task panel.

To build the UI logic of an iView, you add UI elements and operators to the iView, and specify the flow of information between the iView components.