Execute Flow

Description

An Execute Flow Node is used to execute another Flow right away.

After the target Flow finished executing, the main Flow will continue executing.

๐Ÿ“˜

Shared Context

The executed flow will receive the current Context of the executing Flow and can write to it. The changes will be available to the executing Flow after the executed Flow finished.

Node Fields

Use Flow Parent ID


This option allows you to specify the target Flow by its flowParentId, which can be found in the input object (ci) during processing of the relevant flow. By storing and using flow parent IDs in variables, you can achieve dynamic behaviours with Execute & Switch Flows, for special purposes.

Note that the flowParentId refers to the Flow as a whole, not any specific version.

Flow & Version


Here you can select the target Flow and its version which is executed whenever the Flow execution hits the executeFlow node

โ—๏ธ

Linking to the "latest" version

It is not recommended to link to the "latest" version of Flows in production setups, as each incoming message will result in the Flow being loaded anew from the database. Only use during development, testing or in low-volume scenarios.

๐Ÿ“˜

Open Target Flow

By clicking on the icon to the right of the Flow drop-down you can open the target Flow. Make sure to save your Node first!

Parse Intents


This toggle decides whether we should parse intents within the sub Flow.

:paperclip: Example Flows

This .zip file contains two Flows: a parent Flow which executes a child Flow via executeFlow node. The parent flow has an intent called parentIntent with the example sentence: parent intent.

The .zip file can be imported by using our Import/Export Tool.

Parse Keyphrases


This toggle decides whether we should find keyphrases within the sub Flow.

:paperclip: Example Flows

This .zip file contains two Flows and a Lexicon: a parent Flow which has an attached Lexicon and a child Flow. The Lexicon has just one keyphrase: parentKeyphrase.

The .zip file can be imported by using our Import/Export Tool.

Absorb Context


This toggle decides whether the default Flow Context of the sub Flow should be applied to the current Context. So if your sub Flow has a value within its default Context, the value will be copied into the current Context as soon as you enter the child Flow.

:paperclip: Example Flows

This .zip file contains two Flows: a parent Flow with a default context and a child Flow.

The .zip file can be imported by using our Import/Export Tool.

๐Ÿšง

Attached Flow

Intents of attached Flows are not executed when the Flow is attached to the child Flow.

๐Ÿšง

Loops

Cognigy.AI checks how often an Execute Flow Node was hit without a user input inbetween. The default setting for maximum loops is 4, but it is configurable for on-premise installations.

โ—๏ธ

Language

Cognigy.AI did enforce that your current mainFlow and the flow you want to execute were in the same language. We removed this check in order to make the system more flexible! Executing flows in different languages is especially useful for flows which do not depend on ML based intent mapping.


Did this page help you?