File Folder trigger package updates

Review the updates in released versions of the File Folder trigger package such as new and enhanced features as well as fixes and limitations. The page also lists the release dates of each version, and the compatible Control Room and Bot Agent versions.

Versions summary

The following table lists the versions of File Folder trigger package released either with an Automation 360 release or as a package-only release (in descending order of release dates). Click the version link for information about updates in that package version.

Version Release date Release type Bot Agent version Control Room build
1.5.1-20240422-182620 17 June 2024 With Automation 360 v.33 (Sandbox) release 20.11 or later 8750 or later
1.5.0-20230912-171023 6 December 2023 With Automation 360 v.31 (Sandbox) release 20.11 or later 8750 or later
Note:
  • To download an individual package (updated in an Automation 360 release where you want only the package), use this URL:

    https://aai-artifacts.my.automationanywhere.digital/packages/bot-trigger-file-folder-<version.number>.jar

  • For File folder trigger package, the naming convention is: bot-command-filefoldertrigger-<version.number>.jar

    For example, bot-command-filefoldertrigger-1.5.0-20230912-171023.jar

For detailed steps on downloading a package and manually adding it to the Control Room, see Add packages to the Control Room.

1.5.1-20240422-182620

  • Compatible Bot Agent version: 20.11 or later
  • Compatible Control Room version: 8750 or later
Fix

The File Folder trigger is now triggered correctly as per the number of text files created in the network folder. Previously, the File Folder trigger was continuously triggered even if only one text file was created.

Service Cloud Case ID: 02107416

1.5.0-20230912-171023

  • Compatible Bot Agent version: 20.11 or later
  • Compatible Control Room version: 8750 or later
Fix

The resiliency of the File Folder trigger is improved, and the bot no longer gets stuck at the trigger loop action after a network disruption has occurred. Previously, a network error caused the bot to get stuck and not proceed further even after the trigger event has occurred.

Service Cloud Case ID: 01973240