4.6.0

UI Design

• A new Splitter element has been added to web projects, which divides the screen into two sections—side-by-side or one above the other—and allows the sizes of these sections to be adjusted using a drag handle; support for icons, colors, and aligned columns per node has also been added to the Tree element.
• Manual positioning support for the Icon and Tooltip in the Badge element has been added to iOS and Android apps.
• The Title Font Color property, which allows the color of the table header text to be adjusted, has been added to the Table element.
• A feature has been added to the Document Management System that allows folder names to be defined dynamically in different languages.
• Support for Bar Chart sub-elements—which can be optionally added and displayed grouped side-by-side with other series—has been added to the Mixed Chart element (not yet supported on mobile platforms).
• In the Pivot Table element, a feature has been added that automatically saves user-made view changes—such as adding/removing column fields, adding/removing metrics, and editing—on a per-user basis, similar to the Table element.
• For the Multi Select and Select Box elements, a feature has been added that allows options to be grouped under a header and, in the Multi Select element, enables selected values to be displayed with distinct colors or icons.
• A switch has been added to the Properties panel of the Table element, allowing the “Get Table Config” property to be enabled or disabled. Additionally, the ‘excludeSearchFromTableConfig’ property has been added, which ensures that search information is not included in the user-specific table settings while “Get Table Config” is enabled.

Data Sources

• A feature has been added that allows you to view on which pages and elements SQL Actions are used; this way, you can see in advance where changes made to an SQL Action will have an impact.
• A feature has been added to SQL Actions that allows fixed parameters within a query to be copied automatically with the values displayed on the screen.

Process Automation

• The “Add User To Role” and “Remove User From Role” actions have been added to the “Add Action / Authorization” tab under the Create Task object.
• The system has been developed so that when a user initiates a workflow using “Start Process,” if the first pending (WAITING) task in the resulting process belongs to that user, the user will be directed directly to the relevant task screen without going through the task list. This redirection takes effect if the first user task has been assigned to the Process Initiator via Dynamic Assignment, there are no gateways, subprocesses, or events between the start node and this user task, and the nodes in between have only a single outgoing path. Otherwise, the current behavior remains unchanged.

System Actions

• An option has been added to the Get Component Base 64 action that allows the output to be retrieved in JPEG format as well as PDF format.
• In the “Confirmation” action, a feature has been added that allows the colors of the “Cancel” and “Confirm” buttons to be customized.

Platform and Platform Interface

• The platform’s backend infrastructure has been migrated to .NET 10 without requiring any additional work on existing projects.
• A “Remove” function has been added to the profile photo field in the “My Profile” modal, allowing the current photo to be removed.

UI Design

• In menu items, the tooltip behavior has been improved so that long text that does not fit on the screen can be viewed in its entirety on mouse hover.

Process Automation

• If a workflow version uses the Data Model or Step Logic of a previous version, it now runs without requiring that version to remain live.
• When attempting to delete or modify a field in a Data Type used by live workflow versions, a list of affected versions is now displayed.

• The workflow engine’s infrastructure has been completely overhauled to improve performance; task and process screens and lists now open significantly faster, and the engine’s unnecessary load on the database has been reduced.
• When a workflow step fails, the engine now waits in stages (back-off) instead of continuously retrying the same task; if the issue persists, it safely puts the relevant process on hold. This resolves the behavior where a single failed process would slow down the entire system.
• The behavior where all processes associated with a temporarily inaccessible application would unnecessarily retry, thereby tying up the system, has been fixed; when connectivity is restored, processes resume from where they left off.
• The timeout limit for backend calls in workflow steps has been clarified; the behavior where a timed-out call was interpreted as a persistent failure, leading to unnecessary retries, has been fixed.
• The behavior where a single faulty record would block the entire group while a set of records was being processed has been fixed; the engine now filters out the problematic record and continues processing the remaining records.
• In environments where multiple servers/instances are running simultaneously, a bug in the locking mechanism (particularly in PostgreSQL) that prevented the same process from being executed twice by mistake has been fixed; processes are now executed only once under all circumstances.
• The behavior where a workflow whose definition could not be temporarily loaded caused processes to return nothing on each attempt has been resolved, enabling the definition to be automatically reloaded.
• In task and process queries, the issue causing a 500 error to be returned for a user not found in the system has been resolved, ensuring an empty result is returned instead.
• Missing initial indexes were added to workflow tables, enabling queries to run faster.

