Updated on 9/27/2019
Service Designer User's Guide
Navigation Node
Direct link to topic in this publication:

Navigation Node

A Navigation node is used when you want to navigate the user to a specified path. To choose the path for navigation, you should first configure how the user should navigate from one page to another within the app by using the Routes tab

How to Use

  • Open the Services editor window.
  • Click the Add Service button to add a new service or open an existing service.
  • From the Nodes Palette, drag and drop a Navigation node to the service designer.
  • Drag and drop other nodes to create a flow.

Associated Attributes

Navigation node properties
  • Name: A unique name for the node. This field accepts only string values of length 5 - 50 characters.
  • Path to Navigate: A drop-down list that shows the paths configured in the Routes tab of the Studio application page. See Add Routes to learn more. To assign a path, you can either:
    • Select a path from the drop-down list
    • Add a string value or map the path to the bh.input or bh.local variables that you created in the Start node.
If you make any changes to paths in the Routes tab, you can use the Fetch button to fetch the latest changes.
  • Path parameters: This field appears only if the path selected has path parameters associated with them.
    Path parameters are variable parts of a URL path. They are typically used to point to a specific resource within a collection, such as a user identified by ID. A URL can have several path parameters, each starting with a colon (:). For example, in 
    /users/:id, :id is the path parameter.

    You can assign a string value, or bh.input or bh.local variables for each path parameter, or you can map the whole path parameters property to any of the bh.input or bh.local properties.
  • Query parameters: Query parameters are the key-value pairs that you send in the URL string. They appear at the end of the request URL after a question mark (?), with different key=value pairs separated by ampersands (&). Example:

     GET /info?offset=100&limit=50.

    Query parameters can also be mapped to bh.local or bh.input parameters.

  • Result mapping: This property can be mapped to the bh.input or bh.local properties. It indicates the result of the navigation to the specified URL. The result is true if the selected path was navigated successfully. Else, it is false

Storage Node                                                                                                                  Service Variables Node  >