4.3.0

• A new Effects section has been added to the Styling Panel, allowing you to apply opacity, outline, transform, filter, transition, and animation (looping/entry) effects based on states (Hover, Pressed, Focused, Disabled).
• To enable integration with Kuika Agents, the Agent Chat and Agent Custom Dashboard elements have been added to the Kuika Agents Integration category.
• In the Date Time element, navigation between selection fields using the Tab key has been enabled.
• An option has been added to Chart elements that allows the maxYAxisValue value to be automatically calculated as a certain ratio (e.g., 1.2, 1.3) based on the maximum value in the dataset.
• A “Year” view has been added to the Calendar element, in addition to the day, week, and month views.
• Calendar element now supports displaying images, such as personnel photos, on an event basis (e.g., in the Annual Leave template table).
• Added the DesignerReport.componentDatasourceSummary field to the UI Designer build output, which reports, in a structured format for each Data element, whether it requires a datasource, whether it is connected, and the datasource type.
• In the Helpdesk ticket listing screen, the “Creator/User Who Created” filter, which allows filtering by the user who first created the ticket, has been added, and the relevant user’s name is now displayed in parentheses in the ticket title.
• In the Bar Chart element, the Stacked feature has been added, which allows bars in the same category to be displayed stacked on top of each other rather than side by side.
• In the Bar Chart element, a Custom option has been added for the Color field, allowing a static color to be specified in addition to the dynamic (Column) option, and it is now possible to enter the series name displayed in the Legend/Tooltip as static text instead of the column name.
• In the Bar Chart element, numbers on the Y-axis and in the Tooltip are now formatted according to the application language.
• In Chart elements, when the “Max Y Axis” property is not specified, the Y-axis is now automatically determined by rounding based on the Y-axis increment.
• In Charts, X and Y-axis values are now automatically formatted according to the application language (period/comma separator).
• In Workflow screens, it is now possible not only to create a new “managed” screen for a step but also to connect an existing, externally designed screen as “unmanaged” with the ProcessStepScreen role.

Data Sources

• Python, Java, Go, and Rust data sources have been added.
• A “Browse Data” screen has been added to the application’s Preview Database to allow for mock data entry and manipulation via the platform interface.

Report Designer

• When color and size are specified for the “Label” element using formatting tags, fixed or manually entered text now displays in a formatted (rich text) style in both the canvas preview and the PDF output.

Process Automation

• Symbol Picker now allows Process Initiator information to be selected not only as “FullName” but also as separate fields: Mail/Email/Username, FirstName, LastName, and FullName.

System Actions

• The GetMultipleReportsBase64 action has been added, enabling one or more reports to be combined into a single PDF file.
• The ability to add an internal route or external URL to the payload of the Send Push Notification action has been added, and when the notification is tapped, users on Android and iOS are now redirected to the relevant address (in-app deep link or external browser) with the same behavior.

AI

• The Builder mode has been added to the AI Chatbot.
• In the validation panel in the footer, alongside errors that can be corrected by AI—such as a required action parameter left blank—a “Fix with AI” button has been added. Above the panel, a Fix all with AI (N) button has been added; when clicked, it opens a new chat tab in Builder mode where the AI links the relevant parameter to the appropriate component or value and summarizes the result.

‍

UI Design

• Screens created via “Create a screen” from within a folder are now automatically added under the relevant folder, rather than to the general list outside the folder.
• Actions attached to a screen can now be enabled/disabled during use.
• When a large number of key-value pairs are added to the Select Box’s Add Fixed Data Modal, a vertical scroll bar is now added so the modal fits on the screen instead of the modal height exceeding the screen’s height.
• In the Screens panel, when a new screen is created from within a folder, it is now created under the relevant folder—similar to DB actions—rather than in the general list.
• In the Calendar element, event icons (e.g., new, old, edit) can now be changed.
• In the Calendar element, in addition to the Day, Week, and Month views, a “Year” view has been added, and the ability to add images/visuals to events (e.g., displaying an employee’s photo on a per-event basis in the Annual Leave template) has been enabled.
• The Text Direction property in the Table element’s Header has been hidden in mobile projects since it is not supported there.
• In mobile applications, an optional cache mechanism that can be enabled or disabled on a per-page basis has been added; this ensures that data is retrieved from the existing cache—rather than being reloaded—when navigating between different pages.
• In the Big File Upload element, a feature was added to the right panel that allows restricting file extensions such as “.pdf” and “.png” during file upload.
• The Bar Chart Data Source panel was redesigned with separate tabs labeled “Series 1,” “Series 2,” and “Series 3” to clarify which field belongs to which series.
• Elements and system actions were separated and listed individually.
• The issue where the visibility property did not work in table columns has been resolved.

Data Sources

• In the mobile app, after logging out, the KDevice record is now deactivated rather than permanently deleted, ensuring the Device Token is preserved.
• In the SQL Editor (SQL Action screen), the display of tables, columns, and keywords in IntelliSense has been improved and made more user-friendly.

Process Automation

• FE (Front-End) validation has been added to prevent the use of C# keywords such as “string” and “int” as parameter names.

System Actions

