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/docs/2025.3/Guides/user-guides/user-interfaces/gateway/dev/flow-editor/right-panel/execution-viewer/exceptions-viewer.md
+9-7Lines changed: 9 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,34 +15,34 @@ The Exceptions Viewer shows details of any [exceptions][What is an Exception?] w
In addition to a detailed description of the exception, the exception message may include an `Inner Exception`, which details the exception associated with a previous exception that led to this exception to be raised. Some exceptions may contain multiple, nested layers of `Inner Exception` messages.
18
+
In addition to a detailed description of the exception, the exception may include an Inner Exception, which details a previous exception that led to this exception being raised. Some exceptions may contain multiple, nested Inner Exceptions.
19
19
20
20
The exact format of the Exception Object depends on the exception raised. All Exception Objects have:
21
21
22
-
* Exception Type – Machine readable exception type
23
-
* Message – Human readable exception message.
24
-
25
-
The exception message may also contain a help hyperlink, which links to further information relating to this exception.
22
+
* Exception Type – The type of the exception.
23
+
* Message – The description of the exception.
24
+
* HelpLink - A hyperlink to further information relating to the exception.
26
25
27
26
## Actions
28
27
29
28
### View Exception
30
29
31
-
Select the Exception tab on the Right Panel to view all the exceptions raised while debugging the flow. If the execution is stopped, all the exception messages will be discarded.
30
+
Select the Exception tab on the Right Panel to view all the exceptions raised while debugging the flow. If the [execution][What is an Execution?] is stopped, all the exception messages will be discarded.
32
31
33
32
See the [Exceptions Viewer][Exceptions Viewer tutorial] tutorial for a step-by-step guide.
34
33
35
34
## Remarks
36
35
37
36
### Known Limitations
38
37
39
-
* The text displayed in the Exceptions Viewer cannot be copied to the clipboard to then insert into a text editor.
38
+
* The text displayed in the Exceptions Viewer cannot be copied to the clipboard.
40
39
41
40
## See Also
42
41
43
42
### Related Concepts
44
43
45
44
*[Exceptions][]
45
+
*[Executions][]
46
46
*[Flows][]
47
47
48
48
### Related Tutorials
@@ -54,8 +54,10 @@ See the [Exceptions Viewer][Exceptions Viewer tutorial] tutorial for a step-by-s
Copy file name to clipboardExpand all lines: content/en/docs/2025.3/Guides/user-guides/user-interfaces/gateway/dev/flow-editor/right-panel/execution-viewer/variables-viewer.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,26 +36,23 @@ It is important to note that the Variables Viewer can only display a [JSON][] re
36
36
37
37
### View Variables in Variables List
38
38
39
-
To view the variables that have been assigned a value, including a NULL value, that are currently in scope, simply select the execution of interest and click on the Variables tab on the [Right Panel][].
39
+
To view the variables that have been assigned a value, including a NULL value, that are currently in scope, select the execution in the [Executions Grid][]and click on the Variables tab.
40
40
41
41
Variables that have not been assigned a value or are out of [scope][Variable Scopes] will not be displayed.
42
42
43
43
See the [Variables Viewer][Variables Viewer tutorial] tutorial for a step-by-step guide.
44
44
45
-
### View the Detail of the Value in a Variable
45
+
### View the Detail of a Variable
46
46
47
-
Click on a variable in the Variables List to view the detail of a value, displayed in JSON format, contained in a variable. The detail of collection and complex data types will only the expanded in JSON form in the Variables Details Viewer if the execution is paused.
47
+
Click on a variable in the Variables List to view the variable's name, it's data type, and value displayed in JSON format. The detail of collection and complex data types will only be expanded in JSON format in the Variable Details Viewer if the execution is paused.
48
48
49
49
See the [Variables Viewer][Variables Viewer tutorial] tutorial for a step-by-step guide.
50
50
51
51
## Remarks
52
52
53
53
### Known Limitations
54
54
55
-
* The Variables Details Viewer only display the JSON representation of the selected value.
56
-
* Dictionaries with keys of data types other than String will be displayed as a String value.
57
-
* The methods of objects will not be displayed.
58
-
* The Variables Details Viewer will only show the expanded contents of collection and complex data types when the execution is paused.
55
+
* Variables with a [Dictionary<TKey, TValue>][Dictionary Tkey] data type where TKey is not the [String][] data type will have their keys displayed as the [ToString()][ToString] value for the data type.
59
56
60
57
## See Also
61
58
@@ -72,11 +69,14 @@ See the [Variables Viewer][Variables Viewer tutorial] tutorial for a step-by-ste
Copy file name to clipboardExpand all lines: content/en/docs/2025.3/Guides/user-guides/user-interfaces/gateway/dev/flow-editor/right-panel/settings-editor.md
+11-7Lines changed: 11 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,49 +15,53 @@ The Settings Editor enables the developer to set the values of the [input variab
Each Input variable corresponds to an Expression Editor in the Settings Editor, each of which MUST be set, otherwise an errorwill be raised by the parser when a flow is attempted to be debugged.
18
+
Every input variable has a corresponding [Expression Editor][], each of which MUST be set, otherwise an [error][Messages Grid]will be raised when a flow is attempted to be debugged.
19
19
20
-
If an input variable has been assigned a default value, the value configured in Settings Editor will overwrite the value assigned to the respective input variable. If an input variable's default value is to be used, the default value must be copied into the relevant Expression Editor. Null and typed null values are allowed in the Settings Editor if required.
20
+
If an input variable has been assigned a default value, the value configured in the Settings Editor will overwrite the value. If an input variable's default value is to be used, the default value must be copied into the relevant Expression Editor. Null and typed null values (e.g. `null` and `(Structure)null`) are permitted.
21
21
22
-
When the `Is Input Variable?`property is changed for a variable in the [Variables Grid][], the Settings Editor will show a warning message to update the input variables in the Settings Editor.
22
+
When any of the `Name`, `Is Input Variable?`or `Scope` properties are changed for a variable in the [Variables Grid][], the Settings Editor will show a warning message to update the input variables.
23
23
24
24
## Actions
25
25
26
26
### Make a variable an Input Variable
27
27
28
-
To make a variable an Input Variable, open the Variables Grid (Bottom Panel) by selecting on the Variables tab. Double-click on the Is Input Variable? field of the variable that is to be made an Input Variable, and tick the checkbox that appears in the field.
28
+
To make a variable an input variable, open the [Variables Grid][]by selecting on the Variables tab. Double-click on the `Is Input Variable?` property of the variable that is to be made an input variable, and tick the checkbox that appears in the field.
29
29
30
30
See the [Settings Editor][Settings Editor tutorial] tutorial for a step-by-step guide.
31
31
32
32
### Update Input Variables in Settings Editor
33
33
34
-
When a new Input Variable is defined, or an existing Input Variable removed, it is necessary to update the Input Variables in the Settings Editor. To do this, click on the Update Inputs button on the Settings Editor.
34
+
When a new input variable is [defined][], or an existing input variable is renamed, deleted, has it's `Is Input Variable?` changed to false or has it's [scope][Variable Scopes] changed, it is necessary to update the Input Variables in the Settings Editor. To do this, click on the `Update Inputs` button on the Settings Editor.
35
35
36
36
See the [Settings Editor][Settings Editor tutorial] tutorial for a step-by-step guide.
37
37
38
38
## Remarks
39
39
40
40
### Known Limitations
41
41
42
-
* A value must be entered for each Input variable even if that variable has a Default Value assigned.
42
+
* A value must be entered for each input variable even if that variable has a default value assigned.
0 commit comments