Skip to main content

Attribute Checker Configuration

Used by the checkAttributes action to verify the existence and content of a related group of attributes.

An attribute group consists of attributes that are validated together. If any attribute within the group fails validation, the checkAttributes action returns a failed condition.

Attribute Group Configuration

Each attribute group should contain the following:

  • Name: Unique name of the attribute group. Referenced by the checkAttributes function.

  • Attributes: One or more attribute definitions, each containing:

    • Attribute: Name of the CEvent attribute.

    • Match Expression: Optional expression used to validate the attribute value.

    • Default Value: Optional value applied if the attribute is missing or fails validation.

Processing Logic

The checkAttributes function should process each attribute in the group using the following logic:

  • If the attribute exists, the action returns Pass.

  • If the attribute does not exist, the action returns Fail.

  • If the attribute does not exist and a default value is provided, the attribute value is set to the default value and the action returns Pass.

  • If the attribute exists and matches the regular expression, the action returns Pass.

  • If the attribute exists but does not match the regular expression, the action returns Fail.

  • If the attribute exists but does not match the regular expression, and a default value is provided, the attribute value is set to the default value and the action returns Pass.

  • If all attributes in the group pass their checks, any default value updates are applied in a single operation before the action returns.

Return Value

The checkAttributes function returns an inverted result:

  • Return true if any check fails.

  • Return false if all checks are successful.

This behavior allows a subsequent action in the same workflow to run when a check fails and enables the workflow to skip the remaining actions when all checks pass.

Forwarding Behavior

Configure the forwarding behavior as follows:

  • Stop this workflow: On a false return value (all checks pass), stop processing the remainder of the workflow and proceed to the next workflow in the engine.

Match Expression Types

The match expression should support the following four syntax types:

  • Equality expression: A string that performs a case-insensitive equality match.

  • Positive regular expression: A string that starts and ends with /, using standard JavaScript regular expression syntax.

    • For example:

      /^abcd$/

  • Negative regular expression: A string that starts with !/ and ends with /, using standard JavaScript regular expression syntax.

    • For example:

      !/^abcd$/

  • Similarity comparison: Uses the syntax ~nn[text], where:

    • nn is the similarity threshold (0-100).

    • text is the string used for the similarity comparison.

    • For example: ~75[ping fail received from] checks whether the event, alert, or Situation source field value has a similarity score of at least 75% compared to the specified text.

In this section: