Manage Workflow Engine Actions
After you have defined the data you want to process using a Workflow Engine in Moogsoft Onprem, 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.
Delay
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.
Actions
Define workflow actions as follows to add custom processing to events, alerts, or Situations depending on the type of engine:
Action Property | Description |
|---|---|
Action Name | Identifier for the action. Must be unique within the workflow. |
Function | 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 |
Value | 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. |
Forwarding Behavior | Controls the data flow. For objects where the function returns |
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 Onprem 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:
/gto test against all possible matches in a string./ito 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.