inputMapFmt |
The format used to map data from a processor to its
child processor. The toolkit only uses this attribute if the state's type
is subFlow. The HTML flow processor only uses this attribute for the transition
between two HTML states. |
outputMapFmt |
The format used to map the data from a child processor
to its parent. The toolkit only uses this attribute if the state's type is
subFlow. The HTML flow processor only uses this attribute for the transition
between two HTML states. |
context |
The name of the context used for this transition. The
HTML Channel uses the context transiently to validate the data obtained from
a page when the user performs a specific action related to a defined page
transition. The context definition can be in the generic context file or,
if the processor is self-defined, in the file that contains the processor
definition. |
skipValidation |
A boolean that determines whether the toolkit validates
the data contained in the transition context before placing it in the processor
context. The toolkit only checks this attribute if there is a defined transition
context and if the data in the transition context is not typed data. The default
value is false.
If the attribute is true, the toolkit does not copy
the data into the processor context. Instead, it places a reference to the
transition context into the processor context. Before the request handler
passes control to the presentation handler, the toolkit looks for this reference
within the processor context. If the reference exists, the toolkit chains
the transition context to the processor context. The toolkit sets the transition
context as the operation context, which it uses to build the JSP. |
delegate ValAssessment |
A boolean that determines whether the HTML Channel lets
the processor handle the results of validating the data in the transition
context. The default value is false.
The infrastructure keeps the transition
context in the request scope by chaining it to the processor context and assigning
it as the process context. At this point, regardless of the result of the
validation, the toolkit allows the process to keep flowing according to its
definition. The JSP code of the reply page has access to the overall context
including the data of the previous input form so the page can display whatever
information is required by the client. Once the JSP builds the reply page
contents, the toolkit discards the transition context and restores the processor
context as the process context. For an example of how to use this attribute,
see cancelConfirmationState in financialInfoProc.xml in the HTML Sample Application. |