BPM Admin Console

• The workflow engine’s administration console was redesigned to provide screens that are easier for operators to read and understand.
• The loading speed of the management console screens has been improved.
• A monitoring feature has been added that allows operators to directly see why the engine is not running a particular process, making it easier to identify potential issues.
• The process history (migration) screen now displays operations in meaningful groups and in an easy-to-read format.

System Actions

• In Bluetooth actions, a validation issue that caused empty or updated/deleted Method Inputs to not cause problems during preview but result in a “build failed” error during the publishing phase has been resolved.
• In the “Set Process Data” action, a validation issue that caused values sent to boolean and GUID-type fields to be processed incorrectly has been resolved.
• The “Add User To Role” and “Remove User From Role” actions have been moved from the client-side to the server-side to enable their use in workflows.
• In the “If Then Else” action, an enhancement was implemented so that a validation error is displayed in the preview only when an action called exclusively within an “If” or ‘Else’ block is used in the “Condition.”

Platform and Platform Interface

• The interfaces of the UI Designer, Data Sources, AI Functions, Email Builder, Report Designer, Scheduled Jobs, API Builder, and Configuration Manager modules have been updated.
• The Helpdesk panel interface has been updated.
• An enhancement was implemented so that when a project is duplicated, the member/role relationships from the source project are also transferred to the duplicate project.

UI Design

• An authorization error that allowed users with the “viewer” role on a project to make visual (styling) changes on the page because the styling panel was active has been resolved.
• An error that caused the first column header in a Table element to appear left-aligned (without indentation) unlike the other column headers has been resolved.
• An error was fixed in the Select Box element where, when the “Searchable” property was set to true and a large font size was entered, the text cursor did not appear aligned with the input field.
• An error was fixed that caused the Select Box and Auto Complete elements to enter validation during page initialization even though no trigger had occurred.
• In the New Screen modal, the issue where the “Field accepts only English letters!” warning message was not displayed when Turkish characters were entered—similar to the behavior in the New Folder modal—has been resolved.
• In Authentication Templates, the issue where the text ‘NaN’ was displayed in the number input field when a screen was created using the “User Template” option has been resolved.
• In the Table Row, the issue where a record had to be clicked twice for the relevant data to appear in the sub-table after performing a search in the table has been resolved.
• In the Slider element, the issue where the labels displaying the slider value failed to maintain their positions when the page was scrolled or when navigating to another page, causing them to remain fixed in the same place, has been resolved.
• The issue where the Visibility Condition applied to columns and labels within the Table element did not work when a Switch value was used—resulting in labels within columns that should have been visible when the condition was met not being displayed—has been resolved.
• In web applications, the issue where a value assigned to a Select Box element via the data source was correct in the background but did not appear as the selected value in the UI has been resolved.
• The bug that prevented values from being entered into a Text Input element in a Template Column within a Table when a Mask value was assigned to it has been fixed.
• The bug that caused the scroll area in the Designer environment to fail to update correctly when the MasterPage Header height was increased has been fixed.
• The bug that prevented the Save action from always being triggered for the relevant row when a Select Box was used with the current row ID within a Table element has been fixed.
• In a Table element with the Multi-Select feature enabled, the bug that caused the Selected Values Count not to update correctly when all rows were deselected—and consequently caused the button visibility condition (the button remaining visible when nothing is selected) to fail—has been fixed.
• The bug that caused the parent screen’s loading indicator (spinner) to remain active until the panel was closed after adding another action to the FloatPanel following a “Navigate” operation has been fixed.
• The bug that caused the element’s Fill color to become distorted and turn a shade close to white when a Gradient was applied to Text Color in the Styling panel—even though the Fill color is supposed to be an independent property—has been fixed.
• In duplicated projects, the bug that prevented the “Search member” dropdown menu from listing workspace members during the “Change Project Owner” process—and consequently prevented the owner transfer from being completed—has been fixed.
• In the Table element, when the Table Width Mode value was set to Horizontal Scroll, the bug causing inconsistent behavior—where the scroll bar would appear and disappear on the screen—has been fixed.
• The bug that caused the MicroApp screen to lose its content and return to the home page when the page was reloaded has been fixed.
• In UI/UX, the bug that caused the left panel to appear wider than intended when closed and reopened across all tabs has been fixed.
• The performance issue causing pages containing Table and Horizontal Grid elements to take a long time to load has been resolved.
• The bug that caused the title of the copied application to remain the same as the original application during the application copying process has been fixed.

