Standalone Actions

Note: Standalone actions are supported only in the Cleo Harmony application.

Standalone actions are actions that are not tied to a specific host or user. They exist beside, and not within, hosts or users.

You can use standalone actions for a variety of purposes, such as:

Filtering incoming payload (for example, the Antivirus Scan action)
Listening for and acting on log events
Processing new file arrival or user session end events
Scheduling periodic maintenance tasks

A standalone action can access configured hosts and users (and their related incoming payload and events) when they are in-scope, which means that relative to the standalone action, the host or user is located in the same host tree resource folder or below, or in the root host tree folder (which is always accessible). A standalone action contains only JavaScript commands.

Similar to other actions, you can run standalone actions interactively, through the Java API, and through command line operations (for example, Harmonyc -r "MyStandaloneAction"). You can also schedule standalone actions to run periodically, or trigger them to run when a new file arrives or a session ends.