A360BotFramework-3.9.1

What's New

Screen recording (new)

Capture short video clips of bot activity around your log entries to make failures self-explanatory. Configure once on Start Logger Session, then each matching log entry gets a clip alongside it.

• Pick which log levels record: Choose any combination of INFO, WARN, ERROR. Default is ERROR-only.
• Buffer length: 5 to 90 seconds, default 30. Each clip captures the seconds leading up to the log entry that triggered it.
• Encoder choice:
  • Fast (default, recommended): quick to encode, larger files (~5-15 MB per clip).
  • Compact: smaller files (~1-3 MB per clip), slower to encode.
• HTML log preview: Each entry that has a clip shows a poster thumbnail with a play overlay in the Screen column. Click it to open the MP4 in a new browser tab.
• Stop drains pending clips: When you call Stop Logger Session, it waits for any in-flight encoding to finish (up to 5 minutes) so every clip lands on disk before the bot exits. Stop Logger Session is safe to call from a Finally block even if the happy path also called it; the second call is a no-op.
• Force-kill recovery (mainly Compact mode): AV1 (Compact) clips take longer to encode, so if a bot is force-killed before its pending clips finish, the next bot run automatically picks them up and writes them to the exact paths the HTML log already references. Fast mode encodes quickly enough that the regular close-time drain covers it under normal conditions.
• Loop dedup: When several entries fire within the same second, they share one clip instead of producing many near-identical MP4s.
• No FFmpeg install needed: A small FFmpeg binary is bundled with the package and extracted automatically to %LOCALAPPDATA%\A360-BotFramework\ on first use.

Other improvements

• Reliable append-across-sessions: Log files stay structurally clean no matter how many bot sessions append to them, so they always render correctly in the browser.
• Hover highlight on log rows: Mousing over a row now shows a colored outline (blue for INFO, amber for WARN, red for ERROR) so you can clearly see which row you're pointing at on long logs.

How to use

• Jar File: You can add packages using the Jar file format. Simply navigate to Manage > Packages and import your packages effortlessly.

• Zip File: If you prefer a Zip file format, you can also add packages using this method. Go to Automation > Import to import packages via Zip files. - Community Edition

Important Note for Community Edition Control Room Users

• Warning: Please be aware that in the Community Edition Control Room, the system does not automatically set the latest version of imported packages as the default. To ensure you are using the latest and fully functional features, you must manually change the package version to the latest version in every bot.

What's New

Logger UI overhaul

• Visible whitespace glyphs: log messages and variable values now render newlines as ↵, tabs as →, and trailing spaces as · dots. Markers are dim and copy-paste safe (user-select: none) so they don't leak into clipboard. Catches whitespace bugs in stack traces, JSON values, and trailing-space artifacts at a glance.
• Sticky table summary: when scrolling long variable tables, the "Table: X rows ×ばつ Y cols" summary stays pinned at the top alongside the column headers. Collapse from anywhere without scrolling back.
• Threaded nested children: nested lists and dictionaries now show a single continuous left-side line connecting all children, Reddit / GitHub thread style. Click the line to collapse the branch — pure CSS, no JavaScript.
• Flat edge-to-edge layout: dropped rounded outer corners, body padding, and card shadows. Both log.html and variables.html now use the full viewport width like a native data viewer.
• Auto dark mode: both templates honor @media (prefers-color-scheme: dark), switching palette automatically based on OS / browser preference.
• Larger centered screenshot preview: hover preview moved to viewport center and expanded to min(75vw, 1280px) with 16:9 aspect. Near-HD detail without dominating the screen.

Build / project

• gradle.properties.example shipped to help developers pin the Gradle daemon JVM to JDK 11 (matches the AA360 runtime, avoids Groovy 3.0.24 class-file-version errors when the daemon runs on JDK 22+).
• TestNG configuration moved into build.gradle for explicit useTestNG() integration.

How to use

• Jar File: You can add packages using the Jar file format. Simply navigate to Manage > Packages and import your packages effortlessly.

• Zip File: If you prefer a Zip file format, you can also add packages using this method. Go to Automation > Import to import packages via Zip files. - Community Edition

Important Note for Community Edition Control Room Users

• Warning: Please be aware that in the Community Edition Control Room, the system does not automatically set the latest version of imported packages as the default. To ensure you are using the latest and fully functional features, you must manually change the package version to the latest version in every bot.

A360BotFramework-3.6.1

What's New

