September 2026
BIA Version 3.2.0 Release Notes
This release introduces a new version of the Business Integration Agent (BIA) for Process Automation. Not all Process Automation users use BIA — you can read more about it here: BIA - Business Integration Agent.
BIA version 3.2.0 can be downloaded from the installation page.
Updates
LDAPS support when querying Active Directory
It's now possible to query Active Directory over LDAPS, providing a more secure connection than standard LDAP when the BIA reads from a local AD.
Get form field changes from applications
Get form field changes from one or several applications using the BIA API endpoint and store the result in a database. Data is stored normalized, but a pivot action can be configured to store data by case/instance instead.
The CallWS action can include a certificate
The “CallWS” action now has the option to include a certificate when calling other systems. The certificate is included by providing the path to the PFX file along with its password.
A specific command timeout can be set for MS SQL queries
The MS SQL adapter now supports an optional command timeout parameter. The value must be greater than 0.
Bug fixes
Lookup responses only work once
Error
Lookup responses were only processed correctly on the first call.
Fix
Lookup responses now work as expected on repeated calls.
Bali1 adapter, a BIA data source, crashes if form field values are of different types
Error
The Bali1 adapter crashed when form field values contained mixed types.
Fix
The Bali1 adapter now handles mixed-type form field values without crashing.
Bali1 adapter used wrong date format
Error
The Bali1 adapter was formatting dates incorrectly.
Fix
The Bali1 adapter now uses the correct date format.
Sync of extended value lists could not include “[” or “]” characters in column values
Error
Column values containing either the [ or ] character caused sync failures for extended value lists.
Fix
Extended value list sync now supports column values that contain both [ and ] characters.
“On Event Error” did not trigger on login errors
Error
The “On Event Error” handler was not triggered when a login error occurred.
Fix
The “On Event Error” handler now triggers correctly for login errors.
Application messages lost if one message in a batch creates an error
Error
When a single message in a batch or page caused an error, all subsequent application messages in that batch were lost.
Fix
Application messages are no longer dropped when a single message in a batch creates an error.
Sync of external extended value lists takes too long
Error
Syncing external extended value lists was taking too long to complete.
Fix
Performance of external extended value list sync has been improved.
This release also contains additional minor bug fixes and security updates.