Automation is a set of controls that perform actions based on a set of rules.

Preliminar concepts.

Each rule is composed of:



Indicates the order of the evaluation.

The rules with less



Rule description.



Available events:

  • Document create.
  • Document update.
  • Document delete.
  • Document rename.
  • Document purge.
  • Document move.
  • Document version restore.
  • Document download from UI.
  • Document download from UI for preview.
  • Document print.
  • Document stamp.
  • Document virus detected
  • Document set node class
  • Folder create.
  • Folder delete.
  • Folder move.
  • Task update
  • Task delete.
  • Exports folder as JAR.
  • Mail creation.
  • Mail delete.
  • Mail move.
  • Mail download from UI.
  • Mail set node class.
  • Mail import attachments.
  • Record create.
  • Record delete.
  • Record move.
  • Record set node class.
  • Add metadata group.
  • Set metadata group.
  • Remove metadata group.
  • Text extraction.
  • Exports several nodes as ZIP.
  • Task create.
  • User create
  • User login.
  • User logout.
  • Note create.
  • Note update.
  • Note delete.



The evaluation time.

Available values:

  • Pre.
  • Post.

Understanding stages on automation execution:


Internal excution


Pre indicate rule execution before an internal event is executed.

Post indicate rule execution after the internal event is executed.

For example a rules based on "Document creation" event.

  • On "pre" stage the rule is triggered when the document has not yet been created.
  • On "post" stage the rules is triggered after the document has been created



When enabled, indicates no order rules should be executed.



Enables or disables the rule.



List of validators. Each validator is a condition that must be complied.

Validations are also ordered. It's a good practice to first set positions that will have more possibilities not to comply.

When empty, always comply.



List of actions. An action is something that will be done with the node that caused the execution of the rule.

Nodes types:

  • Document
  • Folder
  • Mail
  • Record

Example of an action, can be renaming a document immediately after creation.


Understanding Validators and Actions

The application provides a complete list of available validators and actions from Plugins view. Application plugins' architecture helps administrators to add new features to an existing application.

By default application comes with built in plugins:

Also you can create your own plugins:

More information about how to Register a new plugin.

Creating a rule

Rules are composed of:

  • General fields.
  • Actions and validators definions.

A rule creation has two steps. First define the general fields, then the actions and validations definitions.

  • On top right click on  Create new rule.
  • Fill in the fields.
  • Click on Create button. ( the application will return to the initial screen ).
  • Click on  Definition icon.
  • Add actions and validations according to convenience.
    • Click on Add validation icon.
    • Click on Add action icon.
  • When finished, at the top left click on Automation rules button. ( the application will return to the initial screen ).

Editing a rule

Edit general parameters

  • Click on  Edit rule.
  • Modify the fields.
  • Click on Edit button.

Edit action and validation definitions

  • Click on  Definition icon.
  • Modifiy actions and validations according to convenience.
    • Validations
      • Click on Add validation icon.
      • Click on  Edit validation icon.
      • Click on  Delete validation icon.
    • Actions
      • Click on Add action icon.
      • Click on  Edit action icon.
      • Click on  Delete action icon.

Deleting a rule

  • Click on  Delete rule.
  • Click on Delete button.