This article lists features, improvements, and bug fixes that are currently available in sandbox environments only.
Once the features are released to production environments, they are deleted from this article and will appear only in the standard release notes.
Collaboration Room
🟦 Radius customization
Business Configurators can now define rounded corner styles for buttons, cards, and input fields across the Agent and Customer UIs. Radius values can be customized or selected from presets, with real-time previews and reset options available in system or team settings.
Admin Center
🔍 Advanced column filters for table searches
Admin Center tables now support per-column filtering for faster, more precise searches. Each column includes a filter button that opens a list of all unique values (from the entire dataset, not just the current page) and a search box.
You can:
Select multiple values using checkboxes
Combine filters across columns
View and remove active filters easily
This enhancement is enabled on most pages, including Workflows, Forms, HTML Designer, Document Requests, Campaigns, User management, Permissions & roles, and more.
Document Analyzer
📄 View and edit STP document analysis
Agents can now access and review results from Straight-Through Processing (STP) in the Document Analyzer interface. Until now, STP did not provide a URL for entering the Document Analyzer interface—this update adds a URL to the Document analysis completed event.
When agents enter the interface, they can:
View STP analysis outcomes
Override decisions (attributes, signatures, rules)
Reclassify pages and trigger reanalysis
Submit updated document packages
When changes are submitted, a new event is generated to reflect modifications such as updated attributes, signatures, rules, or classifications. This ensures full visibility and auditability of adjustments made after STP processing.
🚫 Missing data policy update
Missing data in document extraction will now be treated as NULL instead of False, ensuring more accurate rule evaluations. Previously, missing values were interpreted as a failed condition, which could incorrectly disqualify a document package.
With this update:
If a required value (e.g., customer’s age) is not found, the system treats it as unknown, not as a failure.
Rules will only fail when actual extracted data violates the condition (e.g., age below the threshold).
Missing data will be clearly indicated in the Document Analyzer UI, so agents can easily identify and address gaps before submission.
This distinction improves compliance logic and prevents false negatives caused by incomplete data.