3.6.0

UI Design

• The ability to develop platform-specific widget packages has been added. With this feature, a new widget package can be created using the npx create-kuika-widget command through an interactive shell. During the creation process, users can:
  
  • Determine the TypeScript-based package structure
  • CSS, SCSS, or Tailwind styling options
  • React, Vue, Angular, or Svelte framework infrastructure.
  • Once the widget development process is complete, widget packages can be imported into the Design Platform using the yarn run publish command.
  • Imported Widgets can be used by dragging them into the design from the Widgets category under the Elements panel.
• With the new ReadOnly feature added to the Pivot Table element, the table can now be used in read-only mode. When this feature is enabled, no cell or structure on the Pivot Table can be edited; the table is opened for viewing purposes only.
• Thanks to the new Export feature added to the Pivot Table element, created tables can now be downloaded in .xlsx format. When this feature is enabled, users can export the data on the Pivot Table to an Excel file with a single click. The Export button is disabled when the table is empty and the download process is not initiated.
• Two new features, minTime and maxTime, have been added to the Calendar element.
  
  • Calendar Week and Day panels can only display the desired time range.
  • The minTime and maxTime values are empty by default; if minTime is not set, 00:00:00 is used as a reference, and if maxTime is not set, 24:00:00 is used.
  • When values are defined, the calendar view is limited to only show hours within these two time ranges; when the values are deleted, it reverts to the default full day view. With this development, the hour-based grid view has been activated in the Week and Day panels, and the time locations of events are presented in a clearer and more readable way.
• The ability to sort data in the Fixed Option Data creation field within the Select Box element has been enabled.
• The WritingMode (Text Direction) property has been added to the Label element. Label texts have been configured to be displayed in Horizontal or Vertical direction.
• AutoPlay and AutoPlaySpeed features have been added for the Carousel element in Android applications.
  
• A ShowPageIndicator has been added to the Carousel element; the total number of items in the carousel and the active item index are displayed as a numbered counter in the lower right corner.
• The ShowPageIndicator feature has been added to the Horizontal Grid element in Android and iOS applications. Thanks to this feature, a numbered counter displaying the page/index information within the grid is displayed in the lower right corner of the HorizontalGrid.
• A default zoom value can now be defined for the Maps element. When the map is first loaded, it opens with a close-up or distant view at the specified zoom level. The valid value range for the zoom feature is limited to 0–22; 0 represents the furthest zoom level, and 22 represents the closest zoom level.
• Support has been added for adding Progress Bar and Progress Circle to the Table element for web applications. Progress statuses, such as completion rates, can be displayed visually within table cells; Progress Bar and Progress Circle elements can be dragged and dropped into the table.
• Support for the Current UserName, Current FirstName, Current LastName, Current FullName fields in the User list added under Current in Elements has been enabled in iOS and Android applications; additionally, the Current RoleNames field has been added for iOS applications.

Datasources

• A “Test Agent” step has been added to the AI Agent creation process, allowing the agent to be tested before completion.

Process Automation

• The Workflow Multi-Instance structure has been developed to support the selection of Parallel Multi-Instance (PMI) and Sequential Multi-Instance (SMI) strategies at the User Task and System Step levels.
  
  • In this context, when the relevant Step is clicked, the wrench (settings) icon in the context menu that opens allows you to select PMI (horizontal three lines) or SMI (vertical three lines); the selected strategy is saved during the design phase and applied exactly in Runtime.
  • In the PMI strategy, all instances are started simultaneously; when a defined Cancel Condition or threshold value is met, the remaining instances are automatically terminated, and only the results of the completed instances are included in the Aggregation.
  • In the SMI strategy, instances run sequentially; when the specified threshold or condition is met, the multi-instance ends, no new instances are created, and the result of the instance that meets the condition is included in the Aggregation.
  • For both strategies, edge-case scenarios such as the instance count being 0, the Cancel Condition being 0 or greater than the instance count, aggregation not being defined, or the Instance Output being null are handled consistently and without error. The development supports the Majority, SumInt, SumDouble, AverageDouble, Min, and Max aggregation strategies; early termination, instance cancellation, and the seamless transition of the Workflow to the next step are guaranteed.
• The compliance of BPMN diagrams created in Workflow Designer with the rules can now be checked instantly using the client-side validation mechanism. With this development, the visibility of errors and warnings can be managed via a toggle (on/off) button added to the lower left corner of the Process Automation screen.
  
  • For elements that violate the rules, a warning (exclamation mark) or error (cross) icon is displayed in the upper left corner of the element; only the exclamation mark is used if there is a warning, and the cross icon is used if there is an error or both an error and a warning. When the cursor is placed over the icon, the description of the violated rule is displayed via a tooltip.
  • Validation rules work consistently with changes made in the designer, and the same validation logic is applied during the preview/export phase. In this context;
    
    • Default path and condition requirement (gateway-conditions) in Exclusive Gateways,
    • Merging of Parallel and Inclusive Gateway branches of the same type in a join Gateway (gateway-join-matching),
    • Gateways not being used as split with a single output (gateway-min-outgoing),
    • Tasks and similar steps not being empty or having only a whitespace Label (label-required),
    • All Nodes having at least one incoming or outgoing connection (no-isolated-flow-nodes),
    • Basic BPMN and platform rules such as assigning a screen to each User Task (screen-assigned) and having at least one StartEvent and EndEvent in the diagram (start-end-required) are controlled.

