Differences

This shows you the differences between two versions of the page.

--- automationrules [2018_09_21 03:00] – steven
+++ automationrules [2021_05_20 16:13] – smeadmin
@@ Line 3: / Line 3: @@
 ## Introduction
-Whether for compliance or competitive reasons, organisations often need to take action based on documents of special interest.
+The Enterprise File Fabric's Data Automation Rules functionality delivers 'IFTT' functionality for automating actions when particular events happen on your storage.
+As an example:
  * Documents that contain personal data restricted under GDPR? - Don't allow them to be shared!
  * Sales contracts reference obsolete SKUs? - Notify the the legal team and move them to quarantine!
  * Files containing the name Ernie Madeoff? - Send email to the finance director!
+ * High-res media assets require automatic transcoding? Do that as soon as the file lands!
 An administrator can pre-configure actions to be automatically performed when different types of content are detected.  For example, an email could be sent, or a file moved or restricted based on the detection of personal data.
@@ Line 20: / Line 23: @@
  * [[contentdiscoveryconfig]]
-For data automation rules to be enabled the Content Discovery module must be enabled, and providers configured for content search. For more information see Content Discovery.
+For data automation rules to be enabled the Content Discovery module must be enabled, and providers configured for content search. For more information see [[contentdiscoveryconfig]].
 The Data Automation Rules configuration page is accessed from the Organization menu by users with the Administrator role.
+## Content Discovery
+Automation rules work with [[contentdiscovery]] detectors and categories. Content Detectors trigger Content Detection Categories, which raise events that trigger rules which execute actions:
+{{ :contentdiscovery:data-automation-structure.png?nolink&400 |}}
 ## Creating an Automation Rule