The XUI processor is an application flow on the client side. It is a rich client component to support flow navigation in XUI and data sharing among the navigation pages. Use the following examples to get an overall understanding of the XUI processor.
▪ Use the provided <xuiProcessor> tag to define the XUI processor. The definition is compatible with the previous processor. See the following example:
▪ Use the <xuiProcessor> tag to define the XUI processor which can include the element standing for the state (DSEState or XUIState) in the flow processor. The XUIState is defined by the <xuiState> tag and the XUI processor can display the XUI page defined by the XUIState. See the following example:
▪ The DESProcessor can be added as a subflow in the XUI processor. In the following example, the page defined by the <xuiState> tag is displayed after the subflow finishes.
▪ Use the <executeXuiSubflowAct> tag to define a XUI processor as the subflow. The XUI subflow can be defined in a DESState or a XUIState. However, defining the XUI subflow in a XUIState is not recommended.
In the above figure, when XUI Processor 1 reaches state 3, XUI Processor 2 is called by the <executeXuiSubflowAct> tag. XUI Processor 1 does not proceed with the next state until the subflow finishes. If the subflow is defined in a XUIState, the sub processor is displayed before the XUI page. The following example explains how to define the XUI processor as a subflow with the <executeXuiSubflowAct> tag.
▪ The context of the XUI processor can be accessed by all the XUIs in the processor. In the following example, the context specified with the ID accountQueryCtx can be accessed by case0121.xui and case0122.xui. If you want to make some data be accessed globally, put it as the processor context.
▪ The context of the XUIState can be accessed only by its own XUI file. In the following example, the context specified with the ID accountQueryCtx can be accessed by all pages in the processor. While the context specified with the ID pageContext1 can be accessed only by case0131.xui.
▪ A final page can be defined and displayed at the final stage of the processor. In the following example, the final page is displayed after the state goes to finalOk.
