Minor changes are by default collapsed in the page history.
No changes
The page does not exist yet.
Failed to load changes
Version by on
Leave Collaboration
Are you sure you want to leave the realtime collaboration and continue editing alone? The changes you save while editing alone will lead to merge conflicts with the changes auto-saved by the realtime editing session.
Action flow tab fields
To view data in the Action flow tab you must set the event_journal configuration parameter to all_actions in the services.cfg file. For more information, see Defining-configuration-options-in-services-cfg.
Feature
Description
Instance ID
Number of the event returned based on the filter criteria you used. It should match Instance from the Instance table. The first ID is 1, the second 2, and so forth
Sequence ID
Identifier assigned to each node in an action flow as each node is executed. If the action instance has multiple actions (for instance, write to a log, execute a program, and journal) each one appears separately in the table when the instance is selected.
ID
ID of the action node in the Monitor Console when defining an action. By default, these have long identifiers like nid256325173715.
Description
Contains the class of the action node, however, if that action was a Journal node, then this column contains whatever text was in the Journal Entry field or the output of the script defined in the Journal node.
Start
Time when the event started. The data is stored in the database as GMT, but the time shown is the local time of the Monitor Console. The time is similar to:
Mon Jul 16, 07 14:15:08.936 CST
Duration
Amount of time (in milliseconds) it took for the action to complete.
End
Time when the event completed.
Result
Result of the action node. Typical results are return code such as 0 or 1, the meaning of which is dependent on the action type. For example, sending an e-mail has different results than logging to a file.
