Insert excerpt | ||||||||
---|---|---|---|---|---|---|---|---|
|
Live Search | ||||||||
---|---|---|---|---|---|---|---|---|
|
borderColor | #00374F |
---|---|
titleColor | white |
titleBGColor | #00374F |
borderStyle | solid |
title | Sections on this page |
Example
Sometimes there is a threshold in your data that affects the way you want to process it. For example you might want someone to approve orders over £1000, whereas orders below this value can be placed without approval.
In the screenshot below, an application screen lists the orders pending approval.
The actionflow for this requires a gateway node to capture orders with a value of £1000 or more so that it can send these to the person authorised to approve them. todo-sarah Provide screenshot and more details once confirmation and phases have been implemented
forInput Connection Points
This section has a toolbar with standard buttons. The grid contains a list of all input connection points and their type; see 'records will only pass through the output paths if the condition set in the expression is met.
This section has a toolbar with standard buttons. The grid contains a list of output connection points and their expressions.
To add a new output path, in the section toolbar clickThe expression properties has sections for Parent Details , Audit Summary and the following Basic Settings:
Field
Enter an expression which evaluates to true or false to determine if stream-items will pass through this connection point. To work in a larger pop-up window, click .
See also:
For input connection point properties, see Input Connection Points.
Output Connection Points
This section has a toolbar with standard buttons. The grid contains a list of all output connection points.
This section has a toolbar with standard buttons. The grid contains a list of output connection points and their expressions.
To add a new output path, in the section toolbar clickEach output connection point has an expression that specifies the logic to control whether or not records flow to the next action node.
For driving output connections, you can refer to an attribute in the expression using the syntax:
Code Block |
---|
connectionpointname.attributename |
If the expression evaluates to true for the record flowing through the node, it will pass out that connection point onto the next node in the sequence. This can be dependent on if the gateway is marked as exclusive, see below.
Gateways can have an unlimited number of output paths.Output paths process data using expressions; see pages in the topic Expressions and PhixScripts.For links to all pages in this topic, see Understanding Actionflows.