Wiki source code of Das Log

Last modified by Sabrina V. on 2026/08/10 06:15
Show last authors
1 {{aagon.floatingbox/}}
2
3 ​In the log section of the Client Command Editor, you can track and monitor the execution history of client commands. This monitoring is particularly useful when testing the flow of a newly created client command or when investigating the cause of an error in a client command that did not execute successfully.
4
5 The log is divided into the Run Log and variable monitoring.
6
7 {{figure}}
8 [[image:CC Editor_Log.PNG||data-xwiki-image-style-alignment="center"]]
9
10 {{figureCaption}}
11 Log Area
12 {{/figureCaption}}
13 {{/figure}}
14
15
16
17 = Run Log =
18
19 In the first part of the log - the Run Log - every Client Command executed by the loaded Client Command is listed in the order in which it was executed. The log structure thus resembles the script in the Script Area.
20
21 The Run Log appears in this section when you click  [[image:image-20240215163304-1.png||height="22" width="22"]] (Play) in the toolbar of the script area.
22
23 {{aagon.infobox}}
24 The Run Log displays the execution performed by the ACMP Console in the editor, including both the console script and the client script. It is not possible to view the log of an execution from a single client.
25 {{/aagon.infobox}}
26
27 Each command executed within the Client Commands section contains additional, nested commands. These include detailed information about the execution, such as the variables and values used, or precise error descriptions if the command could not be executed successfully.
28
29 {{figure}}
30 [[image:Angaben zur Ausführung.png||data-xwiki-image-style-alignment="center"]]
31
32 {{figureCaption}}
33 Executed command with nested commands
34 {{/figureCaption}}
35 {{/figure}}
36
37 Furthermore, you can track the rows of the executed command in the actual script, the date, start and end times, the runtime, and the result (successfully or unsuccessfully executed) of the respective command.
38
39 = Variable Monitoring =
40
41 Within variable monitoring, you can monitor the values of the variables used during execution, for example, to identify errors.
42
43 It is not possible to view the execution log from a client there. Consequently, some commands may behave differently because, for example, elevated privileges are not available.
44
45 To add a variable for monitoring, right-click in the variable monitoring area and select the //Add Variable// option. A pop-up window containing all variables will open.
46
47 {{figure}}
48 [[image:Variablenüberwachung.png||data-xwiki-image-style-alignment="center"]]
49
50 {{figureCaption}}
51 Variable Monitoring
52 {{/figureCaption}}
53 {{/figure}}
54
55 Select the variable you want to monitor and click //OK//.
56
57 While the script is running, the current value as well as the two prior values are displayed here alongside the variable name and type. This allows you to track a variable precisely and identify errors.
58
59 To exclude a variable from monitoring, right-click the variable you want to exclude and select the //Remove Variable// option.
60
61 = **Managing Log Files** =
62
63 To ensure that log files are saved at all, you can configure each Client Command individually to specify whether a log file should be created for that command.
64
65 This setting can be configured in the [[Client Command Log Options>>doc:ACMP.610.ACMP-Solutions.Desktop Automation.Client Commands.Client Command erstellen.Client Commands neu hinzufügen.Client Command Editor.Menüleiste.Client Command Eigenschaften .WebHome||anchor="HOptions"]] via Project > //Properties > Client Command Specific > Options > Client Command Log Options//.
66
67
68
69 == **Viewing Log Files** ==
70
71 To view the saved log files, you have two different options within the ACMP Console.
72
73 **Option 1:**
74
75 In the //Execution// phase, click the desired Client Command and then click //Show Details// in the lower section.
76
77 {{figure}}
78 [[image:Log Details einsehen_klein.png||data-xwiki-image-style-alignment="center"]]
79
80 {{figureCaption}}
81 Option 1 for viewing log details
82 {{/figureCaption}}
83 {{/figure}}
84
85 The following summary for the Client Command opens:
86
87 {{figure}}
88 [[image:Log Details einsehen_2.png||data-xwiki-image-style-alignment="center"]]
89
90 {{figureCaption}}
91 Log summary
92 {{/figureCaption}}
93 {{/figure}}
94
95 Then click the //View Log// icon to open the Client Command Log Viewer.
96
97 {{figure}}
98 [[image:Client Command Log Viewer.png||data-xwiki-image-style-alignment="center"]]
99
100 {{figureCaption}}
101 Client Command Log Viewer
102 {{/figureCaption}}
103 {{/figure}}
104
105
106
107 **Option 2:**
108
109 Open a client’s Client Details and select //logs// //under Client Commands//.
110
111 Now click the //View Log// icon to open the Client Command Log Viewer.
112
113 {{figure}}
114 [[image:Client Command Logs.png||data-xwiki-image-style-alignment="center"]]
115
116 {{figureCaption}}
117 Option 2 for Viewing Logs
118 {{/figureCaption}}
119 {{/figure}}
120
121
122
123 == **Exporting Log Files** ==
124
125 You also have the option to export log files. There are two options for exporting:
126
127 **Option 1:**
128
129 Open a Client’s Client Details, select the log you want to export, and click ​//Save // [[image:image-20240215165152-2.png]]//Log as File//.
130
131 Then select the storage location and enter a name.
132
133 You will receive an .alf file that you can view with the Client Command Log Viewer. This tool is installed along with the ACMP Console and is located in the Bin directory (e.g., C:\Program Files (x86)\Aagon\ACMP Console\Bin\ClientCommandLogViewer.exe).
134
135 Open the Client Command Log Viewer and add the .alf file via //File > Open Logfile//, or drag and drop the file into the Client Command Log Viewer.
136
137 **Option 2:**
138
139 Right-click to open the context menu of the Client Command Log Viewer. Select the storage location and enter a name.
140
141 You will receive an .alf file that you can view with the Client Command Log Viewer. This tool is installed along with the ACMP Console and is located in the Bin directory (e.g., C:\Program Files (x86)\Aagon\ACMP Console\Bin\ClientCommandLogViewer.exe).
142
143 Open the Client Command Log Viewer and add the .alf file via //File > Open Logfile//, or drag and drop the file into the Client Command Log Viewer.
© Aagon GmbH 2026
Besuchen Sie unsere aagon-Community