Using Transitions with Forms

The smallest, most often overlooked component used to process browser entry information is the transition from an interaction continue node to the next step. Transitions are a pipeline development tool, and not specific for forms processing. Transitions occur when a pipeline flow calls a CallNode, off which there are one or more paths (transitions) based on what the call node returns.

Transitions off an Interaction Continue node let processing exit a template when the named transition is called by an action.


This example references the form definition name for the action (button) in the transition and in the template that calls it.

In the form definition:
<action formid="apply" valid-form="true" />
In the template:
    	class="image imageright" 
    	value="Edit" src="${URLUtils.staticURL('/images/bttn_apply.gif')}" />
Important: All action names are case-sensitive.
Continue with this example: Form Components Working Together.
X Privacy Update: We use cookies to make interactions with our websites and services easy and meaningful, to better understand how they are used. By continuing to use this site you are giving us your consent to do this. Privacy Policy.