26.2 enhancements and patches

Review BMC Helix Innovation Suite 26.2 enhancements for features that will benefit your organization and to understand changes that might impact your users.

Version	SaaS	On-premises	Fixed issues	Updates and enhancements
26.2.00	✅		Known and corrected issues	26.2.00 updates

For a list of recent updates and enhancements across multiple versions, see Release notes and notices.

(SaaS subscribers only) Downloading and installing the SDK

Download the BMC Helix Innovation Studio SDK	See Setting up your IDE and installing BMC Helix Innovation Studio SDK.
Upgrading to BMC Helix Innovation Studio SDK 26.2.00	See Upgrading to the latest BMC Helix Innovation Studio SDK

BMC Helix applies upgrades as described in the BMC Helix Upgrade policy. BMC applies upgrades and patches during Maintenance windows.

26.2.00 updates

The following video (01:00) provides a quick overview of the enhancements in the BMC Helix Innovation Suite 26.2.00.

Automatic filtering of invalid email IDs to reduce email errors

As an administrator, configure the Email Engine to validate recipient email addresses and filter out invalid entries before sending emails, reducing email errors and unnecessary alerts. Invalid email IDs identified during processing are stored and automatically excluded from future email requests.

For more information, see AR System Email Invalid IDs form.

AR System Email form

View more records with infinite scrolling for list-based tables in Progressive Web Application screens

As an application developer, enable infinite scroll for list-based tables in Developer Studio. This allows application users to view more records by scrolling instead of switching pages in Progressive Web Application (PWA) screens. This capability improves usability when users review or select large numbers of records, especially on mobile and tablet devices.

For more information, see Adding a table field to a form.

Infinite scroll for list based tables

Control excessive process execution by using centralized configuration settings

As an administrator, configure centralized configuration settings to limit exclusive gateway loops, call activity recursion, multi‑instance iterations, and repeated receive task timer scheduling. These limits help prevent infinite execution, reduce resource consumption, and improve process stability and system performance.

To enforce the execution limits and control process behavior at runtime, configure the following centralized configuration settings:

Process-ExclusiveGateway-Max-Loop-Count
Process-CallActivity-Max-Recursion-Depth
Process-MultiInstance-Max-Iterations
Process-ReceiveTask-Max-Timer-Schedules
Process-Activity-Limit-Enforce-Exception

For more information, see Configuration settings N-R.

To control excessive process execution, submit a Change Request (RFC) in BMC Helix Support Central. For more information, see the Request for Change process.

What else changed in this release

The following table lists the changes in the product behavior:

Update	Product behavior in versions earlier than 26.2.00	Product behavior in version 26.2.00
Configuration updates in the logback_server.xml file	Changes to the logback_server.xml file take effect after an AR System server restart.	Changes to the logback_server.xml file take effect without an AR System server restart, which helps in avoiding downtime. The file is reloaded periodically, and changes might take a short time to take effect. For more information, see Enabling logging for web services.
Asynchronous logging for improved performance	BMC Helix Innovation Suite utilizes synchronous logging via the logback framework. When multiple threads attempt to log messages at the same time, only one thread can access the log while others are blocked, resulting in sequential logging.	BMC Helix Innovation Suite uses asynchronous logging, enabled by the Enable-Async-Logging CCS parameter. This CCS parameter configuration enables parallel logging, which prevents the threads from blocking each other and improves performance. For more information, see Configuration settings E-M.
Automatic cleanup of stale CCS entries for servers that are no longer running	CCS entries for servers that are no longer running are not automatically deleted and require manual cleanup.	CCS entries for servers that are no longer running are automatically deleted after 24 hours of inactivity, except for platform-sr servers. The administrative server must have four hours of uptime to perform the cleanup. For more information, see Updating configuration settings.