The trigger event
Using a remote action policy (see How to launch workflows from BMC ProactiveNet), you can define the selector criteria for an event that automatically launches the OS Disk Space Full workflow. From the Events Console, you can also manually select an event, such as one that indicates that a disk space threshold has been breached. For example, you can select a warning such as "Windows File System Used above 90%" to launch the workflow.
The event that triggers the workflow is received in XML format. It contain the following informations:
- Workflow type
- Event class that contains the OS disk space parameter
- Disk space parameter itself
- Fully qualified host name or the IP address of the configuration item which is the source of the event
A BMC PATROL event is shown in the following example :
Sample BMC PATROL event for triggering OS Disk Space Full workflow
<!-- Unique identifier of the incoming BEM event -->
<mc-ueid><![CDATA[BII4Patrol/10.20.88.236/3181/1253455419/8545]]>
</mc-ueid>
<!-- Status of the Event -->
<status><![CDATA[OPEN]]></status>
<!-- Event Class.. The incoming event can be from PATROL, BPM or
PNET -->
<class-name>PATROL_EV</class-name>
<!-- Host where the problem has occured -->
<mc-host><![CDATA[vm-w23-rds148.pune-labs.bmc.com]]></mc-host>
<!-- This slot has gateway entries where event has been
propagated.. used in ibrsd case -->
<mc-propagations><![CDATA[[]]]></mc-propagations>
<!-- Below 4 slots are used to retrieve annotations in case of
the event origin is PATROL. Except HostDown work flow. -->
<p-agent><![CDATA[vm-w23-rds148.pune-labs.bmc.com]]></p-agent>
<p-origin><![CDATA[NT_LOGICAL_DISKS.C:.LDldDiskSpaceUsed]]>
</p-origin>
<mc-object-class><![CDATA[NT_LOGICAL_DISKS]]></mc-object-class>
<mc-incident-time><![CDATA[1253459255]]></mc-incident-time>
<!-- Below 3 slots are related with the remote action that is
performed on the Event in BEM -->
<!-- The user inputs regarding change, incident, remediation
captured from BEM UI -->
<mc-action-args><![CDATA[[true,normal,true,true,bem-user]]]>
</mc-action-args>
<!-- Unique identifier that decides which workflow to invoke
in AO -->
<><![CDATA[Atrium_Orchestrator_Disk_Full_Workflow]]> </>
<!-- This id is used to update the result back into BEM after execution -->
<mc-action-result-id><![CDATA[1]]></mc-action-result-id>
</event>
After extracting the configuration data from the event, the common framework determines the logging level for the workflow, sets the level at normal or detailed, and updates the event information in the Notes dialog box of the BMC ProactiveNet Operations Console accordingly.
Following the framework processing, the OS Disk Space Full workflow checks for an existing incident associated with the event. If none is found, it creates an incident. It also checks for an associated configuration item. If it retrieves the configuration item, it associates the item with the incident. If the trigger event is a BMC PATROL event, the workflow tries to retrieve the PATROL annotation data. The workflow updates the event with any incident-related information.
You can view the updates in the Events Console of the BMC ProactiveNet Operations Console. Access the Notes dialog box in the Details pane of the trigger event. In the example shown in the figure below, an incident has been created by BMC Atrium Orchestrator, indicating that the incoming event does not contain an incident already created by the integration for BMC Remedy Service Desk.
OS Disk Space Full: Notes dialog box with incident Id 
The update also mention that details could retrieve a configuration item to associate with the incident, meaning that the configuration item is found in the BMC Atrium CMDB.
The OS Disk Space Full workflow proceeds to the triage phase.