These Nodes perform internal application functions, controlling the user interface, navigation, and application data storage.

Simple Navigation and App Control

These Nodes execute straightforward user experience actions and control global application information.

• Navigate: Used to transition the application to a specified route, initiating a new application state.
• Back: Used to return the application to the immediately previous screen or route in the history stack.
• Set Metadata: Used to dynamically set arbitrary metadata for the current page in Web applications. This typically involves setting <meta> tags for SEO purposes.
• Set Title: Used to dynamically set the user-facing title of the current page or screen, such as the text that appears in a browser tab or window.

UI Control and State Persistence

These Nodes control overlays and manage data that needs to be persisted on the user's device or browser.

• Open Overlay: Opens a UI overlay within the application that renders a specified Layout.
• Update Overlay Data: Updates the data within an overlay on the user’s screen, provided an overlay ID.
• Close Overlay: Closes all open overlays on the user’s screen.
• Set State: Stores string data on the user’s device or browser.
• Get State: Retrieves information previously stored with the Set State action.

Open Overlay

This Node opens a UI overlay. You can pass data from the Flow into the Layout via the Overlay Data property.

• Unique ID: You can optionally provide the overlay with a unique ID to update the data once the overlay has already been opened.
• Behaviors: You can choose between three different behaviors for your overlay: Absolute, Anchor, or Modal.

Set State

This Node stores string data that can later be retrieved using the Get State Node. You must provide an arbitrary key and the value you wish to set.

Storage Types:

• Temporary: The data is stored in memory and will be lost when the user closes the application or PWA.
• Persistent: The data will not be encrypted and will be permanently stored on the user’s device.
• Secure (Native Only): The data will be encrypted and permanently stored on the user’s device.

💡💡💡 Tip 💡💡💡

For a Native application, it is best practice to store sensitive data (e.g., passwords) using Secure storage and other data using Persistent storage.

• Secure Storage Strategy (iOS Only): If you choose Secure storage, you must select a strategy for how the value is unlocked and synced across devices:
• • When Unlocked (Default): The value can be accessed when the device is unlocked.
  • When Unlocked This Device Only: Same as above, but the value will not be migrated to new devices using a backup.
  • When Passcode Set This Device Only: Same as the above, with the additional requirement that the user needs a passcode set.
  • After First Unlock: The value can be accessed while the device is locked, but only after the user has unlocked it at least once after restarting.
  • After First Unlock This Device Only: Same as above, except the value will not be migrated to new devices using a backup.
  • Always: The value is always available, even if the user has not unlocked the device.
  • Always This Device Only: Same as above, except the value will not be migrated to new devices using a backup.

Get State

This Node retrieves information that your application has stored on the user’s device or browser. You must provide the same key that was used in Set State and specify whether the data is in Temporary, Persistent, or Secure storage.