• LogMessage action now returns the file path of the log file
• Fix log rollover: added DefaultRolloverStrategy attribute and 1000 default entry count (#3)
• Upgrade SDK to 1.7.0, Log4j2 to 2.25.3, TestNG to 7.12.0, POI to 5.5.1, commons-io to 2.21.0, org.json to 20251224
• Fix critical CreateFolders bug: prefix null check was overwriting suffix
• Fix XMLReader with full entity expansion protection
• Fix NPE in XMLReader when XML nodes lack expected attributes
• Fix StringIndexOutOfBoundsException in LogMessage URI parsing
• Replace thread-unsafe SimpleDateFormat with DateTimeFormatter in CustomHTMLLayout
• Preserve exception cause chains across all action classes
• Replace System.out/err with proper Log4j2 logging in TaskKiller, ExcelReader, HTMLGenerator
• Add process exit timeout (30s) and kill all matching processes in TaskKiller
• Add parent directory creation in CaptureScreen before writing screenshots
• Pre-compile regex patterns in DeleteFilesFolders for better performance
• Fix null safety in CustomLogger folder path getters
• Fix resource leak in HTMLGenerator template stream loading
• Improve error messages in JSONReader and StopLoggerSession

How to use

• Jar File: You can add packages using the Jar file format. Simply navigate to Manage > Packages and import
  your packages effortlessly.

• Zip File: If you prefer a Zip file format, you can also add packages using this method. Go to Automation > Import to import packages via Zip files. - Community Edition

Important Note for Community Edition Control Room Users

• Warning: Please be aware that in the Community Edition Control Room, the system does not automatically set
  the latest version of imported packages as the default. To ensure you are using the latest and fully functional
  features, you must manually change the package version to the latest version in every bot.

A360BotFramework-3.5.1

What's New

• GitHub-style source column formatting for log line location: WORKSPACE:PATH@vVERSION#LINE
• Entry-count based log rotation for better log management
• Enhanced DeleteFilesFolders with improved clarity and options
• Smart directory preservation for recently modified files

How to use

• Jar File: You can add packages using the Jar file format. Simply navigate to Manage > Packages and import
  your packages effortlessly.

• Zip File: If you prefer a Zip file format, you can also add packages using this method. Go to Automation > Import to import packages via Zip files. - Community Edition

Important Note for Community Edition Control Room Users

• Warning: Please be aware that in the Community Edition Control Room, the system does not automatically set
  the latest version of imported packages as the default. To ensure you are using the latest and fully functional
  features, you must manually change the package version to the latest version in every bot.

What's New

• Table datatype scrolling and header snapping for large tables
• Better logs visuals
• Captures variable in separate file
• Captures variable and screenshot by relative path, allowing viewing on other devices

How to use

• Jar File: You can add packages using the Jar file format. Simply navigate to Manage > Packages and import your packages effortlessly.

• Zip File: If you prefer a Zip file format, you can also add packages using this method. Go to Automation > Import to import packages via Zip files. - Community Edition

Important Note for Community Edition Control Room Users

• Warning: Please be aware that in the Community Edition Control Room, the system does not automatically set the latest version of imported packages as the default. To ensure you are using the latest and fully functional features, you must manually change the package version to the latest version in every bot.

What's New

• Performance Improvement: Optimized logging process for faster execution
• Enhanced Portability: Logs can now be moved between folders without breaking links
• Better Support for Different Locations: Logs work seamlessly in nested folders and different drives
• **CSS changes
  image
  image

Benefits

• Faster bot execution when logging is enabled
• More reliable logging across different environments
• Improved experience when sharing log files with your team

How to use

• Jar File: You can add packages using the Jar file format. Simply navigate to Manage > Packages and import your packages effortlessly.

• Zip File: If you prefer a Zip file format, you can also add packages using this method. Go to Automation > Import to import packages via Zip files. - Community Edition

Important Note for Community Edition Control Room Users

• Warning: Please be aware that in the Community Edition Control Room, the system does not automatically set the latest version of imported packages as the default. To ensure you are using the latest and fully functional features, you must manually change the package version to the latest version in every bot.

Fixes Excel reader on older bot agent versions
Removed AllowedTarget.HEADLESS, newer control room versions do not allow actions which can be executed via api tasks

How to use

• Jar File: You can add packages using the Jar file format. Simply navigate to Manage > Packages and import your packages effortlessly.

• Zip File: If you prefer a Zip file format, you can also add packages using this method. Go to Automation > Import to import packages via Zip files. - Community Edition

Important Note for Community Edition Control Room Users

• Warning: Please be aware that in the Community Edition Control Room, the system does not automatically set the latest version of imported packages as the default. To ensure you are using the latest and fully functional features, you must manually change the package version to the latest version in every bot.

How to use

• Jar File: You can add packages using the Jar file format. Simply navigate to Manage > Packages and import your packages effortlessly.

• Zip File: If you prefer a Zip file format, you can also add packages using this method. Go to Automation > Import to import packages via Zip files. - Community Edition

Important Note for Community Edition Control Room Users

• Warning: Please be aware that in the Community Edition Control Room, the system does not automatically set the latest version of imported packages as the default. To ensure you are using the latest and fully functional features, you must manually change the package version to the latest version in every bot.

How to use

• Jar File: You can add packages using the Jar file format. Simply navigate to Manage > Packages and import your packages effortlessly.

• Zip File: If you prefer a Zip file format, you can also add packages using this method. Go to Automation > Import to import packages via Zip files. - Community Edition

Important Note for Community Edition Control Room Users

• Warning: Please be aware that in the Community Edition Control Room, the system does not automatically set the latest version of imported packages as the default. To ensure you are using the latest and fully functional features, you must manually change the package version to the latest version in every bot.