This documentation supports an earlier version of BMC Helix Operations Management.To view the documentation for the latest version, select 23.1 from the Product version picker.

Slot data types

Slot definitions specify the slot types that are acceptable for processing by assigning data types to the slot.

Slot types

The following table lists the supported data types for creating custom slots. 


Slot filter conditions

Each data type supports particular filter conditions. These conditions can be specified while creating event policies. 

The following table lists the filter conditions available for the slot types that are used for the out-of-the-box slots:

Important

For the event selection criteria, Lookup, Unless, or If actions:

  • The slot values that you specify with the Contains operator are not case-sensitive.
  • The slot values that you specify with the Matches and Equals operators are case-sensitive.
    For example:
    In the case of the Contains operator, Message Contains event and Message Contains EVENT are considered as the same values.
    In the case of the Equals or Matches operator, Message Equals event and Message Equals EVENT are considered as two different values.

Enumeration data types

Enumeration (or Enum) data types are related to integral constants that represent special values within a module. 

Slot enumerations specify acceptable values for a particular slot. The following table lists the out-of-the-box enumerations. Out-of-the-box enums cannot be edited or deleted.

Custom enumerations

Define a custom list of values for Enum data type event slots of the out-of-the-box event classes (except the Event base class) and custom classes. Specify custom enumerations in the event selection criteria. Additionally, specify custom enumerations in the If, Enrich, Variable, Function, Lookup, Trigger-if, and Unless actions on the enrichment policy workflow. Use event operators that are supported for out-of-the-box enumerations with custom enumerations for filtering event slots. For more information, see Out-of-the-box event operators.

You can manage custom enumerations by using APIs. For more information, see Managing-custom-enumerations-with-REST-APIs.

For example, you want to select events based on the device or application status. You could define the following custom list of values to indicate the device or application status and use this custom enumeration to process events:

Device status enumeration

ROUTER_STATE = [
      {"value": "UP", "index": 0, "label": "Up"},

      {"value": "DOWN", "index": 1, "label": "Down"},

      {"value": "ADMIN_DOWN", "index": 2, "label": "Administratively Down"}
       ]

Application status enumeration

APPLICATION_STATE= [
      {"value": "UNKNOWN", "index": 0, "label": "Unknown"},

      {"value": "STANDBY", "index": 1, "label": "Standby"},

      {"value": "PAUSED", "index": 2, "label": "Paused"},
  
  {"value": "UNAVAILABLE", "index": 3, "label": "Unavailable"},

      {"value": "STARTED", "index": 4, "label": "Started"},

      {"value": "ACTIVE", "index": 5, "label": "Active"},
  
  {"value": "STOPPED", "index": 6, "label": "Stopped"}
       ]

To use this enumeration as a class attribute while creating event classes. see the POST /events/classes endpoint on the Managing-events-with-REST-APIs page.

To understand a use case for custom enumerations, see Example-Enrich-events-according-to-the-device-status.