Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
automationrules [2018_08_28 01:21] – ↷ Page name changed from dataautomation to automationrules steven | automationrules [2024_02_28 01:03] – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
# Data Automation Rules | # Data Automation Rules | ||
- | An administrator can pre-configure actions to be automatically performed when different types of content is detected. For example, an email could be sent, or a file moved or restricted based on the detection of personally identifiable information. | + | ##### last updated on: Feb. 26, 2022 |
- | 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. | + | ## Introduction |
- | The Data Automation Rules configuration page is accessed from the Organization menu by users with the Administrator role. | + | Access Anywhere' |
- | ## Creating an Automation Rule | + | Each Data Automation Rule configured in Access Anywhere consists of an //event trigger// (e.g. "File is uploaded" |
- | An automation rule consists of an event, a condition and one or more actions. | ||
- | ### Event | + | ## Applies to: |
- | Choose “Create Rule” | + | * Access Anywhere Appliance v2106 and above (all licenses; functionality varies according |
+ | * Access Anywhere Appliance [[cloudappliance/ | ||
- | 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. | + | ## See Also: |
- | You may create multiple automation rules with the same event type. Typically they will have different conditions but this is not required. | + | * [[contentdiscovery|Content Discovery]] |
- | ### Condition | + | * [[file_content_intelligence/ |
- | For a content detection event the condition is a Content Detection Category. For example “GDPR” or “North America - National Identifiers”. | + | ## Administration |
- | {{ :: | + | The Data Automation Rules configuration page is accessed from the Organization menu by the organization administrator and by users with the Administrator role. |
- | Select ***Create Rule*** to begin adding actions. | ||
- | ### Action | + | ## Event Types |
- | You may create many actions for each automation rule. | + | This section outlines the available Event Types that Access Anywhere supports. |
- | The following actions are supported: | + | ### 1. File is uploaded through this platform |
+ | Description: | ||
+ | |||
+ | **Available since**: 2106.00 | ||
- | * Email members of a role | + | ### 2. File is discovered on storage |
- | * Send an email to an email address | + | Description: |
- | * Disable | + | |
- | * Move the file to another folder | + | |
- | ## Actions | + | **Available since**: 2106.00 |
- | ### Email Members | + | ### 3. File is discovered on storage or uploaded |
+ | Description: | ||
- | This action immediately sends a notification by email to members of a role. | + | **Available since**: 2106.00 |
- | Configuration | + | ### 4. File contains matches against Content Discovery Rules |
+ | Description: | ||
- | * Choose one role (drop-down) | + | **Available since**: 1906.00 |
- | * Choose to only send to members to have access to the file | + | |
- | {{ : | ||
- | An email like the following will be sent when matching content is detected: | ||
- | {{ : | + | ## Action Types |
- | ### Send an Email to an Email Address | + | <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. | ||
+ | </ | ||
- | This action | + | ### 1. Copy file to another folder |
+ | This action | ||
- | Configuration | + | **Supported Events**: #1, #2, #3, #4 |
- | * A valid email address. | + | **Available since**: 1906.00 |
+ | |||
+ | ### 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. | ||
+ | |||
+ | **Supported Events**: #1, #2, #3 | ||
+ | |||
+ | **Available since**: 2006.00 | ||
+ | |||
+ | ### 3. Transcode file | ||
+ | This action sends the file that triggered the event to be transcoded using Access Anywhere' | ||
+ | |||
+ | To use the transcode file rule you will need to enable "Video transcoding" | ||
+ | |||
+ | **Supported Events**: #1, #2, #3 | ||
+ | |||
+ | **Available since**: 2106.00 | ||
+ | |||
+ | ### 4. Send email to an email address | ||
+ | |||
+ | This action allows the event to notify a single email address when a qualifying event is triggered. The email address | ||
{{ : | {{ : | ||
- | ### Disable file url creation | + | **Supported Events**: |
- | This action prevents the file being shared through the creation of shared links. | + | **Available since**: 1906.00 |
- | Configuration | + | ### 5. Send email to members who have a role |
+ | This action sends a notification of the triggering event by email to organization members who have the specified role. When configuring the action you must select the role from the dropdown, as well as whether the notification should only be sent to members of that role that have permissions to access the file that triggered the event, or to all members with the role regardless of their permissions. | ||
- | * Optionally | + | {{ : |
+ | |||
+ | An email like the following will be sent when matching content is detected: | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | **Supported Events**: #4 | ||
+ | |||
+ | **Available since**: 1906.00 | ||
+ | |||
+ | |||
+ | ### 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 | ||
{{ : | {{ : | ||
- | ### Move the file to another folder | ||
- | This action moves the matched | + | **Supported Events**: #4 |
+ | |||
+ | **Available since**: 1906.00 | ||
+ | |||
+ | |||
+ | ### 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 95: | Line 134: | ||
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 |