A client state allows the execution of client side operation from a transaction flow. The toolkit comes with an implementation of a client state that allows to show a popup dialog in the client application side (see PopupPage in the Figure below), as well as with an extension mechanism to add any other project level client invocation behaviors (i.e. device control).
The popup dialog appears in front of the page shown previously as part of the flow execution and it can be moved to another position if required.
The following figure provides an example of adding a PopupPage state to a flow:
The popup dialog is implemented as a view and the associated view is set using the Page field. By clicking beside the Page field a page selection dialog lists the available views for selection.
Note When a XUI view need to be re-displayed on top of itself in the pop-up mode, there will be element duplication issues. As a result, the pop-up view cannot be displayed. We recommend designers use different filenames to represent the two pages.
The events defined in the selected view are used by the flow processor to navigate to the next flow state; these events are automatically listed in the Events panel once the view has been selected. The popup dialog has access to the view context data and the flow context data so it can be used to defined the data mappings for transitions; it also inherits any validation (single field or cross fields validations) and ECA rules defined in the view.
beside the Page field a page selection dialog lists the available views for selection. 