Differences

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

--- automationrules [2023_06_06 14:16] – [Data Automation Rules] eric
+++ automationrules [2024_03_04 17:44] – [Applies to:] steven
@@ Line 5: / Line 5: @@
 ## Introduction
-The Enterprise File Fabric's Data Automation Rules deliver if-this-then-that functionality for automatically taking actions when certain types of events happen on File Fabric.
+Access Anywhere's Data Automation Rules deliver if-this-then-that functionality for automatically taking actions when certain types of events happen on Access Anywhere.
-Each Data Automation Rule configured in the Enterprise File Fabric consists of an //event trigger// (e.g. "File is uploaded") which triggers one or more configurable //actions// (e.g. "Transcode video file" or "Perform content intelligence").
+Each Data Automation Rule configured in Access Anywhere consists of an //event trigger// (e.g. "File is uploaded") which triggers one or more configurable //actions// (e.g. "Transcode video file" or "Perform content intelligence").
-## Applies to:
- * Enterprise File Fabric Appliance v2106 and above (all licenses; functionality varies according to licensed features)
- * Enterprise File Fabric Appliance [[cloudappliance/applupdatev1808|v1808]] - [[cloudappliance/applupdatev2006|v2006]] (licenses including Content Discovery)
 ## See Also:
@@ Line 28: / Line 24: @@
 ## Event Types
-This section outlines the available Event Types that the Enterprise File Fabric supports.
+This section outlines the available Event Types that Access Anywhere supports.
 ### 1. File is uploaded through this platform
-Description: This event is triggered when a file is uploaded by a user directly on the Enterprise File Fabric. The scope of this upload can be narrowed using the Folder selector.
+Description: This event is triggered when a file is uploaded by a user directly on Access Anywhere. The scope of this upload can be narrowed using the Folder selector.
 **Available since**: 2106.00
 ### 2. File is discovered on storage
-Description: This event is triggered when a file is discovered directly on a storage platform under the management of the Enterprise File Fabric. A file will be discovered when a Provider Re-sync, Cloud Refresh or Deep Cloud Refresh is performed; this event type does not trigger the 'automatic discovery' of files or folders. The scope of this upload can be narrowed using the Folder selector.
+Description: This event is triggered when a file is discovered directly on a storage platform under the management of Access Anywhere. A file will be discovered when a Provider Re-sync, Cloud Refresh or Deep Cloud Refresh is performed; this event type does not trigger the 'automatic discovery' of files or folders. The scope of this upload can be narrowed using the Folder selector.
 **Available since**: 2106.00
@@ Line 73: / Line 69: @@
 ### 3. Transcode file
-This action sends the file that triggered the event to be transcoded using the File Fabric's transcoding capabilities. When configuring this event type, you are required to select the Transcoding Preset you wish the file to be transcoded into.
+This action sends the file that triggered the event to be transcoded using Access Anywhere's transcoding capabilities. When configuring this event type, you are required to select the Transcoding Preset you wish the file to be transcoded into.
 To use the transcode file rule you will need to enable "Video transcoding" through the Organization > Content Intelligence page.
@@ Line 140: / Line 136: @@
 ### 8. Call webhook
-This action causes the File Fabric to invoke an HTTP callback when a qualifying event occurs.  The File Fabric customer using this option is responsible for providing the callback implementation at the URL configured for the action in the rule, and for ensuring that the URL is reachable by the File Fabric.
+This action causes Access Anywhere to invoke an HTTP callback when a qualifying event occurs.  The Access Anywhere customer using this option is responsible for providing the callback implementation at the URL configured for the action in the rule, and for ensuring that the URL is reachable by Access Anywhere.
 {{ ::webhook_url.png?direct&400 |}}
-The File Fabric invokes the callback with the HTTP POST request method. The callback is invoked once per file for which a qualifying event is detected.
+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 the File Fabric sending the HTTP request followed by the File Fabric version,  for example: “SME Appliance 2106.00“. It will also contain a Content-Type header set to “application/json”.
+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,  for example: “NAA Appliance 2106.00“. It will also contain a Content-Type header set to “application/json”.
@@ Line 194: / Line 190: @@
 ```
-Webhook invocations by the File Fabric 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.  The rule that invoked the webhook will pause until the response is received or a timeout has occurred.
+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.  The rule that invoked the webhook will pause until the response is received or a timeout has occurred.
-At the discretion of the implementor, webhooks can be accessed using HTTP or HTTPS.  The URL's protocol component should indicate the correct method of access. When HTTPS is used the File Fabric will the SSL certificate provided by the webhook host if validation is turned on in Site Functionality.
+At the discretion of the implementor, webhooks can be accessed using HTTP or HTTPS.  The URL's protocol component should indicate the correct method of access. When HTTPS is used Access Anywhere will the SSL certificate provided by the webhook host if validation is turned on in Site Functionality.
 {{ ::webhooks_val.png?direct&600 |}}