About

June 27 – Release Notes

Explore this week's updates and improvements to Kognitos.

Visual Refresh: A New Look for Kognitos ✨

Kognitos has a new look — We've updated the logo, colors, and typography as part of a visual refresh to better reflect our growth and mission. Everything under the hood remains unchanged — workflows, performance, and behavior are unaffected.

These updates bring a cleaner, more modern experience to the platform that aligns with who we are today and where we’re headed. Learn more here.

New Features

Gemini Models Now Supported in the EU & UK

The platform now supports Google’s Gemini models in LLM automation procedures for the EU and UK regions. You can now specify a supported Gemini model in procedures like extract data to leverage its capabilities for tasks such as document processing and data extraction.

Enhancements

We’ve made the following enhancements to improve functionality and user workflows:

Workflow Improvements

  • You can now filter an agent’s procedures to show only those that have been run, helping you focus on active workflows.

  • Missing credentials for a learned Book can now be entered directly in the Questions panel, streamlining the configuration process.

Improved CSV Tables

  • CSV previews now support smoother scrolling and faster performance on large files.

  • CSV table views have been improved to adapt to your window size and include per-column filtering and sorting.

Process Flow Visualization

  • Flowcharts have been enhanced with larger fonts and improved line spacing for better readability.

  • Diagrams now include a title, subtitle, and step-specific notes, offering more context at a glance.

Bug Fixes

We’ve resolved the following issues:

  • Resolved an issue on the Runs page where the procedure name was displayed incorrectly and difficult to read.

  • Resolved an issue where the Playground editor and visualization panels did not resize correctly when toggling the process flow view.

  • Resolved an issue where inserting a new, empty column into an Excel worksheet would fail to apply the specified column name. The new column will now be created with the correct user-provided name instead of a generic one.

Last updated

Was this helpful?