/
21.5.2026

4.1.0

Attention Points

  • The newly added Secure Screen setting for screen capture and video recording control in Android apps may affect the default behavior; it is recommended to review configurations in relevant projects.
  • Since support for the Scan Barcode action has been added in web projects, it is recommended to retest platform-specific controls in existing barcode scenarios.
  • The AI Chatbot file upload area now enforces a 10 MB limit per file. If the limit is exceeded, the relevant files will not be uploaded; only files of the appropriate size will be processed.
  • Namespace Scope validation has been enabled for C# Custom Action Result usage within the For Each action. Structures must be checked to avoid validation-related errors in existing flows.
  • Some InstanceID usages under “Common” in the Condition modal have been restricted. Updates may be required for legacy implementations.

Critical Updates

  • The Radio Group Button element is now supported in Android and iOS apps.
  • Gradient Fill Style support has been added for mobile projects.
  • The Secure Screen feature has been added for Android; screenshot and video recording behavior is now manageable.
  • The Scan Barcode action is now available in web projects.
  • The Action Paste feature has been added to the If Then Else action.
  • When multiple screens are created on the AI Chatbot side, all created screens—not just the last one—are now reported in the chat.
  • Performance and stability improvements have been achieved by creating the necessary indexes for the WF Engine in PostgreSQL and Oracle databases.

Actions to be taken

  • In Android projects, reconfigure the Secure Screen setting to be active or inactive as needed.
  • Test the Scan Barcode action flows for barcode scenarios to be used in web projects.
  • Check the C# Custom Action Result structures used within For Each for compliance with Namespace Scope rules and perform the necessary migration steps.
  • In projects using the AI Chatbot, update file upload processes in accordance with the new 10 MB file limit.
  • Review existing workflows and condition structures against the usage restrictions for InstanceID in the Condition modal.
  • If you are using the new Gradient Fill Style support in mobile projects, re-run application tests.

New Features

UI Design

  • Support for the Radio Button Group element has been added to Android and iOS apps.
  • Gradient support has been added to the Fill Style in mobile projects.

Configuration Manager

  • A “Secure Screen Mode” toggle has been added to the Android tab to control screen capture and video recording in Android apps.

System Actions

  • Support for the “Scan Barcode” action has been added to web projects.
  • The “Action Paste” feature has been added to the “If Then Else” action.
  • Validation has been added to ensure that when using a C# Custom Action Result within the “For Each” action, the Data Source must be moved to the Namespace Scope.

Improvements

UI Design

  • System error messages are now displayed in a copyable format in Platform Designer.

Data Sources

  • The feature allowing the selected query to be run using the TEST button in the SQL Editor has been enabled.

Process Automation

  • In the Process Automation creation screen, action-less icons in the right panel have been improved to display in a disabled state to prevent user confusion.
  • In the Screen Wizard, the modal now closes automatically after clicking the Save button.
  • In the Condition modal, the use of InstanceIDs under “Common” has been restricted.
  • The necessary indexes for the Workflow Engine have been created in PostgreSQL and Oracle databases.

Platform and Platform Interface

  • The ability to cancel Preview, Export, and Get Source Code operations after they have been initiated has been implemented.

AI

  • When multiple screens are created with the AI Chatbot, all created screens are now reported in the chat instead of only the most recently created screen.
  • The text “Max 10 MB per file” has been added to the file upload field in the AI Chatbot. While files exceeding the size limit are not added and a red warning is displayed, the ability to continue adding files within the limit has been enabled.

Bug Fix

UI Design

  • The issue where pagination remained fixed when scrolling the Table element has been resolved.
  • The issue of misalignment in group headers within the Table element has been resolved.
  • The issue where updates did not reflect in the table after a selection was made in the Select Box has been resolved.
  • The issue where both the “Process Automation” and “Process Automation Viewer” labels appeared nested within each other in the Process Automation Viewer element has been resolved.
  • The issue where the “Slides To Scroll” feature did not work properly in the Horizontal Grid element in Android apps has been resolved.
  • The issue where data written within parentheses in the Value field of the Label element was not displayed with the parentheses has been resolved.
  • The issue where the selected panel view (day/week/month) in the Calendar element was not correctly reflected in the designer canvas and Preview has been resolved.
  • The issue where an Image-type column was not recognized as empty when a record was saved without signing in the Signature element has been resolved.
  • The issue where the background color disappeared during hover when the Striped and Row Hover BgColor properties were used together in the Table element has been resolved.
  • The issue where the Node Tree element overlapped the toolbar drawer has been resolved.
  • In the iOS app, the issue where the MultiSelect element returned the key instead of the value in the OnChange and OnSelect events has been resolved.
  • In Android and iOS apps, the issue where selections could not be cleared using Set Value Of (null) in the MultiSelect element has been resolved.
  • The issue where the text does not appear on the button when only a numeric value is entered in the Label field of the Button element has been resolved.
  • The issue where the placeholder font weight for the Number Input is different (medium) from other input elements has been resolved.
  • The issue where the Range Slider element could not be dragged in Android apps has been resolved.
  • The issue where the Switch element appears closed in the designer when Fixed Value is set to “true” has been resolved.
  • The issue where using “IF” within a Recurring Action in iOS and Android apps resulted in the generation of multiple methods with the same name during code generation and caused an error during export has been resolved.
  • The issue where, in Android apps, the screen’s Page Init would wait until the Recurring Action was triggered when the “Trigger on PageInit” property of the Recurring Action was set to false on the Master Screen has been resolved.
  • The issue where the “Sometimes Enabled” property in a Table applied to the wrong rows despite the condition matching has been resolved in Android apps.
  • The issue where the value was assigned as a fixed value instead of the placeholder text when editing a Label element by double-clicking on the designer canvas has been resolved.
  • The issue where changes made to text color, text size, text style, and font family in the Styling panel of the Multi Select element were not applied has been resolved in Android apps.
  • The issue where selected items in the Multi Select element triggered the onChange and onSelect events while the page was loading in Android apps has been resolved.
  • The issue where row colors became distorted when the rowHoverBgColor property was active while using Dynamic Background Color in the Table element has been resolved.
  • The issue where the rounded appearance was lost for single-character values in the Badge element has been resolved.
  • In iOS apps, the issue where the Align Right and Align Middle values assigned to a Column were overridden by Horizontal Stack, causing icons to appear left-aligned, has been resolved.
  • Issues where the Master Layout was not rendered in screens opened as overlays when using the Master screen with Drawer/Modal/Floating Panel, and where Page Init was not triggered after the overlay was closed despite the “Execute Page Init Actions After Closed” setting being active, have been resolved.
  • The issue where the Dynamic Menu in the Master Screen did not load in iOS apps has been resolved.

