/
24.2.2026

3.8.0

Attention Points

  • In multi-step forms, mandatory field checks are now performed on a step-by-step basis; if information is missing, the user is automatically redirected to the relevant step. Current step transition configurations should be reviewed.
  • Since the backend outputs generated by Vision Actions are based on the Python/FastAPI architecture, the compatibility of environment and deployment settings should be checked.
  • New tools added to the AI Agent (Google Flight, LinkedIn, Instagram) should be tested in existing scenarios in terms of data flow and authorization.
  • Since API Builder now accepts multiple records (Arrays), existing service mapping configurations should be checked.
  • Save Action Source configurations used in Vector Search (RAG) integrations should be carefully designed in terms of key fields, metadata, and data update strategy.
  • The limitation and status monitoring mechanism added to the Save Source action may produce different results compared to previous versions in intensive and concurrent operations.
  • The offline synchronization behavior on the web side has been made compatible with mobile; projects with automatic sync flows should be revalidated.
  • Domain-based access policies should be updated due to the migration of preview publishing addresses to the kuika.io domain.

Critical Updates

  • With the Vision Actions module, object detection and tracking scenarios can now be designed in a workflow logic and backend code can be automatically generated via camera and video streams.
  • The AI Agent infrastructure has been expanded with new tool integrations; flight search, social media data extraction, and the ability to save MCP outputs directly to the database have been added.
  • Thanks to the Save Action Source action, action outputs can be transferred to the vector database and made available for use in RAG scenarios.
  • The Method Inputs structure in API Builder has been expanded to offer Manual and Dynamic (JSON-based) parameter definition support, Array (multi-line) data structure, and automatic type detection support.
  • The Video Player in mobile applications now supports videos in base64 format.
  • Connection strings for external data sources are now stored encrypted.
  • DateTimeOffset fields in agent response models have been made optional.
  • The offline working logic has been standardized in web, mobile, and desktop applications.

Actions to be taken

After this release, it is recommended to check the following areas:

  • Step-based form validations
  • AI Agent tool configurations
  • Social media and flight integration scenarios
  • API Builder service mappings
  • RAG and vector data logging configurations
  • Offline scenario tests

New Features

UI Design

  • Validation control has been added to the multi-step use of the Stepper element, and users are now automatically redirected to the relevant step when required fields are left blank.

Data Sources

  • Vision Actions has been added, which can create object identification & tracking scenarios via camera/video streams, works workflow-based, and can automatically generate Python/FastAPI-compatible backend code.
    • The Undo and Redo features have been added to Vision Workflow Builder along with the state management infrastructure.
    • The dropdown components within Vision Nodes have been standardized, ensuring consistency across the interface.
  • Google Flight Tool has been added to AI Agent, and MCP output is now saved to the Database.
    • A user notification has been added stating that flight number and reservation URL information is not supported by the library.
  • LinkedIn and Instagram MCP integrations were added to the AI Agent, and the following Tools are now available in Agents:
    • LinkedIn Profile Search
    • LinkedIn Company Employees
    • Instagram Scraper

API Builder

  • The Method Inputs structure has been expanded to include support for defining Manual and Dynamic (JSON-based) parameters; an Array (multi-line) data structure has been added, and automatic detection of types (numeric, decimal, ISO DateTime, etc.) in Dynamic inputs has been enabled.

Configuration Manager

  • Apify (LinkedIn & Instagram) MCP integration has been added, enabling LinkedIn and Instagram data to be retrieved in JSON format via MCP and used as a data source for AI Agents; API Key definition support has been provided via Configuration Manager.

System Actions

  • The Save Action Source and Remove Point From Action Result actions have been added; this allows action results that return JSON or strings (including DB actions) to be added to or removed from the Vector Search (RAG) system. For results that return objects, the vector field, metadata, and primary key can be selected; Clean & Insert and Insert or Update modes are supported.
  • A rate limit and status tracking mechanism has been added to the Save Source action to prevent repeated and simultaneous operations.
  • Audit logging infrastructure has been added for Client-side Actions in the Authorization category.
  • Multilingual question-answer support has been provided for documents added to Qdrant with the Save Source action; regardless of the document language, the answer is returned in the language of the question asked.
  • The Start Vision Process and Stop Vision Process actions have been added under the Vision Actions category; these actions enable the initiation and termination of Vision workflows defined by them to be managed at the runtime level.

Improvements

UI Design

  • The Video Player element has been developed to support MP4 and Vimeo URLs in addition to the base64 format in Android and iOS applications.
  • By enabling the Step feature in the Percent element, the value can be increased or decreased by the step amount specified using the Arrow Up and Arrow Down keys on the keyboard.
  • The Date Time element in Android applications has been updated to synchronize with the application language.

Data Sources

  • 3rd Party Data Source Connection Strings are now encrypted in the appsettings.json file.
  • The DTO (Date Time Offset) fields returned in Agent Responses are now optional.
  • On the web side, the offline–online DB synchronization behavior has been updated to work based on manual actions, aligned with the mobile side.

Process Automation

  • Explanatory content display has been added to the right panel for the Exclusive Gateway.
  • The assignment logic in the Workflow Multi-Instance configuration has been improved, and the instance count strategy can now be selected based on the assignment.
  • Client-side validation and the visibility, positioning, and tooltip alignment of error/warning icons have been improved for cases such as missing ok, condition, and start–end requirements for Boundary Event, Gateway, and step rules.

Configuration Manager

  • The Service Account JSON file required to retrieve Android subscription information has been separated from Notification.Json and can now be defined separately via Configuration Manager.

