-
Notifications
You must be signed in to change notification settings - Fork 5
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
628859b
commit 0dad7a3
Showing
3 changed files
with
76 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,22 @@ | ||
--- | ||
title: V 4.0 | ||
description: ILLA Cloud V 4.0 Changelog | ||
--- | ||
|
||
# V 4.0 | ||
|
||
2023.12.07 | ||
|
||
## π New features | ||
|
||
* Mock data for your actions | ||
* When the API is not ready yet, you can use Mock data for simulation | ||
* Create app from an AI Agent | ||
* By clicking `Create app from AI Agent`, we will automatically set up the interface and data connections between components and the AI Agent. You can then configure the necessary functionalities for your business on top of this foundation. | ||
* Actions for SQL databases types such as MySQL, PostgreSQL, MSSQL, etc., now support the ability to set either Safe mode or Unsafe mode. | ||
* Safe mode: Your SQL can only reference variables in the place of variables, for example, `where name = '{{input1.value}}'`. This prevents users from compromising your database by inputting statements like `'; drop table;'` in input1 | ||
* Unsafe mode: When using the unsafe mode, SQL syntax words can also be replaced with variables, such as `where {{input1.value}} {{input2.value}} '{{input3.value}}'`. However, in this case, the database can be compromised by the content entered by the user. It is not recommended for you to use this mode. | ||
|
||
## π Bug fix | ||
|
||
* Fixed an issue where the Data Grid component would throw an error in certain cases when switching the primary key. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,22 @@ | ||
--- | ||
title: V 4.1 | ||
description: ILLA Cloud V 4.1 Changelog | ||
--- | ||
|
||
# V 4.1 | ||
|
||
2023.12.21 | ||
|
||
## π New features | ||
|
||
* Tags component | ||
* A pill list to display color-coded values. It supports custom colors and deterministic assignment, so each unique tag uses a different color. | ||
* Avatar component | ||
* A content area to display user information and profile image. It supports a range of image sizes, fallback icon if no image is provided, text if no image or icon is provided, and includes a label and caption. | ||
* New column type for data grid | ||
* Added support for Avatar type in the Data Grid component. | ||
|
||
## π Bug fix | ||
|
||
* Optimized server-side pagination for the Data Grid component. | ||
* Fixed the issue with selected data in the List component and Grid List component after switching pages. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,32 @@ | ||
--- | ||
title: V 4.2 | ||
description: ILLA Cloud V 4.2 Changelog | ||
--- | ||
|
||
# V 4.2 | ||
|
||
2024.01.04 | ||
|
||
Changelog - Version 1.2.0 (Released on January 4, 2024) | ||
|
||
## π New features | ||
|
||
**Introducing ILLA Flow**, a powerful automated workflow tool that allows you to build automated workflows quickly and integrate with your business tools. Automate tedious tasks and focus on business. | ||
|
||
Unlike other similar tools, ILLA Flow is specifically tailored to integrate seamlessly with applications built using ILLA Builder, enabling developers to trigger flows directly within their applications. ILLA Flow beta supports the following features: | ||
|
||
* **Workflow Automation**: ILLA Flow empowers developers to automate their workflows, eliminating manual tasks and increasing productivity. By defining triggers and actions, developers can create custom workflows that execute seamlessly. | ||
* **Extensive Trigger Options**: ILLA Flow provides flexible trigger options, including scheduled triggers and webhook triggers. With scheduled triggers, developers can set specific times for flows to execute, offering precise control over workflow automation. Webhook triggers enable developers to initiate flows based on incoming HTTP requests, enabling seamless integration with external systems and services. | ||
* **Broad Action Support**: ILLA Flow offers support for various actions commonly used in development scenarios. This includes integration with PostgreSQL and MySQL databases, allowing developers to perform database operations as part of their workflows. Additionally, ILLA Flow supports REST API integration, enabling developers to interact with external services and perform actions such as data transformation. | ||
* **Seamless Integration with ILLA Builder**: ILLA Flow is designed to seamlessly integrate with applications built using ILLA Builder. This integration enables developers to trigger flows directly within their applications, enhancing the overall functionality and automation capabilities of their applications. | ||
* **Customizability and Versatility**: ILLA Flow is highly customizable, allowing developers to tailor workflows to their specific requirements. With its versatile capabilities, ILLA Flow can cover a wide range of application scenarios, making it suitable for various development projects. | ||
|
||
## π Bug fix | ||
|
||
- Fixed the issue where the selection of events in the audit log was not working properly. | ||
- Resolved the problem causing the default view of containers to become ineffective. | ||
|
||
## π Polish | ||
|
||
- Users now have the ability to change the application name within the app itself. | ||
- Improved data synchronization between the app and the dashboard when making edits to the application name. |