Skip to main content

Manage Workflow Engine Actions

After you have defined the data you want to process using a Workflow Engine in Moogsoft Enterprise, you can set up actions to programmatically transform the data and control the data flow.

Read through Workflow Engine Strategies and Tips for ideas about how to use the Workflow Engine.

When you edit an engine, you can click +Add Action to create a new action, or double-click an existing action to edit it.


By default, each workflow has a delay action. It is mandatory and you can not delete it. You can set the delay for up to 86,400 seconds (24 hours). If you enable the Reset option, if another matching event reaches the delay, the delay timer resets to 0.


Define workflow actions as follows to add custom processing to events, alerts, or Situations depending on the type of engine:

Action Property


Action Name

Identifier for the action. Must be unique within the workflow.


A programmatic task based on JavaScript and Java functions. The available function list varies according to the object: event, alert, enrichment, or Situation.

When you set the function, the UI displays its description and updates the Values to correspond to the function. For example, the contains action lets you check a field in your object for matching values. See Workflow Engine Functions Reference.Workflow Engine Functions Reference


Parameters for the function. The parameters vary from function to function. When you select a function, the UI updates the description of the parameters. For more information, see Workflow Engine Functions Reference and Alert and Event Field Reference.Workflow Engine Functions Reference

Forwarding Behavior

Controls the data flow. For objects where the function returns false, you can choose to always forward to the next action or workflow, stop the current workflow, or stop all workflows for the object.

If you have multiple actions, you can drag and drop them to arrange them according to your requirements.

Function Values

The parameters for the functions that make up Moogsoft Enterprise Workflow Engine actions accept the following types of data:

  • string: abcdef

  • number: 123

  • JSON object: { “ab” : “cd” , “e” : [ “f” , “g” ] }

In some cases, a parameter refers to the value for a specific field. For example, in the setClass function, the parameter “class” is a string and expects a specific value. Other parameters require a field name for the in-scope object. For example the upperCase function requires the object field that contains the value to convert to uppercase.

For some parameters you can use a regular expression using Javascript regular expression syntax. By default, Moogsoft uses the following regular expression flags:

  • /g to test against all possible matches in a string.

  • /i to ignore case.

Workflow Engine string and JSON object parameters accept macro syntax to allow for variable substitution. See Variable Substitution in Workflow Engine Actions for more information.