The SequencING widget is available with SmartServer 2.8 and higher.
...
The Sequencing widget is shown in the figure below (the part that appears within the red, dashed box is the Node-RED workspace). Click the Expand button ( 
) to view this widget.
– opens / closes the sidebar with the flow menu and allows you to refresh the flow list- DASHBOARD / FLOW toggle
– opens the Sequencing widget view in a Node-RED browser
...
- Broker – path to the IAP message broker
- QoS – Quality of Service. Valid values are: 0, 1, 2
- Output – valid values are: auto, buffer, utf8, json, base64
- Name – name of the node
- Throttle – time interval in seconds specifying the minimum time between updates to the specified output datapoints, with a default of 300 seconds.
- Fixed – fixed if checkbox is enabled; otherwise, relative (see Setting Fixed and Relative Nodes for more information).
- Filters – set one or more filters to the unfiltered datapoint list to refine it to a smaller, more management list as needed. Filters can be set by:
- Protocol
- Device type
- Datapoint type
- Block name
- Block index
- Datapoint name
- Device name – available only for the fixed datapoint option
- Context type – valid values include campus, building, floor, room, or area (available only for the fixed datapoint option)
- Context – fully qualified path (available only for the fixed datapoint option)
- Selected Datapoints – lists the selected datapoint for the IAP Output node; device type datapoints for relative and device datapoints for fixed; appearing in the format: /<hostname>/<protocol>/<device_handle>/<block_name>/<block_index>/<datapoint_name> (shown below).
Datapoints – unfiltered list of all the datapoints, sorted alpha-numerically by context/device/datapoint name; device type datapoints for relative and device datapoints for fixed; appearing in the format: /<block_name>/<block_index>/<datapoint_name> (shown below).
Note Note: When a fixed node is selected, the datapoint path is exact, with reference to the device that the datapoint belongs to. When a relative node is selected, the datapoint path is for the device type rather than the actual device. 
To set the datapoint priority for the IAP-Output node, which may be needed for BACnet devices, you will need to add the priority parameter to the Node-RED msg.payload that you send to the IAP-Output node. The following figure shows an example of setting the datapoint priority using a Node-RED function node.
Function node code shows setting write priority to 15.
...
| Info | ||
|---|---|---|
| ||
If the fixed option is enabled, a more robust list of datapoints will be displayed on the IAP Input/Output node view since the list is generated for each device. If the relative option is enabled, a narrower list of datapoints will be displayed on the IAP Input/Output node view since the list is generated for each device type. |
Click Done to save any IAP Input or Output node settings that you make.
...
| Info | ||
|---|---|---|
| ||
If you import a flow from another system, or if you import a flow from same system that was restarted and rebuilt with a new database, then you need to re-assign the datapoints on the IAP Input/Output nodes that appear on the flow. |
To use these features, click the Node-RED button (
).
...