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 not really part of the Forms Framework, but an element of the broader pipeline creation/usage Framework. Transitions occur when a pipeline flow calls a CallNode, off which there are one or more paths (transitions) based on what the call node returned.

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

Example

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

In form definition:

<action formid="apply" valid-form="true" />

In template:

<input 
	class="image 
	imageright" 
	type="image" 
	name="${pdict.CurrentForms.sendstuff.apply.htmlName}" 
	value="Edit" src="${URLUtils.staticURL('/images/bttn_apply.gif')}" />

Important: All action names are case-sensitive.