Page Comparison

User defined actions are created using the defaction keyword. The defaction keyword closely follows the syntax of functions. User-defined actions allow for data preprocessing and the execution of one or more actions. User-defined actions are useful for wrapping actions to allow for composite actions or a cleaner syntax surrounding existing actions for a common use case.

defaction(<arguments><parameters>) {
  configure using key1 = value1 and 
           
      key2 = value2 and 
                  ...
                  keyN = valueN
  <declaration0>
  ...
  <declarationN>

  <action block>
}

The arguments are parameters are a possibly empty, comma-separated list of variable names. Optional arguments can be specified with the configure statement, as shown here, and are given default values. . All parameters can be assigned a default value.  More details can be found in Using Optional and Named Parameters. 

Zero or more declarations can be included to prepare data for the action block. 

The action block is the same as the action block in a rule. Any action, including a user-defined action, can be used in the action block. Actions can be simple or compound. A simple action is a valid action block. For example, the following defines an action called send_warning using the notify action event:send action:

send_warning = defectiondefaction(msg, eci) {
notify("  event:send({"eci":eci, "domain":"message", "type":"warning", "attrs": {"warning":"Warning!", + msg}});
}

Compound actions must be enclosed in curly brackets ({...}). work the same as a rule. Suppose, for example, that in addition to putting up a notification, you wished to place the warning message in a <div/> element on the pageuse send_directive:

send_warning = defectiondefaction(msg, eci) {

  every {notify("Warning!", msg);
    event:send({"eci":eci, "domain":"message", "type":"warning", "attrs": {"warning":"Warning!" + msg}});

    appendsend_directive("#warning_diva_warning_was_given", {"message":"msg"})
  }
}

You can use optional parameters to modify send_warning so that it is sticky by default. (The default behavior for notify is for the notification to fade after six seconds. When the sticky parameter is true, notifications are permanent until the user closes them.)

send_warning = defaction(msg) {
  configure using transitory = false
  notify("Warning!", msg)
    with sticky = not transitory
}

The variable send_warning only has meaning in an action context within a rule. The following shows the use of send_warning and its optional parameter in the action of a rule:

if error_level > 12 && error_level < 15 then
  send_warning("Abnormal error levels")
    with transitory = true

Because user-defined actions are first-class values (i.e., they can be returned as the result of executing an expression), they can be passed into functions or other user-defined actions and returned as the result from a function. You can thus write recursive actions.The variable send_warning only has meaning in an action context within a rule. Because user-defined actions are first-class values (i.e., they can be returned as the result of executing an expression), they can be passed into functions or other user-defined actions and returned as the result from a function. You can thus write recursive actions.

User defined actions may also return values. The returned value may be a string, map, array etc. Consider the following example that returns a map:

    deleteChild = defaction(pico_name){
      ent_children = children(){"children"}
      child_collection = ent_children.collect(function(child){
                                              (child{"name"} ==  pico_name) => "to_delete" | "dont_delete"
                                            })
      child_to_delete = child_collection{"to_delete"}.head()

      every {
        engine:removePico(child_to_delete{"id"})
      }
      return
      {
        "updated_children": child_collection{"dont_delete"},
        "child": child_to_delete
      }
    }

To retrieve the returned value (in this case a map), bind it to a new name using "setting":

deleteChild(<give pico name>) setting(returnValue)