FileSystemTrigger

Estimated reading: 3 minutes 2024 views

This activity helps the user monitor changes in a specified file or folder, such as the creation, deletion, or modification of files or folders. When such changes occur, the activity triggers the execution of a specific set of actions or a workflow.

Pre-requisites

1. This activity must be set as the initial activity in the workflow and cannot be used at the end or in the middle of the automation process.
2. Only one trigger activity is allowed per workflow and its sub-workflows. Multiple triggers are not supported.

Properties

INPUT

Extension: Indicates the file extension that needs to be filtered and monitored during workflow execution.
This parameter accepts values in the String datatype. You can either hardcode the values in “String” format or provide them in a “String” variable.

If left blank, all extension types will be considered.

IsIncludeSubfolders: When this option is checked, it enables monitoring of changes in the subfolders within the specified folder.
If left unchecked, subfolders will not be considered.

RootDirectory:* This parameter specifies the folder or directory path where the activity should monitor changes.
It accepts input values in the String datatype. You can either hardcode the values in a “String” variable or provide them in “String” format.

MISC

DisplayName: Displays the name of the activity. The activity name can be customized, which aids in troubleshooting.

SkipOnError: Specify the “Boolean” value as “True” or “False.”
True: Continue executing the workflow regardless of any errors thrown.
False: Halt the workflow if it encounters any errors.
None: If the option is left blank, the activity will, by default, behave as if “False” were chosen.

Version: It indicates the version of the feature being used.

OUTPUT

Result: It provides the ability to view the execution status of the activity. It returns values in “Boolean.”
True: Indicates that the activity has been executed successfully without any errors.
False: Indicates that the activity has been unsuccessful due to an unexpected error being thrown.

Represents mandatory fields to execute the workflow

Conditions

The advanced filter option allows you to validate against any of the specified conditions and trigger the workflow based on the selected action. By default, the trigger is set to activate when a file is created. You can select multiple filters to validate and trigger the action.

File System Events: Indicates to choose on which event the bot needs to filter and monitor the type of change. The action will be triggered immediately when the chosen action is met,

  • All: If a file or folder is created, renamed, modified, or deleted in the specified root directory.
  • Created: If a file or folder is created in the specified root directory.
  • Renamed: If a file or folder is renamed in the specified root directory.
  • Modified: If a file or folder is modified in the specified root directory.
  • Deleted: If a file or folder is deleted in the specified root directory.

Notify Filters: Based on the filter type chosen, it will validate with the file system events above to trigger the action workflow.

  • File name: Changes to file\folder name in the specified root directory.
  • Directory name: Changes to Directory name in the specified root directory.
  • Attributes: Changes to file\folder attribute in the specified root directory.
  • Size: changes to file size in the specified root directory.
  • Last write: Changes to last write date\time in the specified root directory.
  • Last access: Changes to last access date\time in the specified root directory.
  • Creation time: Changes to creation date\time in the specified root directory.
  • Security: Changes to File\folder security in the specified root directory.
Share this Doc

FileSystemTrigger

Or copy link

CONTENTS