Using Interaction Continue Nodes with Forms

Use interaction nodes and interaction continue nodes to render information on a browser. In ISML templates, you reference in-memory form instances created by form pipelets (as defined by form definitions). Use Interaction Continue nodes to process form actions via action transitions.

Processing form actions requires three elements:

All three components (form definition, transition from interaction continue and template) must use the same name for the action to work (for example, deleteGiftCertificate).

The following snippet from the cart template shows where the template processes the button for the deleteGiftCertificate action.

<button class="textbutton" type="submit" value="${Resource.msg('global.remove','locale',null)}" 

Interaction Continue nodes wait for user input, with the system maintaining the state. Upon user input, the system checks whether an action was fired. If it was, the flow continues with the specific steps related to the action via the appropriate transition. If the user has submitted form data, the system stores the submitted data into the in-memory form instance (created by a pipelet) and performs validation based on the rules in the form definition.

In the cart page, checkout processing depend on the action button clicked by the consumer,. For example, if the consumer clicks the Update Cart link, the system executes the updateCart transition.

Note: All action names are case-sensitive.

Continue with this example: Using Transitions with Forms.

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.