Your suggested change has been received. Thank you.

close

Suggest A Change

https://thales.na.market.dpondemand.io/docs/dpod/services/kmo….

Thales Logo

All

  • All
back

Flow Nodes

Start node

search

Please Note:

Start node

The Start node is the entry point of the flow. It initializes the IO session and defines some core configuration options for the flow execution.

This node is available in: Authentication, Admin, Self Service, API, Consent, Library, Custom, User Defined

The set of available options may depend on the flow category or type in which the node is used.

Authentication — Login flow

Flow - Start Login node

Node configurations

  • Session TTL in seconds: Define the IO flow session time-to-live (TTL) in seconds. Once this time expires, the flow session is no longer valid and the flow session ends. Default: 300.

  • Login page template: Override the default IO login template with your own custom HTML, CSS and JavaScript code. Example: <body> <p>Hello World!</p> </body> You can write directly into the dedicated editor and import/download a file if required. Note: You can always override later the template from the dedicated Override Flow Execution Template node.

  • Head element: Inject head elements into the rendered page in two ways:

    • From a CDN: A JavaScript resource can be loaded from a CDN by choosing a library from the automatically retrieved list.

    • From a Custom Library: A custom element can be defined using the integrated editor, creating a custom <script> element.

    For each loaded element, it is also possible to specify its scope: loaded temporarily (only for the duration of the node) or persisting for the entire flow execution. Example: <script type="text/javascript" src="https://cdnjs.cloudflare.com/.../index.js" /> Note: The integrated editor offers dedicated controls to download or import the code.

  • Script to execute: Allows defining a custom script that executes within the rendered HTML page. The script runs in the browser context when the node is processed and can be used to manipulate the page, interact with loaded libraries, or perform custom client-side logic.

  • Where do you want to retrieve the token from?: Determines where the node should look for an existing authentication token or session. The token can be retrieved either from the browser's local storage or from a cookie. If a valid token is detected, the current authentication session is reused and the node returns the Already Authenticated outcome.

  • Save in the Flow store: Attributes generated or retrieved from the node can be saved into a variable. They can then be reused by other nodes in the flow by referencing them as {{variable.attribute}}. See Common Configurations for details.

Default output node

  • Not Authenticated
  • Already Authenticated
  • Failure

Authentication — Logout flow

Flow - Start Logout node

Node configurations

  • Session TTL
  • Login page template
  • Head element
  • Script to execute
  • Token retrieval
  • Save in Flow store (see above)

Default output node

  • Still Logged
  • Failure

Admin flow

Flow - Start Admin node

Node configurations

  • Session TTL
  • Login page template
  • Head element
  • Script to execute
  • Token retrieval
  • Save in Flow store (see above)

Default output node

  • Authorized
  • Not Authorized
  • Not Authenticated
  • Failure

Node configurations

  • Session TTL
  • Login page template
  • Head element
  • Script to execute (see above)

Default output node

  • Success
  • Failure

Self-service flows

Flow - Start Registration node

Node configurations

  • Session TTL
  • Login page template
  • Head element
  • Script to execute (see above)

Default output node

  • Next
  • Failure

Flow - Start Reset Password node

Node configurations

  • Session TTL
  • Login page template
  • Head element
  • Script to execute (see above)

Default output node

  • Next
  • Failure

Flow - Start Update Password node

Node configurations

  • Session TTL
  • Login page template
  • Head element
  • Script to execute (see above)
  • Token retrieval
  • Save in Flow store

Default output node

  • Not Authenticated
  • Already Authenticated
  • Failure

API flows

Flow - Start Backend node

Node configurations

  • Session TTL
  • Save in Flow store

Default output node

  • Success
  • Failure

Library flows

Flow - Nested Start node

Node configurations

No configurations required. Defines only the start point of the nested library.

Default output node

  • Next
  • Failure

Custom/user defined flows

In the Custom category, the Start node is available as two separate nodes.

Flow - start frontend node

Node configurations

  • Session TTL
  • Login page template
  • Head element
  • Script to execute (see above)

Default output node

  • Success
  • Failure

Flow - start backend node

Node configurations

  • Session TTL
  • Save in Flow store

Default output node

  • Success
  • Failure

On this page