Data Sources

• The bug that caused the column maximum length (max length) value to appear as “2000” when “max” was selected in the Oracle data source has been fixed.
• A bug that caused the “String” type to be listed twice in the column type options when creating a table in PostgreSQL has been fixed.
• When adding a new role, an error that prevented the role from being added if the role name already existed in the KRole table with a difference in case (e.g., “TEST” and “test”) has been fixed; since role names are considered identical regardless of case, saving the same role with different case is now prevented during the Designer phase.
• The bug that prevented datasource names—which were truncated with three dots (...) due to their length—from being displayed in full when the left panel was collapsed and then expanded has been fixed.
• The bug that caused the User ID and Password fields to appear empty and disabled when reopening a datasource created in an Oracle data source using “Use Connection String” has been fixed.
• The issue where the “Edit” button did not appear in the Data Sources module when the table name was too long has been resolved.
• The issue where the Symbol Picker failed to work in actions used in a Bluetooth data source when at least one method input was added has been resolved.
• The issue where a migration in one project could affect a table with the same name in another project sharing the same database has been resolved.

Process Automation

• The issue where the application could not be compiled due to older workflow versions in production when a data type name was changed has been resolved.

Configuration Manager

• The issue where a long configuration name caused the editor title to overlap with the platform ribbon, making the “Rename” (pencil) button unclickable, has been resolved.

AI

• In the process of creating database-connected applications with AI, an issue was resolved where column names containing Turkish characters and spaces (e.g., “Proje Adı,” “Not”) could not be written to the database or were saved incorrectly.

System Actions

• In the “Confirmation” added to the “Notify” action under “Page Init,” the bug that caused the screen to get stuck on the spinner when the ‘Cancel’ button was clicked in the preview has been fixed.
• When downloading a report using “Component to PDF,” the bug that prevented icons selected from the icon library from appearing in the generated PDF has been fixed.
• The issue causing icons to appear as text instead of their actual images and images to display incorrectly when exporting to PDF using the “Component to PDF” action in Mac + Google Chrome and Kuika Preview environments has been resolved.
• The issue causing images on pages converted to PDF using the “Get Component Base64” action to not appear in the output has been resolved.
• In the “Component to PDF” and “Get Component Base64” actions, the error that prevented output generation (resulting in a “PDF could not be created” error) when an Image element was selected directly as the target element has been resolved.
• The issue where, in the “Get Multiple Reports Base64” action, dynamically generated report parameters were incorrectly checked when the action was triggered via a button in a table row, resulting in a “field not found” error, has been resolved.
• In web applications, a bug has been fixed where, when the result of an action (such as SAP or C# Custom Action) that returns a list within an object—and is executed within an “If Then Else” action—is bound to the “Select Box Options” field, the Select Box remained empty.

Platform and Platform Interface

• An error has been fixed that prevented a user from being redirected to their own Workspace when they were removed from a Workspace they had been invited to—even if the page was refreshed while the project screen was open (an issue that could only be resolved by logging out and back in).
• On the Team Members screen, the issue where the list ignored the filter text in the search box after a member was invited—causing all members to be displayed (resulting in inconsistencies between the search box text and the listed results)—has been resolved.