You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/en/blog/releases/2024.X/2024.9.md
+4-5Lines changed: 4 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -128,7 +128,7 @@ Affected Components:
128
128
##### Saving Output Properties to multiple variables
129
129
130
130
It is now possible to use the [Expression editor][] for output properties.
131
-
This supports a new [decomposition syntax][decomposition of output properties] allowing saving selected values from an output property to multiple variables.
131
+
This supports a new [decomposition syntax][] allowing saving selected values from an output property to multiple variables.
132
132
TODO - REVIEW DECOMPOSITION LINKS LOCAL AND OUT FROM THIS PAGE
A new [built-in _executionContext variable][] is now exposed in [processes][process] and [activities][activity].
147
147
The `_executionContext` variable contains the initiator of the flow execution, as well as an `Extensions` property that can be used to store additional information.
148
-
TODO - REVIEW LINK TO EXECUTION CONTEXT WHICH SHOULD HAVE SECTION IN
TODO - REVIEW LINK TO EXECUTION CONTEXT WHICH SHOULD HAVE SECTION
151
149
<!-- Flow Engine - Expose Initiator on new _executionContext builtin variable -->
152
150
153
151
Affected Components:
@@ -448,7 +446,7 @@ The [What is a Flow][] documentation has been updated to include information on
448
446
449
447
##### Decomposition of Output properties
450
448
451
-
The [What is a Block Property][] documentation has been updated to include information on the new [Decomposition of Output properties][] feature.
449
+
The [What is a Block Property][] documentation has been updated to include information on the new [Decomposition of Output properties][decomposition syntax] feature.
452
450
<!-- Product Portal - add Decomposition of Output properties to What is a Block Property information page -->
453
451
TODO - REVIEW DECOMPOSITION LINKS LOCAL AND OUT FROM THIS PAGE
[Innovation Only - Single Server - Without HA]: {{< url path="Cortex.GettingStarted.OnPremise.InstallInnovationOnly.SingleServerWithoutHA.MainDoc" version="2024.9" >}}
690
689
[Innovation Only - Multiple Server - With HA]: {{< url path="Cortex.GettingStarted.OnPremise.InstallInnovationOnly.MultipleServerWithHA.MainDoc" version="2024.9" >}}
Copy file name to clipboardExpand all lines: content/en/docs/2024.9/Reference/Concepts/fundamentals/executions/what-is-an-execution.md
+48Lines changed: 48 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -48,6 +48,48 @@ When a [flow][] starts the execution of a child flow using the [Run Flow][] bloc
48
48
| Ended | The execution has ended normally |
49
49
| Error | The execution has ended after having thrown an exception that was not handled |
50
50
51
+
## Execution Context
52
+
53
+
Executions have their own context that contains specific information about the current execution. This can be accessed via the built-in `_executionContext`[variable][] and currently contains the following properties:
54
+
55
+
-[Initiator][]
56
+
-[Extensions][]
57
+
58
+
### Initiator
59
+
60
+
The initiator is a read-only property that contains the following information about the user that initiated the execution:
61
+
62
+
-`Name`: The name of the user that initiated the execution.
63
+
-`AuthenticationType`: The authentication type of the user that initiated the execution.
64
+
-`IsAuthenticated`: A boolean value indicating if the user that initiated the execution is authenticated. This should always be `true`.
65
+
-`Claims`: A list of claims associated with the user that initiated the execution.
66
+
67
+
The values can be accessed using [property expression][] or dictionary [index expressions][] syntax, as follows:
68
+
69
+
```csharp
70
+
($)_executionContext.Initiator.Name
71
+
```
72
+
73
+
```csharp
74
+
($)_executionContext.Initiator["Name"]
75
+
```
76
+
77
+
### Extensions
78
+
79
+
The `Extensions` property can be used to store additional information. This data will be accessible to all blocks within the execution, including child executions.
80
+
81
+
A value can be added to the `Extensions` property using the [expression editor][], using the dictionary [index expressions][] syntax, for example:
82
+
83
+
```csharp
84
+
($)_executionContext.Extensions["key"] ="value";
85
+
```
86
+
87
+
The value can be accessed in the same way, for example:
Copy file name to clipboardExpand all lines: content/en/docs/2024.9/Reference/Concepts/fundamentals/flows/what-is-a-flow.md
+28-32Lines changed: 28 additions & 32 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ weight: 1
9
9
10
10
## Summary
11
11
12
-
A flow is an object in [{{% ctx %}} Studio][CORTEX Studio] that contains the logic and actions (in the form of [blocks][] and [workspaces][]) that is able to be executed on a {{% ctx %}} Innovation platform.
12
+
A flow is an object in [{{% ctx %}} Studio][CORTEX Studio] that contains the logic and actions (in the form of [blocks][] and [workspaces][]) that is able to be executed on a {{% ctx %}} platform.
13
13
14
14
## Anatomy of a Flow
15
15
@@ -24,24 +24,40 @@ Processes are a type of [Flow][] that can contain multiple [Activities][Activity
* Processes only contain a subset of blocks as they are intended to model high-level business processes, not low-level implementation of tasks or actions
31
+
27
32
### Activity
28
33
29
-
Activities are a type of [Flow][] that can be used to model tasks or actions.
34
+
Activities are a type of [Flow][] that can be used to model low-level tasks or actions.
* Activities contain all blocks as they are intended to model low-level tasks or actions
42
+
43
+
## Composition of a Flow
34
44
35
-
Flows are composed of the following blocks:
45
+
Flows are composed of the following:
36
46
47
+
*[Workspace][Workspace ref]
37
48
*[Start Flow block][]
38
49
*[Action blocks][]
39
-
*[Decision block][]
50
+
*[Decision blocks][Decision blocks ref]
40
51
*[Workspace blocks][]
41
52
*[End Flow block][]
42
53
*[Handle Flow Exception block][]
43
-
*[Flow Variable Store][Flow Variable Store ref]
44
-
*[Workspace][Workspace ref]
54
+
55
+
### Workspace
56
+
57
+
The [Top-Level Workspace][] within the flow.
58
+
59
+
* Canvas on which blocks are placed and connected to create the flow logic
60
+
* See [Workspace][workspaces]
45
61
46
62
### Start Flow block
47
63
@@ -62,14 +78,12 @@ Performs a specific action.
62
78
63
79
Causes the [flow execution][] to branch, dependent on a condition.
64
80
65
-
* Icon on block indicates type of condition causing branching
66
81
* See [Decision Blocks][Decision Blocks]
67
82
68
83
### Workspace blocks
69
84
70
85
Contains grouped flow logic.
71
86
72
-
* The turndown on the top-right of the icon indicates it contains a [workspace][], which can be opened by double-clicking the icon
73
87
* See [Workspace][Workspace Block] block
74
88
75
89
### End Flow block
@@ -84,28 +98,9 @@ Ends the [flow execution][].
84
98
Handles [flow level exceptions][], thrown during the [flow execution][].
85
99
86
100
* Automatically created when the flow is created
87
-
* The turndown on the top-right of the icon indicates it contains a [workspace][workspaces], which can be opened by double-clicking the icon
88
101
* Cannot be deleted
89
102
* See [Handle Flow Exception][] block
90
103
91
-
### Flow Variable Store
92
-
93
-
Stores variables that can be used within the flow.
94
-
95
-
* The [Variables Grid][] can be opened by double-clicking the icon, the scope will be set to `Defined (Selected Workspace)`
96
-
* Cannot be deleted
97
-
98
-
{{% alert title="Note" %}}
99
-
This is deprecated in favour of the {{< ahref path="Cortex.Guides.Studio.SouthPanel.VariablesGrid" title="Variables Grid" >}}
100
-
{{% /alert %}}
101
-
102
-
### Workspace
103
-
104
-
The [Top-Level Workspace][] within the flow.
105
-
106
-
* Canvas on which blocks are placed and connected to create the flow logic
107
-
* See [Workspace][workspaces]
108
-
109
104
## Grouping Logic within a Flow
110
105
111
106
All the logic of a flow can exist on the [Top-Level Workspace][], however, this can quickly become difficult to maintain and understand as the numbers of blocks increase. Blocks can be grouped into workspaces in order to reduce the complexity and make the flow easier to maintain.
@@ -120,7 +115,7 @@ A [flow execution][flow execution] may be started by:
120
115
121
116
*[Debugging][] a flow in [{{% ctx %}} Studio][CORTEX Studio]
122
117
* Triggering it by making an HTTP request from an external source (e.g. a web application or web hooks)
123
-
* Triggering it using the [Run Flow][] block
118
+
* Triggering it using the [Run Flow][]and [Run Flow Async][]block
124
119
* Triggering it using predefined events (future) (e.g. on receipt of an email)
125
120
* Scheduling it to execute at predetermined times
126
121
@@ -156,6 +151,7 @@ Currently, it is not possible to have a [Handle Workspace Exception][] block on
0 commit comments