• In addition to the existing user-based notification delivery, support for user-independent, device-based notifications and broadcast notifications to all devices has been added to the Send Push Notification action.
• Tags added to actions are now displayed in the action header, eliminating the need to open and check each one individually.
• The optional “TriggerParentAppGoBack” parameter added to the “Go Back” action now remains visible in web projects containing micro apps but is hidden in mobile projects.
• The return value of the Send Mail action has been improved to return a SendMailResult DTO (Data Transfer Object) containing detailed information such as success, status, provider, messageId, sizeBytes, and receivers, rather than a single Boolean value.

Platform and Platform Interface

• An “Modified” field, showing when the last change was made to a project, has been added to the project list on the Apps page.
• The interface of the New App and Projects screens has been updated.
• Across the Kuika platform (excluding generated apps), the sign-up flow has been disabled, except for the invitation flow. Going forward, you can contact us via the demo form.

AI

• In the AI Chatbot, the positions of the arrows in the process design have been improved.
• In the AI Chatbot, label placement has been improved, even though the default branch of the Exclusive Gateway can be added.
• In the AI Chatbot, when given a single-line, vague brief, the system now asks logical questions and provides guidance.

UI Design

• The issue where clicking the Navigate action via a menu item to a MasterPage screen configured as a modal caused the screen to open in full-screen mode instead of as a modal has been resolved.
• In tables with a large number of rows, the scroll position now remains at the user’s current row instead of always scrolling to the bottom.
• In on-premise installations, the issue where the “Export” button added to tables did not perform any action when clicked has been resolved.
• The issue where data would not appear in the table even if the Labels within a TableTemplateColumn had no visibility conditions, despite a visibility condition being applied to the TableTemplateColumn itself, has been resolved.
• The issue where the input fields used for searching were not displayed when the “Searchable” feature was enabled in a Table has been resolved.
• The issue where the border appeared distorted due to the border-radius value defaulting to 3 in the MD Editor element has been resolved.
• The issue where values could not be assigned using the Set Value Of function after any editing was performed on the MD Editor element has been resolved.
• The issue where line breaks were not preserved in text saved in the MD Editor—due to single Enter keystrokes being completely ignored and double Enter keystrokes behaving like a single Enter—has been resolved.
• The issue where the screen appeared duplicated when moving from one folder to another has been resolved.
• The issue where nodes did not fit completely and their names were not visible when printing to PDF using the Node Tree element’s PDF feature has been resolved.
• The issue where the DefaultDataField property in TableTemplateColumn was lost when adding a Panel inside a TemplateColumn and a Label inside the Panel in the Table element, When a table field was bound to a Panel via DynamicBackGroundColor, the DefaultDataField could not be displayed, causing the Sorter and Search properties to fail in the relevant column; and when two Labels were present within a Panel, the field bound to DynamicBackGroundColor was indirectly displayed within the DefaultDataField—these issues have been resolved.
• The issue where, when attempting to make edits to an existing screen (“do/add … to this page”), the Pipeline would unnecessarily attempt to create a new screen with the same name as the existing one—and this attempt would fail—has been resolved.
• In mobile apps, the issue where the system time was displayed instead of the incoming data when time data from SQL was assigned as the value to a Label and the Formatter was set to “Time” has been resolved.
• In mobile apps, the issue where a Visibility Condition defined via a Guid or String-type column in Text Input and Text Area elements did not function correctly—as it does in the web environment—causing the element that should have been visible to remain hidden has been resolved.
• In the Android app, the issue where the screen would crash when there were too many elements on a single screen has been resolved.
• The issue where the app would throw an error when attempting to open the details of a newly created ticket in the Helpdesk has been resolved.
• In the Master screen, when the right/left padding values of a Column element in the Left Menu were set to 0, the issue where the Left Menu would completely disappear after a page refresh when the Hamburger Menu was active has been resolved.
• The issue where a white background was automatically added to the Header by default when there were too many rows in a table has been resolved.

Data Sources

• In the search screen (Ctrl+F) opened via C#, the issue where tooltips would not close after the search was closed but would continuously trigger and flicker has been resolved.

Email Builder

• When an image was uploaded to a mail template, the issue where images were uploaded to the Unlayer side and emails were sent with errors as a result of these images being deleted has been resolved.

Process Automation

• The icon was changed to prevent confusion with the “more options” icon in the Buttons panel.
• The issue where border settings for the top, bottom, left, and right directions could not be adjusted separately in Box and Vertical Panel elements (due to the relevant fields being disabled) has been resolved.
• The issue where no warning was displayed in the diagram when the user task screen was missing in process design has been resolved.

API Builder

• The issue where an error occurred when an API named “Kuika” was found has been resolved.

Configuration Manager

• The issue where a non-user-friendly warning message was displayed in Configuration Manager and Email Builder when the Name field was left blank and the “Create” button was clicked has been resolved.

System Actions

• The issue where language selection information was saved to Local Storage but not written to the database when the “Set Language” action was executed has been resolved.

Platform and Platform Interface

• On the “Projects” screen, the border-radius values (4px for images, 8px for icons) were standardized when both images and icons were used as app icons.
• The issue where an “update” message was displayed when taking a preview again from a previously saved preview, even though no tab was open, has been resolved.

AI

• The issue where the AI Chatbot design assistant interpreted the “enable dark mode” command as a background change by creating a new screen instead of applying it to the theme has been resolved.
• The issue involving the creation of buttons that did not perform any actions when using system actions has been resolved.
• The issue where UI elements did not align with each other in multi-page designs and the master screen was not used has been resolved.