Platform and Platform Interface

  • Preview environments are now published via the kuika.io domain instead of the kuika.com domain.

Bug Fix

UI Design

  • The excessive scrolling issue that occurred when the Tab Position property of the Tab element was set to Left/Right has been resolved.
  • In the For Each action used within Table, the Current field has been extracted as “For Each Current,” and the issue of this field being caught in validation has been resolved.
  • The issue of receiving an error in Preview when no Process Instance value was given for the Process Automation Viewer element has been resolved.
  • The transition of the Python service to FastAPI has been completed, resolving the issue of context mixing when multiple users initiated agent/text-to-app flows simultaneously.
  • The issue of delete/copy/duplicate operations not being visible in some Rows and Columns has been resolved.
  • The issue causing the Horizontal Grid element to behave differently in iOS apps compared to Android and Web has been fixed.
  • The issue causing the MD Viewer element to throw a component error and not be selectable via canvas has been fixed.
  • The issue causing inconsistency in list loading between Android and Web when ID and/or Field to Display are null in the Select Box element has been fixed.
  • Fixed an issue in the Stepper element where the center line appeared as a solid blue instead of the Active/Finished Step Color when steps were passed, and ensured that it takes the Finished Step Color value.
  • Fixed an issue in the Text panel where, after entering the Font Size value, if the unit type was not changed, it appeared as “px” but was reflected as pt in the application, causing styling differences between projects.
  • In web applications, the issue in the Shadow Hex code input field in the Styling panel and in the Default style settings has been fixed.
  • In the Select Box element with the Searchable feature enabled, the issue of the onChange event being triggered when opening and closing without making a selection has been fixed.
  • The issue where pressing the Enter key in single-line Text Input and Email elements in Android applications would move to the next line and cause data access problems has been resolved.
  • In the Web View element, the problem of automatic border and radius being applied even though there was no border definition has been resolved.
  • The problem of spaces not being preserved in fixed texts entered from the value field in the Label element has been resolved.
  • The issue of the Step property being non-functional in the Percent element has been resolved, ensuring the step value works correctly.
  • The issue of the onSelect Event returning empty and not triggering in the Tree element has been resolved.
  • The overflow and positioning issues of the selected element menu have been resolved.
  • The issue where conditional visibility rules in Horizontal Grid, Content Menu, Carousel, and Gallery View prevented building and caused incorrect behavior on Android/iOS has been resolved.
  • The issue where onChange was triggered even though Set Value was closed in Pagination, and both pagination change and the associated action worked together in the same interaction has been resolved.
  • The issue of not being able to update styling on existing screens (approximately 12 forms) due to the detach feature of the Form element being disabled on screens created with CRUD, and the inability to adjust the responsive column break in forms called within the Drawer, has been resolved by reactivating the detach / duplicate / paste style features of the Form element.
  • The incompatibility between the Label and Select Box elements in Date Time format has been resolved, ensuring consistent format across both components.

Data Sources

  • The issue causing Mac keyboard shortcuts (Option + 3/4/5, etc.) in SQL and C# Editors to switch tabs and cause written content to disappear has been resolved.
  • The issue preventing the application from starting when a SAP data source was added but no action was defined has been resolved.
  • The type mismatch and associated startup error that occurred when using [first] on the interface side due to functions marked as List in the SAP definition screen being generated as Array in the backend source code has been resolved.
  • The issue of half of the screen area not being used in the AI Agents Input Pop-up has been fixed.

Process Automation

  • The error that occurred when using “Current URL” in the Condition panel has been fixed.
  • The vertical alignment issue of the Instance Count Strategy dropdown icon (PMI/SMI) in the Workflow Multi Instance Assignment screen has been fixed.

Report Designer

  • The calculation issue that occurred when using colspan/rowspan in Static Table columns added from the Operations section has been resolved.
  • The padding problem visible on the selected Static Table in Designer has been fixed.
  • The Merge Cells operation in Static Table has been rechecked, and the issue of shifting and width distortion in the output has been resolved.

Scheduled Jobs

  • The issue where the Slack Post Message action in the Scheduled Jobs module caused an error and could not be saved when a fixed value was entered in the message field has been fixed.

Configuration Manager

  • The issue where the JSON file added under Play Store Settings was not saved/was lost has been fixed.

System Actions

  • In the Share action, the issue of content being written to the mail body field during VCF sharing and appearing both in the body and as an attachment has been fixed in the Web and iOS applications.
  • In the Web and mobile applications, the issue of Page Init not working after Go Back when “Current Page” is selected in the Navigate action has been fixed.
  • The issue where the Add User to Role and Remove User from Role actions did not return a response value in Preview has been fixed, ensuring they return true/false values consistent with the boolean behavior in Designer.
  • The issue where the Get Mobile App Subscription Detail action returned a request error when fetching subscription details in Android and iOS applications has been fixed.
  • The inconsistency causing incorrect behavior of if conditions due to the boolean appearing in Designer but not returning a response in Preview/Explorer during Add User to Role / Remove User from Role actions has been resolved, making the response behavior of these methods consistent across environments.
  • In iOS applications, the issue causing the spinner not to appear while the Mobile App Activate Subscription action was running has been resolved, ensuring that the loading indicator is displayed while the process continues.

Platform and Platform Interface

  • The issue causing the hash code to change when exporting Source Code with different configurations has been resolved; Startup.cs content has been updated to not be included in the hash calculation, ensuring that code downloaded with different configurations in the same project has the same hash.
  • The issue causing the page to go blank when the Click event was triggered in the Error Panel message has been resolved.