Skip to content
Release: Australia · Updated: 2026-07-09 · Official documentation · View source

Execution Tracking - Begin (CIs) Flow Action

The Execution Tracking - Begin (CIs) flow action starts the auditing process for a Security Operations Integration flow that operates on configuration items (CIs).

The Execution Tracking - Begin (CIs) flow action can be used with any CI flow to begin recording the progress of the flow in an audit.

Results

Possible results for this flow action are:

ResultDescription
SuccessAn audit record is created.

Input variables

Input variables determine the initial behavior of the flow action.

VariableDescription
capabilityIdSystem identifier of the Integration Capability being executed.
isImplFlag that specifies whether auditing is done for an Integration Capability flow or an Integration Capability implementation flow. Possible values are: - false - denotes auditing on an abstract Integration Capability flow such as Sightings Search. \(default.\) - true - denotes auditing on an Integration Capability implementation flow. For example, Splunk or Elasticsearch.
taskIdSystem identifier for any task associated with the flow.
ciListOne or more Configuration Items \(CI\)s to perform the desired action against in the following format:
["sysId", "sysId"]
or
"sysId"
Used as a flow input.
flowContextIdSystem identifier of the associated flow context record. Supplied by the system.
flowNameName of the flow. Supplied by the system.
parentCapabilityExcutionIdSystem identifier of the audit record that launched the implementation flow. Only required for Integration Capability implementation flows such as Splunk, Elasticsearch.

Output variables

The output variables contain data that can be used in subsequent activities.

VariableDescription
capabilityExecutionIdSystem identifier of the audit record.

The flow process actions include:

Parent Topic:Security Operations Integrations - Get Network Statistics flow