User Interaction
Last updated
Last updated
The user interaction node is used when there is an interaction with the user. These nodes translate into forms or pages where a wide range of user interaction components can be used (forms, lists, buttons, images, charts, etc.).
The properties are accessed by selecting the node. The properties of the selected node are shown in the properties pane on the right hand side of the screen.
Item | Description |
Name | Enter the name of the user interaction node This name also appears beneath the node on the flowchart canvas. |
Default button exit | This dropdown list shows al defined button exits for this user interaction. When selected, this exit will be used when the user hits the 'enter' anywhere on the page. It is possible that this feature is disabled in the design template. This feature can also be enabled by using the "SetEnterKeyAction" widget. |
Show as overlay | When this checkbox is checked, the user interaction is shown as an overlay. An overlay is a form that resides on top of you application (like a popup). You cannot access the rest of the application without closing the overlay. |
Exits | These are the exits that are triggered by a button in the user interaction form itself (e.g. `Save` or `Cancel`). Whenever a button is added to the interaction node with a "Follow exit" event an exit is added to this list. Another option is adding an exit via the "New button exit" button. Exits added using this method will be visible when a button is dragged to the Template editor canvas. |
Event Flowcharts | This is only visible if the interaction template contains buttons that Execute a flowchart |
The Edit template button at the bottom of the properties form works the same as double-clicking the node: it opens the user interaction template editor.
The editor is where you create the form / interaction that is needed to communicate with users of the application. This editor is also referred to as the "template editor". This template editor has to many features to explain in this chapter. Therefore a seperate section in this documentation is dedicated to the template editor.
