Window trigger package updates
- Updated: 2025/12/15
Review the updates in released versions of the Window 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 Window 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.7.1 | 15 December 2025 | Package-only; post Automation 360 v.39 (Sandbox) release | 21.112 or later | 11314 or later |
| 1.6.0 | 17 June 2024 | With Automation 360 v.33 (Sandbox) release | 21.112 or later | 11314 or later |
- 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-windows-<version.number>.jar - For Windows trigger package, the naming convention is:
bot-trigger-window-<version.number>.jarFor example,
bot-trigger-window-1.6.0.jar
For detailed steps on downloading a package and manually adding it to the Control Room, see Add packages to the Control Room.
1.7.1
- Compatible Bot Agent version: 21.112 or later
- Compatible Control Room version: 11314 or later
| What's new |
|---|
|
New Browser option The Window trigger package update introduces the Browser option. The Browser option enables you to define triggers based on the tabs that are currently open in a browser. The Refresh button auto-populates the browser title, the web page link, and the browser application. Service Cloud Case ID: 02204126 |
1.6.0
- Compatible Bot Agent version: 21.210 or later
- Compatible Control Room version: 13980 or later
| Fix |
|---|
| If you have used any of the Microsoft 365 Outlook rules as the window
trigger, the bot is now triggered successfully
when the corresponding rule in the Microsoft 365 Outlook is
executed. Service Cloud Case ID: 02099023 |