Data Sources

  • The issue where scrolling was not possible on the Data Source addition page has been resolved.
  • The issue where JSON output subfields were not visible during parameter selection in AI Actions created with OpenAI models has been resolved.

Configuration Manager

  • The issue with case sensitivity during configuration searches has been resolved.
  • The issue of receiving a 404 error during logout with MSAL (EntraID) has been resolved.
  • The issue where the required adi-registration.properties file for package name ownership verification was not included in the APK when publishing Android apps to the Google Play Console has been resolved.
  • The issue where the Billing Manager permission could not be created and in-app purchases could not be processed due to changes in the Configuration Manager structure in Android apps has been resolved.

Platform and Platform Interface

  • The issue where HTTP exceptions (including backend mismatches) caused the app to crash on Android has been resolved.
  • The issue where links redirecting to a different project went to the project’s homepage instead of the target page has been resolved.

System Actions

  • The issue where the date value would reset to the current day’s date when the time was changed in the Date Time field transferred via the Navigate action from the Calendar has been resolved.

AI

  • The issue where design could not be performed due to the “Component addition/editing tools are currently inactive” error, and the same error was prompted twice upon proceeding, has been resolved.
  • The issue where menu items in the Menu element were named inconsistently with the pages they navigated to has been resolved.
  • The issue where a red fill color could not be assigned to a Column, even though it was possible via the Styling panel, has been resolved.
  • The issue where the Enter key could not be pressed after clicking the “Cancel Improving” button following “Improve Prompt” has been resolved.
  • The issue where a gradient could not be applied to the Header background and the change did not reflect on the screen, even though brand colors were correctly detected in Styling mode, has been resolved.
  • The issue where the system automatically proceeded without opening the text input field when the “Other (I’ll Write It)” option was selected on the multiple-choice navigation screen has been resolved.
  • The issue where the “Back to the AI Chatbot” button closed only the pop-up instead of redirecting the user back to the Design screen after loading the balance has been resolved.
  • The issue where credits continued to be consumed even after the screen creation process was canceled has been resolved.
  • Turkish natural language navigation has been improved. Commands containing the verbs “go,” “proceed,” “return,” “exit,” “open,” and “show,” along with directional (-a/-e) and possessive (-ı/-i) suffixes added to screen names, now correctly redirect to the appropriate screen. Support has been added for apostrophe usage (“Go to Product”), spelling without an apostrophe (“Go to Producta”), and case sensitivity (“Go to Product’a”).
  • The issue where the horizontal alignment property of the page’s title element was not working has been resolved.
  • The issue where too many rows were added when creating a static table has been resolved.
  • The issue where defining the primary color using a hex code and updating all related elements did not work has been resolved.
  • The issue where the notification dropdown could not be created and a message that should not have been displayed was shown has been resolved.
  • Issues with code generation when an empty object was entered in the Sample Output Data field in AI Action have been resolved.
  • The issue where the operation could not be canceled and the record could not be saved when encountering a “creation failed” error during deletion operations has been resolved.
  • The issue where the screen copy operation repeated multiple times and the “account cannot be accessed” warning appeared has been resolved.
  • The issue where an unsupported feature was reported as successfully added instead of being rejected has been resolved.
  • The issue where an “added” response with details was returned for an unsupported feature request, even though the action was not performed, has been resolved.
  • The issue where the command to add a new column to a table returned a success response but caused an error in the designer has been resolved.
  • The issue where a tooltip could not be added to a button has been resolved.
  • The issue where the Badge element could not be added to the notification icon in the correct position and with the correct value has been resolved.
  • The issue where, when a design suggestion was requested, changes were made directly to the design instead of providing a suggestion has been resolved.
  • The issue where the “Empty State” request created a separate screen instead of being added to the current screen, leaving the Home Page empty, has been resolved.
  • The issue where a drawer opening from the right could not be created has been resolved.
  • The issue where the Breadcrumb element could not be created has been resolved.
  • The issue where a mobile hamburger menu could not be created as a full-screen overlay from the right in a web project has been resolved.
  • The issue where visual areas in the Skeleton card grid were filled with actual images instead of gray placeholders has been resolved.

Authorization & Login

  • The issue where data entered on the login screen was lost and the screen reloaded twice when the app was minimized has been resolved.