System Actions

• A validation mechanism for the use of collection name has been added to Vector Search operations.
  
  • When searching with a single collection name, if the collection exists, the operation is completed successfully; if the collection name is incorrect or has not been created, a red warning is displayed with the error “Collection ‘collection_name’ not found”.
  • When searching with multiple collection names, the search operation is only successfully performed on existing collections.
  • Incorrect or missing collection names are listed under the notFoundCollections field in the response DTO so that the user can handle them using the notification mechanism if desired.
  • Users can use this field in the generated app according to their own scenarios (e.g., notify, display warning message, etc.).
  • At the same time, the isSuccess parameter returns true if the notFoundCollections field is full and false if it is empty.
  • Additionally, if the Source download process fails for any reason, feedback is provided to the user via a warning email indicating the error status. Emails are only sent if mail settings are configured in the system; no emails are sent in environments where mail settings are not defined.

UI Design

• The green Completed message that appeared during preview while generation was in progress has been removed and replaced with a yellow Preview busy warning.

System Actions

• The Change Two Factor Authentication Type action has been improved to be int/enum-based, supporting the options Mail, App (OTP), or No Authentication for the user, and No Authentication (2) has been added to allow direct login by bypassing TFA.
• In Android applications, a spinner was added during the wait for the Navigate To Task action, making the loading process more user-friendly.

UI Design

• The issue where the SlidesToShow value set in Designer was not taken into account on mobile devices for the Horizontal Grid element used in Android and iOS applications, and the view defaulted to 4, has been resolved.
• The inconsistency that occurred when previewing the background color specified for a screen via Styling Panel → Fill > Color, even though it was applied correctly in Designer, has been resolved.
• The issue that prevented the project from being generated when a space or Turkish character (via copy-paste) was used between two words in the tag name field has been resolved.
• For elements removed from the table but with remaining value assignments via the current row reference, validation is now shown in Designer instead of generating an error during code generation.
• The issue causing the SQL Edit screen to open by mistake when selecting AI Agent from the Custom Actions list in Screen Design has been fixed, and the correct edit/popup behavior is now applied for the agent.
• The issue causing the background to appear incorrectly when using the Micro App element in full screen mode has been resolved.
• The issue causing inline edit icons to appear at the beginning, despite the template column being preferred in nested tables, has been resolved.
• The issue causing the   character to appear in Label and Input elements, particularly due to Placeholders containing excessive spaces, has been resolved.
• The issue causing the width and height values of the Image element defined in the UI Designer to be generated as maxWidth and maxHeight in iOS applications has been resolved.
• The issue causing the Image uploaded to Android applications to be displayed in low resolution has been resolved.
• The errors occurring when pulling parameter-containing data via SQL Action in the Select Box element in iOS and Android applications have been resolved.
• In Android applications, errors that caused Actions set to the Datasource and changing the result according to the parameter to not retrieve the correct Items when the Searchable feature was enabled in the Select Box element have been fixed.
• The problem of the SQL Edit screen opening when redirecting to Agents via Custom Actions has been fixed.
• The error related to connecting data to the Marker Pop-Up field in the Maps element via Datasource has been fixed.
• The issue of the width value of the Progress Circle element being applied incorrectly in Android and iOS applications has been fixed.
• The issue causing a code build error related to the Tab element in iOS applications has been fixed.
• In iOS applications, the TabHeader area was aligned to the left, causing excess space on the right; this has been fixed and centered.
• The issue causing mismatches in the Breadcrumb element in web applications due to screen name case sensitivity has been resolved.
• An issue that occurred when applying a border to the Image element on the Android apps has been fixed.
• An issue with the Floating Button element on the Android apps in projects without a Header and Footer has been fixed. 
• An issue causing placeholders not to appear in the SelectBox element on the Android apps has been fixed. 
• An issue where conditional-based data failed to load in the SelectBox element on the Android apps has been fixed.

Data Sources

• Issues encountered when retrieving .first and .last items from the Datasource in iOS applications have been resolved.

Report Designer

• Bug fixes have been made for the Box element.

Email Builder

• The restriction causing an error in the Workflow Engine (wfengine) when parameters defined with “@” were used in multiple places in Mail Templates has been removed.

API Builder

• The code generation error that occurred when an Input added to a method was used within the action condition has been fixed.

System Actions

• The issue causing the height parameter given in the Navigate action to not be applied correctly in modally opened screens has been fixed.