Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
automationrules [2021_06_08 13:51] – smeadmin | automationrules [2024_03_04 17:44] – [Applies to:] steven | ||
---|---|---|---|
Line 1: | Line 1: | ||
# Data Automation Rules | # Data Automation Rules | ||
+ | |||
+ | ##### last updated on: Feb. 26, 2022 | ||
## Introduction | ## Introduction | ||
- | The Enterprise File Fabric's Data Automation Rules deliver | + | Access Anywhere's Data Automation Rules deliver |
- | Data Automation | + | Each Data Automation |
- | Data Automation Rules are configured a Organization Administrator. | ||
- | Applies to: | ||
- | * Enterprise File Fabric Appliance [Add-On] (since [[cloudappliance/ | + | ## See Also: |
- | See Also: | + | * [[contentdiscovery|Content Discovery]] |
- | * [[contentdiscovery]] | + | * [[file_content_intelligence/ |
- | * [[contentdiscoveryconfig]] | + | |
- | For data automation rules to be enabled | + | ## Administration |
+ | |||
+ | The Data Automation Rules configuration page is accessed from the Organization menu by the organization administrator | ||
- | The Data Automation Rules configuration page is accessed from the Organization menu by users with the Administrator role. | ||
## Event Types | ## Event Types | ||
- | This section outlines the available Event Types that the Enterprise File Fabric | + | This section outlines the available Event Types that Access Anywhere |
### 1. File is uploaded through this platform | ### 1. File is uploaded through this platform | ||
- | Description: | + | Description: |
- | Available since: 2106.00 | + | **Available since**: 2106.00 |
### 2. File is discovered on storage | ### 2. File is discovered on storage | ||
- | Description: | + | Description: |
- | Available since: 2106.00 | + | **Available since**: 2106.00 |
### 3. File is discovered on storage or uploaded | ### 3. File is discovered on storage or uploaded | ||
- | Description: | + | Description: |
- | Available since: 2106.00 | + | |
+ | **Available since**: 2106.00 | ||
### 4. File contains matches against Content Discovery Rules | ### 4. File contains matches against Content Discovery Rules | ||
- | Description: | + | Description: |
- | Available since: 2106.00 | + | |
- | ## Action Types | + | **Available since**: 1906.00 |
- | ## Content Discovery | + | ## Action Types |
- | Automation rules work with [[contentdiscovery]] detectors and categories. Content Detectors trigger Content Detection Categories, which raise events that trigger rules which execute actions: | + | <WRAP center round tip 100%> |
+ | Each action type is available only for the event types listed at the end of the action type's description. | ||
+ | </ | ||
- | {{ : | + | ### 1. Copy file to another folder |
+ | This action copies the file that triggered the event to a designated folder. The designated folder can be selected using the folder selector control. The Copy operation will be performed as a Background Task assigned to the Admin user. | ||
+ | **Supported Events**: #1, #2, #3, #4 | ||
- | ## Creating an Automation Rule | + | **Available since**: 1906.00 |
- | An automation rule consists | + | ### 2. Perform Content Intelligence |
+ | This action sends the file that triggered the event to the Content Intelligence module for analysis. The Content Intelligence extractors that are enabled at the time of the event will be executed for the file. The process of Content Intelligence will be executed via a Background Task and will be performed as per the systems Task scheduling. | ||
- | ### Event | + | **Supported Events**: |
- | Choose “Create Rule” to create an automation rule. | + | **Available since**: 2006.00 |
- | The only event currently supported is “Content is detected in a file”. It’s triggered when content of interest is detected in a file that is uploaded or moved. | + | ### 3. Transcode file |
+ | This action sends the file that triggered the event to be transcoded using Access Anywhere' | ||
- | You may create multiple automation rules with the same event type. Typically they will have different conditions but this is not required. | + | To use the transcode file rule you will need to enable "Video transcoding" |
- | ### Condition | + | **Supported Events**: |
- | For a content detection event the condition is a Content Detection Category. For example “GDPR” or “North America - National Identifiers”. | + | **Available since**: 2106.00 |
- | {{ :: | + | ### 4. Send email to an email address |
- | Select ***Create Rule*** | + | This action allows the event to notify a single email address when a qualifying event is triggered. The email address is specified during the configuration of the action. |
- | ### Action | + | {{ : |
- | You may create many actions for each automation rule. | + | **Supported Events**: #4 |
- | The following actions are supported: | + | **Available since**: 1906.00 |
- | * Email members of a role | + | ### 5. Send email to members who have a role |
- | | + | This action sends a notification |
- | * Disable file url creation | + | |
- | * Move the file to another folder | + | |
- | + | ||
- | ## Actions | + | |
- | + | ||
- | ### Email Members of a Role | + | |
- | + | ||
- | This action | + | |
- | + | ||
- | Configuration | + | |
- | + | ||
- | * Choose one role (drop-down) | + | |
- | * Choose to only send to members | + | |
{{ : | {{ : | ||
Line 103: | Line 96: | ||
{{ : | {{ : | ||
- | ### Send an Email to an Email Address | + | **Supported Events**: |
- | This action allows the event to notify a single email address. | + | **Available since**: 1906.00 |
- | Configuration | ||
- | * A valid email address. | + | ### 6. Disable file URL creation |
+ | This action prevents the file from being shared through the creation of secure shared links. This action can also be configured to disable existing shared links. | ||
- | {{ : | + | {{ : |
- | ### Disable file url creation | ||
- | This action prevents the file being shared through the creation of shared links. | + | **Supported Events**: #4 |
- | Configuration | + | **Available since**: 1906.00 |
- | + | ||
- | * Optionally disable shared links that have already been created. | + | |
- | + | ||
- | {{ : | + | |
- | ### Move the file to another folder | ||
- | This action moves the matched | + | ### 7. Move file to another folder |
+ | This action moves files matched | ||
Configuration | Configuration | ||
- | * Choose folder from dialog (folder must exist or can be created from dialog) | + | * Choose |
- | * Optionally disable shared links that have already been created. | + | |
{{ : | {{ : | ||
- | A suffix is added to the file as it is moved which includes the date and time. This prevents subsequent updates overwriting the quarantined version. An additional optional suffix may also be added. File extensions are preserved. | + | A suffix is added to the file as it is moved which includes the date and time. This prevents subsequent updates |
- | For example, with an provided suffix of " | + | For example, with a provided suffix of " |
CreditApplication.pdf | CreditApplication.pdf | ||
Line 143: | Line 130: | ||
CreditApplication_ContainsSSN_2018-08-20_22-08-24.pdf | CreditApplication_ContainsSSN_2018-08-20_22-08-24.pdf | ||
+ | | ||
+ | **Supported Events**: #4 | ||
+ | |||
+ | **Available since**: 1906.00 | ||
+ | |||
+ | ### 8. Call webhook | ||
+ | This action causes Access Anywhere to invoke an HTTP callback when a qualifying event occurs. | ||
+ | |||
+ | {{ :: | ||
+ | |||
+ | The Access Anywhere invokes the callback with the HTTP POST request method. The callback is invoked once per file for which a qualifying event is detected. | ||
+ | |||
+ | The HTTP request will contain a User-Agent header et to the site title of Access Anywhere sending the HTTP request followed by Access Anywhere version, | ||
+ | |||
+ | |||
+ | The request body is a JSON representation of information about the file in which the qualifying content was discovered and about the event that caused the webhook to be called. Here is an example: | ||
+ | |||
+ | ``` | ||
+ | { | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | ], | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | ], | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | } | ||
+ | }, | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | } | ||
+ | } | ||
+ | } | ||
+ | ``` | ||
+ | |||
+ | Webhook invocations by Access Anywhere will timeout if a connection cannot be established with the webhook host within 3 seconds, or if the first byte of the reply is not received within 30 seconds after the connection is established. | ||
- | Email notifications use the new generated file name and folder location. | + | At the discretion of the implementor, |
+ | {{ :: | ||
+ | **Supported Events**: #4 | ||
+ | **Available since**: 2106.00 |