diff --git a/.version b/.version
index 23a93836ae..5c18f9195b 100644
--- a/.version
+++ b/.version
@@ -1 +1 @@
-2.24.5
+2.25.0
diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md
index e317567c07..bae56e7799 100644
--- a/CODE_OF_CONDUCT.md
+++ b/CODE_OF_CONDUCT.md
@@ -114,15 +114,13 @@ the community.
## Attribution
-This Code of Conduct is adapted from the [Contributor Covenant][homepage],
-version 2.0, available at
-https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org), [version 2.0](https://www.contributor-covenant.org/version/2/0/code_of_conduct.html).
Community Impact Guidelines were inspired by [Mozilla's code of conduct
enforcement ladder](https://github.com/mozilla/diversity).
-[homepage]: https://www.contributor-covenant.org
-For answers to common questions about this code of conduct, see the FAQ at
-https://www.contributor-covenant.org/faq. Translations are available at
+- For answers to common questions about this code of conduct, see the FAQs at
+https://www.contributor-covenant.org/faq.
+- Translations are available at
https://www.contributor-covenant.org/translations.
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index d5e9f4f00f..fcfc56cc55 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -8,9 +8,9 @@ We love your input! We want to make contributing to this project as easy and tra
## Setup
-[Mac OS](https://docs.tooljet.io/docs/contributing-guide/setup/macos)
-[Docker](https://docs.tooljet.io/docs/contributing-guide/setup/docker)
-[Ubuntu](https://docs.tooljet.io/docs/contributing-guide/setup/ubuntu)
+- [Mac OS](https://docs.tooljet.io/docs/contributing-guide/setup/macos)
+- [Docker](https://docs.tooljet.io/docs/contributing-guide/setup/docker)
+- [Ubuntu](https://docs.tooljet.io/docs/contributing-guide/setup/ubuntu)
## We Develop with GitHub
We use GitHub to host code, to track issues and feature requests, as well as accept pull requests.
@@ -51,4 +51,4 @@ We use GitHub issues to track public bugs. Report a bug by [opening a new issue]
By contributing, you agree that your contributions will be licensed under its AGPL v3 License.
## Questions?
-Contact us on [Slack](https://tooljet.com/slack) or mail us at [hello@tooljet.io](mailto:hello@tooljet.io).
+Contact us [on Slack](https://tooljet.com/slack) or [email us at hello@tooljet.io](mailto:hello@tooljet.io).
diff --git a/README.md b/README.md
index 0b8ca7cd66..c5c31f5db3 100644
--- a/README.md
+++ b/README.md
@@ -1,52 +1,26 @@
ToolJet is an **open-source low-code framework** to build and deploy internal tools with minimal engineering effort. ToolJet's drag-and-drop frontend builder allows you to create complex, responsive frontends within minutes. Additionally, you can integrate various data sources, including databases like PostgreSQL, MongoDB, and Elasticsearch; API endpoints with OpenAPI spec and OAuth2 support; SaaS tools such as Stripe, Slack, Google Sheets, Airtable, and Notion; as well as object storage services like S3, GCS, and Minio, to fetch and write data.
-⭐ If you find ToolJet useful, please consider giving us a star on GitHub! Your support helps us continue to innovate and deliver exciting features.
+ :star: If you find ToolJet useful, please consider giving us a star on GitHub! Your support helps us continue to innovate and deliver exciting features.
-
-[](https://github.com/ToolJet/ToolJet/issues)
-[](https://github.com/ToolJet/ToolJet/stargazers)
-
-
-
+
+[](https://github.com/ToolJet/ToolJet/issues)
+[](https://github.com/ToolJet/ToolJet/stargazers)
+
+
+
-[](https://github.com/ToolJet/ToolJet)
-[](https://twitter.com/ToolJet)
+[](https://github.com/ToolJet/ToolJet)
+[](https://twitter.com/ToolJet)
@@ -140,15 +140,15 @@ The user will become Super Admin and the Type column will update from **`workspa
When a user joins a workspace, they are provided with their own personal workspace and option to create new workspaces.
-Super Admins can **control** this behavior from the Manage Instance Settings page, they can **toggle off** the option to **Allow personal workspace**. Now whenever a user joins a workspace they won't be provided a personal workspace nor they will be able to create a new workspace in the instance.
+Super Admins can **control** this behavior from the Manage Settings page, they can **toggle off** the option to **Allow personal workspace**. Now whenever a user joins a workspace they won't be provided a personal workspace nor they will be able to create a new workspace in the instance.
### Enable multiplayer editing
-Super Admins can enable multiplayer editing from the Manage Instance Settings page. Once enabled, users will be able to edit the same app simultaneously resulting in real-time collaboration.
+Super Admins can enable multiplayer editing from the Manage Settings page. Once enabled, users will be able to edit the same app simultaneously resulting in real-time collaboration.
## License
-Manage the instance license via the **Instance Settings** page. Super Admins have the capability to update the instance's license key from this page.
+Manage the instance license via the **Settings** page. Super Admins have the capability to update the instance's license key from this page.
Check out the [License](/docs/licensing) page for more details.
diff --git a/docs/docs/Enterprise/white-label.md b/docs/docs/Enterprise/white-label.md
index 2f91cf349a..3199b55b72 100644
--- a/docs/docs/Enterprise/white-label.md
+++ b/docs/docs/Enterprise/white-label.md
@@ -35,7 +35,7 @@ With this feature, you gain the ability to rebrand the following key elements:
## Configuration
-To enable white labelling, you'll need to go to the **Instance Settings** from the Dashboard and click on the `White labelling` tab. On the White labelling page, you'll be able to configure the following:
+To enable white labelling, you'll need to go to the **Settings** from the Dashboard and click on the `White labelling` tab. On the White labelling page, you'll be able to configure the following:
- **Application Logo**: Add the URL of the image you want to use as your application logo. Preferred dimensions of the logo are: width `130px` and height `26px`.
- **Favicon**: Enter the URL of the image you want to use as your application's favicon. Preferred dimensions of the favicon are: width `32px` and height `32px` or `16px` and height `16px`.
diff --git a/docs/docs/contributing-guide/setup/codespaces.md b/docs/docs/contributing-guide/setup/codespaces.md
new file mode 100644
index 0000000000..1204d71f63
--- /dev/null
+++ b/docs/docs/contributing-guide/setup/codespaces.md
@@ -0,0 +1,117 @@
+---
+id: codespaces
+title: GitHub Codespaces
+---
+
+Follow the steps below to set up ToolJet on GitHub Codespaces. We recommend reading our guide on [architecture](https://docs.tooljet.com/docs/contributing-guide/setup/architecture) of ToolJet before proceeding.
+
+Open the terminal and run the commands below.
+
+## Setting up
+
+### 1. Set up the environment
+
+1. Install Node.js ( version: v18.3.0 ) and npm (version: v8.11.0)
+
+```
+nvm install 18.3.0
+nvm use 18.3.0
+npm install -g npm@8.11.0
+```
+
+2. Install Postgres
+
+```
+sudo sh -c 'echo "deb [http://apt.postgresql.org/pub/repos/apt](http://apt.postgresql.org/pub/repos/apt) $(lsb_release -cs)-pgdg main" > /etc/apt/sources.list.d/pgdg.list'
+
+wget --quiet -O - [https://www.postgresql.org/media/keys/ACCC4CF8.asc](https://www.postgresql.org/media/keys/ACCC4CF8.asc) | sudo apt-key add -
+
+sudo apt-get update
+
+sudo apt-get install postgresql-13 postgresql-contrib-13
+```
+
+To start the postgresql service run the below command:
+
+```
+sudo service postgresql start
+```
+
+If you wish to change the password of the installed postresql service run the below commands:
+
+```
+sudo su
+
+sudo -u postgres psql
+
+\password postgres
+
+\q
+```
+
+### 2. Set up environment variables
+
+Create a `.env` file by running the command `touch .env`. More information on the variables that can be set is given in the [environment variables reference](https://docs.tooljet.com/docs/setup/env-vars)
+
+**For basic set-up you add the below env variables:**
+
+```
+TOOLJET_HOST=http://localhost:3000
+
+LOCKBOX_MASTER_KEY=
+
+SECRET_KEY_BASE=
+
+PG_USER=postgres
+
+PG_HOST=localhost
+
+PG_PASS=postgres
+
+PG_DB=tooljet_prod
+
+SUB_PATH=/apps/tooljet/
+
+NODE_ENV=production
+
+SERVE_CLIENT=true
+```
+
+> `SECRET_KEY_BASE` requires a 64 byte key. (If you have `openssl` installed, run `openssl rand -hex 64` to create a 64 byte secure random key)
+>
+> `LOCKBOX_MASTER_KEY` requires a 32 byte key. (Run `openssl rand -hex 32` to create a 32 byte secure random key)
+
+### 3. Install and build dependencies
+
+Make sure node version is set to 18.3.0 before running the below command:
+
+```
+npm install
+npm install --prefix server
+npm install --prefix frontend
+npm run build:plugins
+```
+
+
+### 4. Set up database
+
+```
+npm run --prefix server db:create
+npm run --prefix server db:mirgate
+```
+
+If at any point you need to reset the database, use this command `npm run --prefix server db:reset`
+
+### 5. Build client
+
+```
+cd ./frontend && NODE=production npm run build
+```
+
+### 6. Run server
+
+```
+cd ./server && npm run start:prod
+```
+
+The client will start on the **port 3000**, you can access the client by visiting the url created by codespace - `https:///apps/tooljet`
\ No newline at end of file
diff --git a/docs/docs/dashboard.md b/docs/docs/dashboard.md
index 821e12663f..cc173528e7 100644
--- a/docs/docs/dashboard.md
+++ b/docs/docs/dashboard.md
@@ -5,7 +5,7 @@ title: Dashboard
The ToolJet Dashboard is the initial landing page that you see upon logging into your workspace. This interface serves as a central hub where you can access a variety of features. Primarily, it displays all the applications you've created within ToolJet. Moreover, you have the capability to create new workspaces and applications directly from this dashboard. Additionally, it provides an option to create folders for categorizing and managing applications for easier organization, access control, and workflow management.
-Furthermore, the dashboard serves as a gateway to various essential sections, such as **[Workflows](/docs/workflows/overview)**, **[ToolJet Database](/docs/tooljet-database)**, **[Data Sources](/docs/data-sources/overview)**, **[Marketplace](/docs/marketplace/marketplace-overview)**, **[Workspace Settings](/docs/tutorial/manage-users-groups)**, **[Instance Settings](/docs/enterprise/superadmin/#instance-settings)**, and **[Audit logs](/docs/enterprise/audit_logs/)**. You can effortlessly navigate to these sections directly from the dashboard.
+Furthermore, the dashboard serves as a gateway to various essential sections, such as **[Workflows](/docs/workflows/overview)**, **[ToolJet Database](/docs/tooljet-database)**, **[Data Sources](/docs/data-sources/overview)**, **[Marketplace](/docs/marketplace/marketplace-overview)**, **[Workspace Settings](/docs/tutorial/manage-users-groups)**, **[Settings](/docs/enterprise/superadmin/#settings)**, and **[Audit logs](/docs/enterprise/audit_logs/)**. You can effortlessly navigate to these sections directly from the dashboard.
@@ -207,7 +207,7 @@ This option allows you to select a specific version of the app to export or expo
#### Export ToolJet table schema
-Selecting this option will inclue the schema of the tooljet table connected to that application in the exported JSON file. This option is available for all the apps on ToolJet however only the apps with a tooljet table connected(includes tjdb query) will have the schema included in the exported JSON file.
+Selecting this option will include the schema of the tooljet table connected to that application in the exported JSON file. This option is available for all the apps on ToolJet however only the apps with a tooljet table connected(includes tjdb query) will have the schema included in the exported JSON file.
This JSON file can be used to [import](#importing-app-connected-to-tooljet-table) the application to ToolJet along with the table schema that was connected to the application.
@@ -245,4 +245,4 @@ The current version of ToolJet is displayed on the top right corner of the dashb
-
\ No newline at end of file
+
diff --git a/docs/docs/data-sources/clickhouse.md b/docs/docs/data-sources/clickhouse.md
index bb55b4a069..a9d60b9cd4 100644
--- a/docs/docs/data-sources/clickhouse.md
+++ b/docs/docs/data-sources/clickhouse.md
@@ -13,7 +13,7 @@ ToolJet uses this [NodeJS](https://github.com/TimonKK/clickhouse) client for Cli
## Connection
-To add a new ClickHouse datasource, Go to the **Datasource Manager** on the left sidebar of the app editor and click on `Add datasource` button. Select **ClickHouse** from the modal that pops up.
+To establish a connection with the Clickhouse data source, you can either click on the `+Add new data source` button located on the query panel or navigate to the **[Data Sources](/docs/data-sources/overview)** page through the ToolJet dashboard.
ToolJet requires the following to connect to your ClickHouse Database:
@@ -33,7 +33,7 @@ ToolJet requires the following to connect to your ClickHouse Database:
## Querying ClickHouse
-After setting up the ClickHouse datasource, you can click on the `+` button of the query manager and select the ClickHouse datasource that you added in the previous step to create a new query.
+After setting up the ClickHouse data source, you can click on the `+` button of the query manager and select the ClickHouse data source that you added in the previous step to create a new query.
:::info
For more details on clickhouse visit [Clickhouse docs](https://clickhouse.com/docs/en/quick-start).
diff --git a/docs/docs/data-sources/mongodb.md b/docs/docs/data-sources/mongodb.md
index 8a4dea7b16..af4c93353c 100644
--- a/docs/docs/data-sources/mongodb.md
+++ b/docs/docs/data-sources/mongodb.md
@@ -7,11 +7,11 @@ title: MongoDB
ToolJet can connect to MongoDB to read and write data.
-## Connection
+## Manual Connection
Please make sure the host/ip of the database is accessible from your VPC if you have self-hosted ToolJet. If you are using ToolJet cloud, please whitelist our IP.
-To establish a connection with the MongoDB data source, click on the `+Add new data source` button located on the query panel or navigate to the [Data Sources](https://docs.tooljet.com/docs/data-sources/overview) page from the ToolJet dashboard.
+To establish a manual connection with the MongoDB data source, click on the `+Add new data source` button located on the query panel or navigate to the [Data Sources](https://docs.tooljet.com/docs/data-sources/overview) page from the ToolJet dashboard.
ToolJet requires the following to connect to your MongoDB.
@@ -26,6 +26,20 @@ It is recommended to create a new MongoDB user so that you can control the acces
Click on 'Test connection' button to verify if the credentials are correct and that the database is accessible to ToolJet server. Click on 'Save' button to save the data source.
+## Connect Using Connecting String
+
+You can also use a **Connection String** by switching the method from the dropdown. You will be prompted to enter the details of your MongoDB connection.
+
+The primary piece of information you need here is your MongoDB connection string. The connection string typically looks like this:
+`mongodb+srv://${username}:${password}@${cluster}/{database}`.
+
+For example: `mongodb+srv://tooljettest:fakepassword@cluster0.urul7.mongodb.net/hrms`
+
+
+
+Make sure to replace username, password, cluster, and database with your actual MongoDB details. If your MongoDB instance requires additional connection options, you can usually append these options to the connection string.
+
+
## Querying MongoDB
Click on `+` button of the query manager at the bottom panel of the editor and select the database added in the previous step as the data source. Select the operation that you want to perform and click 'Save' to save the query.
diff --git a/docs/docs/data-sources/restapi.md b/docs/docs/data-sources/restapi.md
index ab4cbc3194..179dfbd11b 100644
--- a/docs/docs/data-sources/restapi.md
+++ b/docs/docs/data-sources/restapi.md
@@ -1,6 +1,6 @@
---
id: restapi
-title: REST API
+title: REST API
---
ToolJet can establish a connection with any available REST API endpoint and create queries to interact with it.
@@ -61,11 +61,32 @@ ToolJet supports the REST HTTP methods **GET**, **POST**, **PUT**, **PATCH**, an
+
+
+
+## Additional header
+
+Whenever a request is made to the REST API, a **tj-x-forwarded-for** header is added to the request, the value of the header will be the IP address of the user who is logged in to the ToolJet application. This header can be used to identify the user who is making the request to the REST API.
+
+
+
+
+
+
+
+## Request types
+
+The plugin will send a **JSON** formatted body by default. If a file object from a [`FilePicker` widget](/docs/widgets/file-picker) is set as a value, the body is automatically converted to be sent as a `multipart/form-data` request.
+
+
+
+
+
## Response types
-REST APIs can return data in a variety of formats, including **JSON** and **Base64**. JSON is a common format used for data exchange in REST APIs, while Base64 is often used for encoding binary data, such as images or video, within a JSON response.
+REST APIs can return data in a variety of formats, including **JSON** and **Base64**. JSON is a common format used for data exchange in REST APIs, while Base64 is often used for encoding binary data, such as images or video, within a JSON response.
When the response `content-type` is **image**, the response will be a `base64` string.
### Example JSON response
diff --git a/docs/docs/how-to/bulk-update-multiple-rows-in-table.md b/docs/docs/how-to/bulk-update-multiple-rows-in-table.md
index b29e582b46..f518b117ac 100644
--- a/docs/docs/how-to/bulk-update-multiple-rows-in-table.md
+++ b/docs/docs/how-to/bulk-update-multiple-rows-in-table.md
@@ -5,56 +5,62 @@ title: Bulk update multiple rows in table
# Bulk update multiple rows in table
-Currently, the datasources in ToolJet have operation for **bulk update(GUI mode)** but that only works for changes made in the single row. We will soon be adding a new operation for bulk updating the multiple rows but for now we can bulk update multiple rows by creating a Custom JS query.
+Currently, the data sources in ToolJet have operation for **bulk update(GUI mode)** but that only works for changes made in the single row. We will soon be adding a new operation for bulk updating the multiple rows but for now we can bulk update multiple rows by creating a Custom JS query.
-In this guide, We have assumed that you have successfully connected the data source. For this guide, we will be using the PostgreSQL data source as an example database, currently, this workaround can be used only for PostgreSQL and MySQL.
+In this guide, We have assumed that you have successfully connected the data source. For this guide, we will be using the PostgreSQL data source as an example database. Currently, this workaround can be used only for PostgreSQL and MySQL.
## 1. Create a query to get the data from the database
-Let's create the query that will be getting the data from the database:
+- Create a postgresql query in **SQL mode** and enter
+
+```sql
+SELECT * FROM tooljet // replace tooljet with your table name
+```
+
+- Hit **Run** to fetch the data from the database
-
+
## 2. Display the data on the table
-- Drag a **Table** widget on the canvas and click on its handle to open the properties on the left sidebar
-- Edit the **Table data** field value and enter **`{{queries.postgresql1.data}}`**
+- Go to the **Components** library on the right and drag a **Table** component onto the canvas
+- Click on the handle of the **Table** component to open its properties on the right sidebar
+- Populate the table with the data from the query by entering **`{{queries..data}}`** in the **Data** field
-
+
## 3. Make the columns editable
-- Go to the **Columns**, Add or edit columns section and enter the **Column Name** that you want to display on the table and the **Key** name. Key is the name of the column in your database.
-- Enable the toggle for **Make editable** for the columns that you want to be editable.
+- Under the **Columns** accordion, click on the column name that you want to make editable
+- On clicking the column name, a new section will open. Enable the toggle for **Make editable** to make the column editable
-
+
-## 4. Enable bulk update options for table widget
+## 4. Enable Multiple Row Selection
-- Go to the **Options** section and enable the **Show update buttons**. Enabling this will add two buttons - **Save Changes** and **Discard Changes** at the bottom of the table, only when any cell in the table is edited.
-- You can also enable highlight selected row.(**Optional**)
+- Under the **Row Selection** accordion, enable the **Allow Selection**, **Highlight Selected Row**, and **Bulk Selection** option
-
+
## 5. Create a Custom JS query
-We will create a new Custom JS query(**runjs1**) that will generate SQL query for updating multiple rows.
+- Create a new Run Javascript query and use the code below to generate the SQL query for updating multiple rows.
```js
const uniqueIdentifier = "id"
@@ -81,36 +87,47 @@ Update **table1** with the name of the table you are using.
:::
-
+
## 6. Create an Update query
-Let's create a new PostgreSQL query and name it `update`. In **SQL mode**, enter `{{queries.runjs1.data.join(' ')}}` and **Save** it.
+- Create a postgresql query in **SQL mode** and rename it as **update**:
+
+```sql
+{{queries.runjs1.data.join(' ')}}
+```
+
+- This query will run the SQL query generated by the runjs1 query.
-
+
-## 7. Creating a flow for queries
+## 7. Adding event handlers to execute queries in sequence
-- Click on the handle of the **Table** widget to open its properties
-- Go to the **Events**, and add a handler
-- Select **Bulk Update** in Events, **Run Query** in Actions, and then select the **runjs1** query in Query. Now whenever a user will edit the table and hit the **Save Changes** button runjs1 will run.
+- Edit the **Table** component and add the event handler for **Save Changes** event so that whenever a user will edit the table and hit the **Save Changes** button the runjs1 query will run.
+- Add **loading state** to table so that whenever the **users** or **update** query is running the table will show a loading state.
+
+```js
+{{queries.users.isLoading || queries.update.isLoading}} // add this in the loading state field of the table
+```
-
+
-- Now, go to the **Advanced** tab of **runjs1** and add a handler to run update query for **Query Success** Event. Now whenever the runjs1 query will be run - the update operation will be performed on the database.
+- Now, go to the **runjs1** query and add a **Event** to run update query for **Query Success** Event. This will run the update query whenever the runjs1 query will be run.
-
+
-
\ No newline at end of file
+
+
+- Finally, go to the **update** query and add a **Event** to run the users query for **Query Success** Event. This will refresh the table whenever the update query will be run.
\ No newline at end of file
diff --git a/docs/docs/org-management/licensing.md b/docs/docs/org-management/licensing.md
index 57d9d9aa7c..0f9204f801 100644
--- a/docs/docs/org-management/licensing.md
+++ b/docs/docs/org-management/licensing.md
@@ -24,9 +24,9 @@ Let's look into three types of licenses:
If you are an existing user and wish to update your trial license key, follow these steps:
1. Set up the instance and log in as a **[Super Admin](/docs/Enterprise/superadmin)**.
-2. Navigate to the instance settings page.
+2. Navigate to the Settings page.
3. In the license key tab, make the necessary updates to the provided license key.
-4. Within the license tab of the instance settings page, you can access the limit tab, which displays the current status of available super admins, builders, and end users.
+4. Within the license tab of the Settings page, you can access the limit tab, which displays the current status of available super admins, builders, and end users.
:::caution Note
The trial license key will be valid for 14 days. To fully enjoy ToolJet, we recommend upgrading to premium plans within this period. If you wish to upgrade from the trial to the business or enterprise edition, you can click the **Upgrade or Renew** button or contact our team via **[Slack](https://tooljet.com/slack)**. Upon expiration, access to premium features like OpenID SSO login and Audit logs will be restricted, ensuring no data loss occurs. However, don't worry! You can still upgrade to any of our premium plans and enjoy the benefits of ToolJet.
@@ -65,9 +65,9 @@ The business license key will be valid for 3 months only. You can renew it to co
**To update the license key, follow these steps:**
1. Log in as a **[Super Admin](/docs/Enterprise/superadmin)**, ensuring that you are on the correct instance URL.
-2. Go to the Instance settings page.
+2. Go to the Settings page.
3. In the license key tab, update the provided license key.
-4. Within the license tab of the instance settings page, you can access the limit tab, which provides details about available super admins, builders, and end users.
+4. Within the license tab of the Settings page, you can access the limit tab, which provides details about available super admins, builders, and end users.
:::info Note
As a super admin, you can conveniently view the remaining days of your enterprise edition period on the dashboard. (Refer to screenshots below)
@@ -101,7 +101,7 @@ If your business or enterprise edition license key is nearing expiration, please
**Ref: Screenshot addressing upgrade/renew CTAs. Note that there are a couple of other pages which will display banners or CTAs, from where you can upgrade/renew.**
### 2) What is the duration of my license's validity?
-If you have an active license, you can find its validity period in the instance settings. Generally, the duration of your license varies based on the type:
+If you have an active license, you can find its validity period in the Settings. Generally, the duration of your license varies based on the type:
- Trial licenses are valid for 14 days.
- Business licenses are valid for 3 months.
- Enterprise licenses can be customized to suit your needs.
diff --git a/docs/docs/org-management/workspaces/workspace_overview.md b/docs/docs/org-management/workspaces/workspace_overview.md
index 9f0bcd19e3..6b2eb0a91e 100644
--- a/docs/docs/org-management/workspaces/workspace_overview.md
+++ b/docs/docs/org-management/workspaces/workspace_overview.md
@@ -5,7 +5,7 @@ title: 'Workspace: Overview'
# Workspace: Overview
-User can create their own workspaces, user who created workspace will be having admin privileges for the workspace.
+The user who creates the workspace will automatically be assigned as its administrator.
@@ -27,16 +27,15 @@ User can create their own workspaces, user who created workspace will be having
Please check the detailed doc on **[Permissions](/docs/org-management/permissions)**.
:::
-- The administrator can manage [users and groups](/docs/tutorial/manage-users-groups) of each workspace
-- Applications and settings can not be shared between workspaces
-- A user authorised to login to ToolJet will not have access to all workspaces, Users should be invited or signed up to a workspace to log-in to it.
-- When Multi-Workspace feature is enabled, user should login with username and password to log in to Tooljet.
-- Administrator can configure authentication methods for their workspaces.
+- Administrators can manage [users and groups](/docs/tutorial/manage-users-groups) of each workspace.
+- Applications and settings cannot be shared between workspaces.
+- Users authorised to login to ToolJet will not have access to all workspaces. Users must be invited to or sign up for a workspace before they can log in.
+- When the Multi-Workspace feature is enabled, users must log in with a username and password.
+- Administrators can configure authentication methods for their workspaces.
- If password login is enabled, switching to the workspace will happen without any other authorization since the user is already authorized with password login.
-- User logged in to Tooljet and trying to switch to a workspace where SSO is enabled and password login is disabled, will be redirected to workspace login page and enabled SSO options will be shown
-- User can directly login to a workspace using workspace login URL, Administrator can view the URL **Manage SSO -> General Settings -> Login URL**.
+- If a user is logged into ToolJet and switches to a workspace that only uses Single Sign-On (SSO), the user will be sent to a login page to select an SSO option.
+- Users can directly login to a workspace using workspace login URL. Administrators can view the URL in the Workspace Settings under **SSO -> General Settings -> Login URL**.
-### When disabled (Super Admin)
+### Disabling Workspace Creation (Super Admin)
- Only **[Super Admins](/docs/Enterprise/superadmin#restrict-creation-of-personal-workspace-of-users)** can disable the option for creating personal workspaces for a user.
-- If creating personal workspaces is disabled, Create workspace feature won’t be available.
-- No separate login page for workspace and SSO configured for the workspace will be reflected to the main login page/login.
\ No newline at end of file
+- If the option to make personal workspaces is turned off for a user, the user won't be able to create new workspaces.
diff --git a/docs/docs/setup/azure-container.md b/docs/docs/setup/azure-container.md
index 60bdc0aaa5..0dfb78125a 100644
--- a/docs/docs/setup/azure-container.md
+++ b/docs/docs/setup/azure-container.md
@@ -68,3 +68,20 @@ Please note that you need to set up a PostgreSQL database manually to be used by
You can access ToolJet via the application URL provided in the overview tab.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
+
diff --git a/docs/docs/setup/client.md b/docs/docs/setup/client.md
index ebea627ad9..a29cfb1b60 100644
--- a/docs/docs/setup/client.md
+++ b/docs/docs/setup/client.md
@@ -96,3 +96,19 @@ Summarising the steps below:
```bash
cd tooljet-assets && gcloud app deploy
```
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
diff --git a/docs/docs/setup/digitalocean.md b/docs/docs/setup/digitalocean.md
index 0030942f83..0df6ca4994 100644
--- a/docs/docs/setup/digitalocean.md
+++ b/docs/docs/setup/digitalocean.md
@@ -107,3 +107,19 @@ Follow the steps below to deploy ToolJet Database on DigitalOcean:
4. Add your newly created PostgREST app to the trusted sources of your managed or separate database.
5. Update your existing ToolJet application deployment with [environment variables](/docs/setup/env-vars#enable-tooljet-database--optional-) required for PostgREST.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
diff --git a/docs/docs/setup/docker.md b/docs/docs/setup/docker.md
index ea1671ef1f..8a80874ba0 100644
--- a/docs/docs/setup/docker.md
+++ b/docs/docs/setup/docker.md
@@ -128,11 +128,29 @@ Confused about which setup to select? Feel free to ask the community via Slack:
`sudo docker-compose up -d`
iv. Setup docker to run without root privileges by following the instructions written here https://docs.docker.com/engine/install/linux-postinstall/
- :::
+:::
-
-
-
-
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
+
+
+
+
+
+
diff --git a/docs/docs/setup/ec2.md b/docs/docs/setup/ec2.md
index 662b4f2d56..1c10b0e918 100644
--- a/docs/docs/setup/ec2.md
+++ b/docs/docs/setup/ec2.md
@@ -11,6 +11,13 @@ You should setup a PostgreSQL database manually to be used by the ToolJet server
*If you have any questions feel free to join our [Slack Community](https://tooljet.com/slack) or send us an email at hello@tooljet.com.*
+You can effortlessly deploy Amazon Elastic Compute Cloud Service (EC2) by utilizing a **CloudFormation template**. This template will deploy all the services required to run ToolJet on AWS EC2 instances.
+
+To deploy all the services at once, simply employ the following template:
+```
+curl -LO https://tooljet-deployments.s3.us-west-1.amazonaws.com/cloudformation/EC2-cloudfomration.yml
+```
+
Follow the steps below to deploy ToolJet on AWS EC2 instances.
1. Setup a PostgreSQL database and make sure that the database is accessible from the EC2 instance.
@@ -77,4 +84,26 @@ Follow the steps below to deploy ToolJet on AWS EC2 instances.
ToolJet AMI comes inbuilt with PostgREST. If you intend to use this feature, you'd only have to setup the environment variables in `~/app/.env` file and run `./setup_app` script.
-You can learn more about this feature [here](/docs/tooljet-database).
\ No newline at end of file
+You can learn more about this feature [here](/docs/tooljet-database).
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
+
+
+
+
+
+
diff --git a/docs/docs/setup/ecs.md b/docs/docs/setup/ecs.md
index c3eb758aa0..9a92e088a7 100644
--- a/docs/docs/setup/ecs.md
+++ b/docs/docs/setup/ecs.md
@@ -225,6 +225,21 @@ Follow the steps below to deploy PostgREST on a ECS cluster.
-
Update ToolJet deployment with the appropriate env variables [here](https://docs.tooljet.com/docs/setup/env-vars/#enable-tooljet-database--optional-) and apply the changes.
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
+
diff --git a/docs/docs/setup/env-vars.md b/docs/docs/setup/env-vars.md
index 18f69d14e5..030d910da1 100644
--- a/docs/docs/setup/env-vars.md
+++ b/docs/docs/setup/env-vars.md
@@ -63,7 +63,7 @@ Self-hosted version of ToolJet pings our server to fetch the latest product upda
### Comment feature enable ( optional )
-Use this environment variable to enable/disable the feature that allows you to add comments on the canvas. To configure this environment variable, ensure that multiplayer editing is enabled in the instance settings.
+Use this environment variable to enable/disable the feature that allows you to add comments on the canvas. To configure this environment variable, ensure that multiplayer editing is enabled in the Settings.
| variable | value |
| ---------------------- | ----------------- |
@@ -305,6 +305,14 @@ If this parameter is not specified then PostgREST refuses authentication request
Please make sure that DB_URI is given in the format `postgrest://[USERNAME]:[PASSWORD]@[HOST]:[PORT]/[DATABASE]`
:::
+## Log file path ( Optional )
+
+If a log file path is specified in environment variables, a log file containing all the data from audit logs will be created at the specified path. The file will be updated every time a new audit log is created.
+
+| Variable | Description |
+| -------- | --------------------------------------------------------------------------- |
+| LOG_FILE_PATH | the path where the log file will be created ( eg: tooljet/log/tooljet-audit.log) |
+
## ToolJet Apps
### Enabling embedding of private apps
diff --git a/docs/docs/setup/google-cloud-run.md b/docs/docs/setup/google-cloud-run.md
index 0431078dcc..3034395e2f 100644
--- a/docs/docs/setup/google-cloud-run.md
+++ b/docs/docs/setup/google-cloud-run.md
@@ -151,3 +151,20 @@ Once the Service is created and live, to make the Cloud Service URL public. Ple
+
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/docs/setup/helm.md b/docs/docs/setup/helm.md
index cca63346c1..ce2632a837 100644
--- a/docs/docs/setup/helm.md
+++ b/docs/docs/setup/helm.md
@@ -33,4 +33,20 @@ For more information about the ToolJet database, you can visit [here](/docs/tool
If you plan to use this feature, you need to set up and deploy the PostgREST server, which facilitates querying the ToolJet Database.
-To enable the ToolJet database, please set the environment variable `ENABLE_TOOLJET_DB` to true in the `values.yaml` file.
\ No newline at end of file
+To enable the ToolJet database, please set the environment variable `ENABLE_TOOLJET_DB` to true in the `values.yaml` file.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/docs/setup/kubernetes-aks.md b/docs/docs/setup/kubernetes-aks.md
index 04cc1515d2..6fad371369 100644
--- a/docs/docs/setup/kubernetes-aks.md
+++ b/docs/docs/setup/kubernetes-aks.md
@@ -53,3 +53,19 @@ If you intend to use this feature, you'd have to set up and deploy PostgREST ser
```
2. Update ToolJet deployment with the appropriate env variables [here](https://tooljet-deployments.s3.us-west-1.amazonaws.com/kubernetes/AKS/deployment.yaml) and apply the changes.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
diff --git a/docs/docs/setup/kubernetes-gke.md b/docs/docs/setup/kubernetes-gke.md
index c87a6c36bd..1cbbf82210 100644
--- a/docs/docs/setup/kubernetes-gke.md
+++ b/docs/docs/setup/kubernetes-gke.md
@@ -79,3 +79,19 @@ If you intend to use this feature, you'd have to set up and deploy PostgREST ser
```
2. Update ToolJet deployment with the appropriate env variables [here](https://tooljet-deployments.s3.us-west-1.amazonaws.com/kubernetes/GKE/deployment.yaml) and apply the changes.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
diff --git a/docs/docs/setup/kubernetes.md b/docs/docs/setup/kubernetes.md
index 10441ef99d..168c2cc926 100644
--- a/docs/docs/setup/kubernetes.md
+++ b/docs/docs/setup/kubernetes.md
@@ -62,3 +62,19 @@ If you intend to use this feature, you'd have to set up and deploy PostgREST ser
```
2. Update ToolJet deployment with the appropriate env variables [here](https://tooljet-deployments.s3.us-west-1.amazonaws.com/kubernetes/deployment.yaml) and apply the changes.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
diff --git a/docs/docs/setup/openshift.md b/docs/docs/setup/openshift.md
index 73f6a7e531..ae8f4e5bf7 100644
--- a/docs/docs/setup/openshift.md
+++ b/docs/docs/setup/openshift.md
@@ -68,3 +68,19 @@ If you intend to use this feature, you'd have to set up and deploy PostgREST ser
```
https://tooljet-deployments.s3.us-west-1.amazonaws.com/openshift/postgrest.yaml
```
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
diff --git a/docs/docs/setup/tooljet-subpath.md b/docs/docs/setup/tooljet-subpath.md
index e05625d5d6..51c8a438ad 100644
--- a/docs/docs/setup/tooljet-subpath.md
+++ b/docs/docs/setup/tooljet-subpath.md
@@ -20,4 +20,20 @@ You'll need to setup the following environment variables if ToolJet installation
See all **[Environment Variables](/docs/setup/env-vars)** here.
:::
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
+
diff --git a/docs/docs/setup/try-tooljet.md b/docs/docs/setup/try-tooljet.md
index eb60b5323a..ff2bc44904 100644
--- a/docs/docs/setup/try-tooljet.md
+++ b/docs/docs/setup/try-tooljet.md
@@ -10,10 +10,11 @@ title: Try ToolJet
You can run the command below to have ToolJet up and running right away.
```bash
-docker run \
+docker run -d \
--name tooljet \
--restart unless-stopped \
-p 80:80 \
+ --platform linux/amd64 \
-v tooljet_data:/var/lib/postgresql/13/main \
tooljet/try:latest
```
diff --git a/docs/docs/tutorial/keyboard-shortcuts.md b/docs/docs/tutorial/keyboard-shortcuts.md
index f534298ff4..26d32d5b93 100644
--- a/docs/docs/tutorial/keyboard-shortcuts.md
+++ b/docs/docs/tutorial/keyboard-shortcuts.md
@@ -5,118 +5,18 @@ title: Keyboard Shortcuts
# Keyboard Shortcuts
-You can perform operations like undo, redo, clone, or removing the widget directly using the keyboard shortcuts.
+You can perform operations like copying and pasting components, cloning components, deleting components, undo, redo, and more using keyboard shortcuts.
-## Copy
-You can copy the component on the visual app editor using the following shortcut keys:
+| Action | Mac Shortcut | Linux/Windows Shortcut |
+|:------------|:-------------------|:-----------------------|
+| Copy component | `cmd + c` | `ctrl + c` |
+| Cut component | `cmd + x` | `ctrl + x` |
+| Paste component | `cmd + v` | `ctrl + v` |
+| Undo | `cmd + z` | `ctrl + z` |
+| Redo | `cmd + shift + z` | `ctrl + shift + z` |
+| Clone component | `cmd + d` | `ctrl + d` |
+| Remove component | `delete` | `backspace` |
+| Deselect component | `esc` | `esc` |
-**On Mac:** `cmd + c`
-
-**On Linux/Windows:** `ctrl + c`
-
-
-
-
-
-
-
-## Cut
-
-You can cut the component on the visual app editor using the following shortcut keys:
-
-**On Mac:** `cmd + x`
-
-**On Linux/Windows:** `ctrl + x`
-
-
-
-
-
-
-
-## Paste
-
-You can paste the selected component using the following shortcut keys:
-
-**On Mac:** `cmd + v`
-
-**On Linux/Windows:** `ctrl + v`
-
-
-
-
-
-
-
-:::caution
-There are few edge cases when copy-paste commands might not work:
-- The URL should be `https` and it won't work on http on many browsers
-- Recent Firefox versions has some issue with copy functionality
-:::
-
-## Undo
-
-You can undo any operation performed on the visual app editor using the following shortcut keys:
-
-**On Mac:** `cmd + z`
-
-**On Linux/Windows:** `ctrl + z`
-
-
-
-
-
-
-
-## Redo
-
-If you have `undo` an operation and want to redo that again than you can use the following shortcut keys:
-
-**On Mac:** `cmd + shift + z`
-
-**On Linux/Windows:** `ctrl + shift + z`
-
-
-
-
-
-
-
-## Clone
-
-Now you can create multiple clones of any widget without having to drag and drop the widget again from the sidebar. Just select any widget that you want to create a clone and use the following shortcut keys:
-
-**On Mac:** `cmd + d`
-
-**On Linux/Windows:** `ctrl + d`
-
-
-
-
-
-
-
-## Remove widget
-
-Now you can delete a selected widget by using the following shortcut keys:
-
-**On Mac:** `delete`
-
-**On Linux/Windows:** `backspace`
-
-
-
-
-
-
-
-## Unselect the selected widget
-
-You can quickly deselect a widget using the `esc` key.
-
-
-
-
-
-
+To choose several components at once within the app-builder, simply hold down the shift key while clicking on each component you want to select.
\ No newline at end of file
diff --git a/docs/docs/tutorial/sharing-and-deploying.md b/docs/docs/tutorial/sharing-and-deploying.md
index 4931337d82..265b61c6a8 100644
--- a/docs/docs/tutorial/sharing-and-deploying.md
+++ b/docs/docs/tutorial/sharing-and-deploying.md
@@ -45,7 +45,7 @@ Once you have released a version of your app, you can share the app with others
-- You can also `Embedd` your application using the embeddable link
+- You can also `Embed` your application using the embeddable link
You can access ToolJet via the application URL provided in the overview tab.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
diff --git a/docs/versioned_docs/version-1.x.x/setup/client.md b/docs/versioned_docs/version-1.x.x/setup/client.md
index ebea627ad9..a29cfb1b60 100644
--- a/docs/versioned_docs/version-1.x.x/setup/client.md
+++ b/docs/versioned_docs/version-1.x.x/setup/client.md
@@ -96,3 +96,19 @@ Summarising the steps below:
```bash
cd tooljet-assets && gcloud app deploy
```
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
diff --git a/docs/versioned_docs/version-1.x.x/setup/digitalocean.md b/docs/versioned_docs/version-1.x.x/setup/digitalocean.md
index 7fb769f91e..b625c6c794 100644
--- a/docs/versioned_docs/version-1.x.x/setup/digitalocean.md
+++ b/docs/versioned_docs/version-1.x.x/setup/digitalocean.md
@@ -42,4 +42,20 @@ Now you can quickly deploy ToolJet using the Deploy to DigitalOcean button.
:::tip
ToolJet server and client can be deployed as standalone applications. If you do not want to deploy the client on DigitalOcean, modify `package.json` accordingly. We have a [guide](/docs/setup/client) on deploying ToolJet client using services such as Firebase.
-:::
\ No newline at end of file
+:::
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
diff --git a/docs/versioned_docs/version-1.x.x/setup/docker.md b/docs/versioned_docs/version-1.x.x/setup/docker.md
index eea8ead606..4943eb1aaf 100644
--- a/docs/versioned_docs/version-1.x.x/setup/docker.md
+++ b/docs/versioned_docs/version-1.x.x/setup/docker.md
@@ -126,11 +126,29 @@ Confused about which setup to select? Feel free to ask the community via Slack:
`sudo docker-compose up -d`
iv. Setup docker to run without root privileges by following the instructions written here https://docs.docker.com/engine/install/linux-postinstall/
- :::
+:::
-
-
-
-
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
+
+
+
+
+
+
diff --git a/docs/versioned_docs/version-1.x.x/setup/ec2.md b/docs/versioned_docs/version-1.x.x/setup/ec2.md
index 0d85cf1a74..db4ce00a70 100644
--- a/docs/versioned_docs/version-1.x.x/setup/ec2.md
+++ b/docs/versioned_docs/version-1.x.x/setup/ec2.md
@@ -72,3 +72,19 @@ Follow the steps below to deploy ToolJet on AWS EC2 instances.
10. If you've set a custom domain for `TOOLJET_HOST`, add a `A record` entry in your DNS settings to point to the IP address of the EC2 instance.
12. You're all done, ToolJet client would now be served at the value you've set in `TOOLJET_HOST`.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
diff --git a/docs/versioned_docs/version-1.x.x/setup/ecs.md b/docs/versioned_docs/version-1.x.x/setup/ecs.md
index 30aaab9fb9..1d993af9db 100644
--- a/docs/versioned_docs/version-1.x.x/setup/ecs.md
+++ b/docs/versioned_docs/version-1.x.x/setup/ecs.md
@@ -94,3 +94,19 @@ The setup above is just a template. Feel free to update the task definition and
6. Click on run task to have this task seed the database with user having following credentials:
- email: `dev@tooljet.io`
- password: `password`
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-1.x.x/setup/google-cloud-run.md b/docs/versioned_docs/version-1.x.x/setup/google-cloud-run.md
index de8b8d6468..8228762d0c 100644
--- a/docs/versioned_docs/version-1.x.x/setup/google-cloud-run.md
+++ b/docs/versioned_docs/version-1.x.x/setup/google-cloud-run.md
@@ -142,3 +142,19 @@ The deployment will fail as it only runs a seed script. Check logs to see that d
```
The default username of the admin is `dev@tooljet.io` and the password is `password`.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-1.x.x/setup/helm.md b/docs/versioned_docs/version-1.x.x/setup/helm.md
index cca63346c1..ce2632a837 100644
--- a/docs/versioned_docs/version-1.x.x/setup/helm.md
+++ b/docs/versioned_docs/version-1.x.x/setup/helm.md
@@ -33,4 +33,20 @@ For more information about the ToolJet database, you can visit [here](/docs/tool
If you plan to use this feature, you need to set up and deploy the PostgREST server, which facilitates querying the ToolJet Database.
-To enable the ToolJet database, please set the environment variable `ENABLE_TOOLJET_DB` to true in the `values.yaml` file.
\ No newline at end of file
+To enable the ToolJet database, please set the environment variable `ENABLE_TOOLJET_DB` to true in the `values.yaml` file.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-1.x.x/setup/heroku.md b/docs/versioned_docs/version-1.x.x/setup/heroku.md
index 3f993f6f96..a92619ced4 100644
--- a/docs/versioned_docs/version-1.x.x/setup/heroku.md
+++ b/docs/versioned_docs/version-1.x.x/setup/heroku.md
@@ -61,3 +61,19 @@ The one click deployment will create a **free dyno** and a **free postgresql dat
:::tip
ToolJet server and client can be deployed as standalone applications. If you do not want to deploy the client on Heroku, modify `package.json` accordingly. We have a [guide](/docs/setup/client) on deploying ToolJet client using services such as Firebase.
:::
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
diff --git a/docs/versioned_docs/version-1.x.x/setup/kubernetes-aks.md b/docs/versioned_docs/version-1.x.x/setup/kubernetes-aks.md
index 8d34e9dc3f..6597c8947f 100644
--- a/docs/versioned_docs/version-1.x.x/setup/kubernetes-aks.md
+++ b/docs/versioned_docs/version-1.x.x/setup/kubernetes-aks.md
@@ -49,3 +49,19 @@ This seeds the database with a default user with the following credentials:
**email**: `dev@tooljet.io`
**password**: `password`
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
diff --git a/docs/versioned_docs/version-1.x.x/setup/kubernetes-gke.md b/docs/versioned_docs/version-1.x.x/setup/kubernetes-gke.md
index 61aa753c5b..21bee8ea59 100644
--- a/docs/versioned_docs/version-1.x.x/setup/kubernetes-gke.md
+++ b/docs/versioned_docs/version-1.x.x/setup/kubernetes-gke.md
@@ -74,3 +74,19 @@ This seeds the database with a default user with the following credentials:
**emai**: `dev@tooljet.io`
**password**: `password`
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
diff --git a/docs/versioned_docs/version-1.x.x/setup/kubernetes.md b/docs/versioned_docs/version-1.x.x/setup/kubernetes.md
index 08b444c5cf..031524453d 100644
--- a/docs/versioned_docs/version-1.x.x/setup/kubernetes.md
+++ b/docs/versioned_docs/version-1.x.x/setup/kubernetes.md
@@ -48,4 +48,20 @@ If there are self signed HTTPS endpoints that Tooljet needs to connect to, pleas
:::tip
If you want to serve ToolJet client from services such as Firebase or Netlify, please read the client Setup documentation **[here](/docs/setup/client)**.
-:::
\ No newline at end of file
+:::
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
diff --git a/docs/versioned_docs/version-1.x.x/setup/tooljet-subpath.md b/docs/versioned_docs/version-1.x.x/setup/tooljet-subpath.md
index e05625d5d6..51c8a438ad 100644
--- a/docs/versioned_docs/version-1.x.x/setup/tooljet-subpath.md
+++ b/docs/versioned_docs/version-1.x.x/setup/tooljet-subpath.md
@@ -20,4 +20,20 @@ You'll need to setup the following environment variables if ToolJet installation
See all **[Environment Variables](/docs/setup/env-vars)** here.
:::
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
+
diff --git a/docs/versioned_docs/version-1.x.x/setup/try-tooljet.md b/docs/versioned_docs/version-1.x.x/setup/try-tooljet.md
index ed0173f004..6d379d672b 100644
--- a/docs/versioned_docs/version-1.x.x/setup/try-tooljet.md
+++ b/docs/versioned_docs/version-1.x.x/setup/try-tooljet.md
@@ -9,10 +9,11 @@ title: Try ToolJet
You can run the command below to have ToolJet up and running right away.
```bash
-docker run \
+docker run -d \
--name tooljet \
--restart unless-stopped \
- -p 3000:3000 \
+ -p 80:80 \
+ --platform linux/amd64 \
-v tooljet_data:/var/lib/postgresql/13/main \
tooljet/try:latest
```
diff --git a/docs/versioned_docs/version-2.0.0/setup/azure-container.md b/docs/versioned_docs/version-2.0.0/setup/azure-container.md
index b9e9f9947f..c0d9138d6e 100644
--- a/docs/versioned_docs/version-2.0.0/setup/azure-container.md
+++ b/docs/versioned_docs/version-2.0.0/setup/azure-container.md
@@ -65,3 +65,19 @@ Please note that you need to set up a PostgreSQL database manually to be used by
You can access ToolJet via the application URL provided in the overview tab.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
diff --git a/docs/versioned_docs/version-2.0.0/setup/client.md b/docs/versioned_docs/version-2.0.0/setup/client.md
index ebea627ad9..a29cfb1b60 100644
--- a/docs/versioned_docs/version-2.0.0/setup/client.md
+++ b/docs/versioned_docs/version-2.0.0/setup/client.md
@@ -96,3 +96,19 @@ Summarising the steps below:
```bash
cd tooljet-assets && gcloud app deploy
```
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
diff --git a/docs/versioned_docs/version-2.0.0/setup/digitalocean.md b/docs/versioned_docs/version-2.0.0/setup/digitalocean.md
index a4143f9e4f..c68c8e127d 100644
--- a/docs/versioned_docs/version-2.0.0/setup/digitalocean.md
+++ b/docs/versioned_docs/version-2.0.0/setup/digitalocean.md
@@ -64,3 +64,19 @@ Follow the steps below to deploy ToolJet Database on DigitalOcean:
4. Add your newly created PostgREST app to the trusted sources of your managed or separate database.
5. Update your existing ToolJet application deployment with [environment variables](/docs/setup/env-vars#tooljet-database-feature-enable--optional-) required for PostgREST.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
diff --git a/docs/versioned_docs/version-2.0.0/setup/docker.md b/docs/versioned_docs/version-2.0.0/setup/docker.md
index e3dd3affe8..98f21a7551 100644
--- a/docs/versioned_docs/version-2.0.0/setup/docker.md
+++ b/docs/versioned_docs/version-2.0.0/setup/docker.md
@@ -126,11 +126,29 @@ Confused about which setup to select? Feel free to ask the community via Slack:
`sudo docker-compose up -d`
iv. Setup docker to run without root privileges by following the instructions written here https://docs.docker.com/engine/install/linux-postinstall/
- :::
+:::
-
-
-
-
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
+
+
+
+
+
+
diff --git a/docs/versioned_docs/version-2.0.0/setup/ec2.md b/docs/versioned_docs/version-2.0.0/setup/ec2.md
index 540b16c50d..55b0cdb563 100644
--- a/docs/versioned_docs/version-2.0.0/setup/ec2.md
+++ b/docs/versioned_docs/version-2.0.0/setup/ec2.md
@@ -77,4 +77,26 @@ Follow the steps below to deploy ToolJet on AWS EC2 instances.
ToolJet AMI comes inbuilt with PostgREST. If you intend to use this feature, you'd only have to setup the environment variables in `~/app/.env` file and run `./setup_app` script.
-You can learn more about this feature [here](/docs/tooljet-database).
\ No newline at end of file
+You can learn more about this feature [here](/docs/tooljet-database).
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
+
+
+
+
+
+
diff --git a/docs/versioned_docs/version-2.0.0/setup/ecs.md b/docs/versioned_docs/version-2.0.0/setup/ecs.md
index b16770014a..1db580fb95 100644
--- a/docs/versioned_docs/version-2.0.0/setup/ecs.md
+++ b/docs/versioned_docs/version-2.0.0/setup/ecs.md
@@ -77,3 +77,18 @@ Follow the steps below to deploy ToolJet on a ECS cluster.
The setup above is just a template. Feel free to update the task definition and configure parameters for resources and environment variables according to your needs.
:::
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
diff --git a/docs/versioned_docs/version-2.0.0/setup/google-cloud-run.md b/docs/versioned_docs/version-2.0.0/setup/google-cloud-run.md
index 7cac3dce7f..8a7b2f3f6a 100644
--- a/docs/versioned_docs/version-2.0.0/setup/google-cloud-run.md
+++ b/docs/versioned_docs/version-2.0.0/setup/google-cloud-run.md
@@ -151,3 +151,20 @@ Once the Service is created and live, to make the Cloud Service URL public. Ple
+
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.0.0/setup/helm.md b/docs/versioned_docs/version-2.0.0/setup/helm.md
index cca63346c1..ce2632a837 100644
--- a/docs/versioned_docs/version-2.0.0/setup/helm.md
+++ b/docs/versioned_docs/version-2.0.0/setup/helm.md
@@ -33,4 +33,20 @@ For more information about the ToolJet database, you can visit [here](/docs/tool
If you plan to use this feature, you need to set up and deploy the PostgREST server, which facilitates querying the ToolJet Database.
-To enable the ToolJet database, please set the environment variable `ENABLE_TOOLJET_DB` to true in the `values.yaml` file.
\ No newline at end of file
+To enable the ToolJet database, please set the environment variable `ENABLE_TOOLJET_DB` to true in the `values.yaml` file.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.0.0/setup/heroku.md b/docs/versioned_docs/version-2.0.0/setup/heroku.md
index 80e14d2c06..00749f1b66 100644
--- a/docs/versioned_docs/version-2.0.0/setup/heroku.md
+++ b/docs/versioned_docs/version-2.0.0/setup/heroku.md
@@ -143,3 +143,19 @@ Please install Heroku CLI on your local machine. Please refer Heroku CLI install
Please enter the below env variables in the Tooljet application, under the setting tab. You can also refer environment variable [**here**](/docs/setup/env-vars#tooljet-database).
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
diff --git a/docs/versioned_docs/version-2.0.0/setup/kubernetes-aks.md b/docs/versioned_docs/version-2.0.0/setup/kubernetes-aks.md
index c61404eb9f..a2c0b0eaa6 100644
--- a/docs/versioned_docs/version-2.0.0/setup/kubernetes-aks.md
+++ b/docs/versioned_docs/version-2.0.0/setup/kubernetes-aks.md
@@ -52,4 +52,20 @@ If you intend to use this feature, you'd have to set up and deploy PostgREST ser
kubectl apply -f https://raw.githubusercontent.com/ToolJet/ToolJet/main/deploy/kubernetes/AKS/postgrest.yaml
```
-2. Update ToolJet deployment with the appropriate env variables [here](https://raw.githubusercontent.com/ToolJet/ToolJet/main/deploy/kubernetes/AKS/deployment.yaml) and apply the changes.
\ No newline at end of file
+2. Update ToolJet deployment with the appropriate env variables [here](https://raw.githubusercontent.com/ToolJet/ToolJet/main/deploy/kubernetes/AKS/deployment.yaml) and apply the changes.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
diff --git a/docs/versioned_docs/version-2.0.0/setup/kubernetes-gke.md b/docs/versioned_docs/version-2.0.0/setup/kubernetes-gke.md
index af86339fec..93ff34262e 100644
--- a/docs/versioned_docs/version-2.0.0/setup/kubernetes-gke.md
+++ b/docs/versioned_docs/version-2.0.0/setup/kubernetes-gke.md
@@ -79,3 +79,19 @@ If you intend to use this feature, you'd have to set up and deploy PostgREST ser
```
2. Update ToolJet deployment with the appropriate env variables [here](https://raw.githubusercontent.com/ToolJet/ToolJet/main/deploy/kubernetes/GKE/deployment.yaml) and apply the changes.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
diff --git a/docs/versioned_docs/version-2.0.0/setup/kubernetes.md b/docs/versioned_docs/version-2.0.0/setup/kubernetes.md
index f3caf2b871..69baa7cf5a 100644
--- a/docs/versioned_docs/version-2.0.0/setup/kubernetes.md
+++ b/docs/versioned_docs/version-2.0.0/setup/kubernetes.md
@@ -61,3 +61,19 @@ If you intend to use this feature, you'd have to set up and deploy PostgREST ser
```
2. Update ToolJet deployment with the appropriate env variables [here](https://raw.githubusercontent.com/ToolJet/ToolJet/main/deploy/kubernetes/deployment.yaml) and apply the changes.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
diff --git a/docs/versioned_docs/version-2.0.0/setup/openshift.md b/docs/versioned_docs/version-2.0.0/setup/openshift.md
index 1cdb3dd674..a9802dff29 100644
--- a/docs/versioned_docs/version-2.0.0/setup/openshift.md
+++ b/docs/versioned_docs/version-2.0.0/setup/openshift.md
@@ -67,4 +67,20 @@ If you intend to use this feature, you'd have to set up and deploy PostgREST ser
```
https://raw.githubusercontent.com/ToolJet/ToolJet/main/deploy/openshift/postgrest.yaml
-```
\ No newline at end of file
+```
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
diff --git a/docs/versioned_docs/version-2.0.0/setup/tooljet-subpath.md b/docs/versioned_docs/version-2.0.0/setup/tooljet-subpath.md
index e05625d5d6..51c8a438ad 100644
--- a/docs/versioned_docs/version-2.0.0/setup/tooljet-subpath.md
+++ b/docs/versioned_docs/version-2.0.0/setup/tooljet-subpath.md
@@ -20,4 +20,20 @@ You'll need to setup the following environment variables if ToolJet installation
See all **[Environment Variables](/docs/setup/env-vars)** here.
:::
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
+
diff --git a/docs/versioned_docs/version-2.0.0/setup/try-tooljet.md b/docs/versioned_docs/version-2.0.0/setup/try-tooljet.md
index 7ba26756aa..e2158d85fd 100644
--- a/docs/versioned_docs/version-2.0.0/setup/try-tooljet.md
+++ b/docs/versioned_docs/version-2.0.0/setup/try-tooljet.md
@@ -9,10 +9,11 @@ title: Try ToolJet
You can run the command below to have ToolJet up and running right away.
```bash
-docker run \
+docker run -d \
--name tooljet \
--restart unless-stopped \
-p 80:80 \
+ --platform linux/amd64 \
-v tooljet_data:/var/lib/postgresql/13/main \
tooljet/try:latest
```
diff --git a/docs/versioned_docs/version-2.1.0/setup/azure-container.md b/docs/versioned_docs/version-2.1.0/setup/azure-container.md
index b9e9f9947f..c0d9138d6e 100644
--- a/docs/versioned_docs/version-2.1.0/setup/azure-container.md
+++ b/docs/versioned_docs/version-2.1.0/setup/azure-container.md
@@ -65,3 +65,19 @@ Please note that you need to set up a PostgreSQL database manually to be used by
You can access ToolJet via the application URL provided in the overview tab.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
diff --git a/docs/versioned_docs/version-2.1.0/setup/client.md b/docs/versioned_docs/version-2.1.0/setup/client.md
index ebea627ad9..a29cfb1b60 100644
--- a/docs/versioned_docs/version-2.1.0/setup/client.md
+++ b/docs/versioned_docs/version-2.1.0/setup/client.md
@@ -96,3 +96,19 @@ Summarising the steps below:
```bash
cd tooljet-assets && gcloud app deploy
```
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
diff --git a/docs/versioned_docs/version-2.1.0/setup/digitalocean.md b/docs/versioned_docs/version-2.1.0/setup/digitalocean.md
index a4143f9e4f..ab64f0b3bd 100644
--- a/docs/versioned_docs/version-2.1.0/setup/digitalocean.md
+++ b/docs/versioned_docs/version-2.1.0/setup/digitalocean.md
@@ -64,3 +64,19 @@ Follow the steps below to deploy ToolJet Database on DigitalOcean:
4. Add your newly created PostgREST app to the trusted sources of your managed or separate database.
5. Update your existing ToolJet application deployment with [environment variables](/docs/setup/env-vars#tooljet-database-feature-enable--optional-) required for PostgREST.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.1.0/setup/docker.md b/docs/versioned_docs/version-2.1.0/setup/docker.md
index 0c63fd3a83..89a739564a 100644
--- a/docs/versioned_docs/version-2.1.0/setup/docker.md
+++ b/docs/versioned_docs/version-2.1.0/setup/docker.md
@@ -126,11 +126,29 @@ Confused about which setup to select? Feel free to ask the community via Slack:
`sudo docker-compose up -d`
iv. Setup docker to run without root privileges by following the instructions written here https://docs.docker.com/engine/install/linux-postinstall/
- :::
+:::
-
-
-
-
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
+
+
+
+
+
+
diff --git a/docs/versioned_docs/version-2.1.0/setup/ec2.md b/docs/versioned_docs/version-2.1.0/setup/ec2.md
index 540b16c50d..55b0cdb563 100644
--- a/docs/versioned_docs/version-2.1.0/setup/ec2.md
+++ b/docs/versioned_docs/version-2.1.0/setup/ec2.md
@@ -77,4 +77,26 @@ Follow the steps below to deploy ToolJet on AWS EC2 instances.
ToolJet AMI comes inbuilt with PostgREST. If you intend to use this feature, you'd only have to setup the environment variables in `~/app/.env` file and run `./setup_app` script.
-You can learn more about this feature [here](/docs/tooljet-database).
\ No newline at end of file
+You can learn more about this feature [here](/docs/tooljet-database).
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
+
+
+
+
+
+
diff --git a/docs/versioned_docs/version-2.1.0/setup/ecs.md b/docs/versioned_docs/version-2.1.0/setup/ecs.md
index b16770014a..a21236d5e0 100644
--- a/docs/versioned_docs/version-2.1.0/setup/ecs.md
+++ b/docs/versioned_docs/version-2.1.0/setup/ecs.md
@@ -77,3 +77,18 @@ Follow the steps below to deploy ToolJet on a ECS cluster.
The setup above is just a template. Feel free to update the task definition and configure parameters for resources and environment variables according to your needs.
:::
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.1.0/setup/google-cloud-run.md b/docs/versioned_docs/version-2.1.0/setup/google-cloud-run.md
index 0aba9f1854..8fae7cf56e 100644
--- a/docs/versioned_docs/version-2.1.0/setup/google-cloud-run.md
+++ b/docs/versioned_docs/version-2.1.0/setup/google-cloud-run.md
@@ -151,3 +151,20 @@ Once the Service is created and live, to make the Cloud Service URL public. Ple
+
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.1.0/setup/helm.md b/docs/versioned_docs/version-2.1.0/setup/helm.md
index cca63346c1..ce2632a837 100644
--- a/docs/versioned_docs/version-2.1.0/setup/helm.md
+++ b/docs/versioned_docs/version-2.1.0/setup/helm.md
@@ -33,4 +33,20 @@ For more information about the ToolJet database, you can visit [here](/docs/tool
If you plan to use this feature, you need to set up and deploy the PostgREST server, which facilitates querying the ToolJet Database.
-To enable the ToolJet database, please set the environment variable `ENABLE_TOOLJET_DB` to true in the `values.yaml` file.
\ No newline at end of file
+To enable the ToolJet database, please set the environment variable `ENABLE_TOOLJET_DB` to true in the `values.yaml` file.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.1.0/setup/heroku.md b/docs/versioned_docs/version-2.1.0/setup/heroku.md
index 80e14d2c06..eeafb5aa46 100644
--- a/docs/versioned_docs/version-2.1.0/setup/heroku.md
+++ b/docs/versioned_docs/version-2.1.0/setup/heroku.md
@@ -143,3 +143,19 @@ Please install Heroku CLI on your local machine. Please refer Heroku CLI install
Please enter the below env variables in the Tooljet application, under the setting tab. You can also refer environment variable [**here**](/docs/setup/env-vars#tooljet-database).
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.1.0/setup/kubernetes-aks.md b/docs/versioned_docs/version-2.1.0/setup/kubernetes-aks.md
index c61404eb9f..9d28fed702 100644
--- a/docs/versioned_docs/version-2.1.0/setup/kubernetes-aks.md
+++ b/docs/versioned_docs/version-2.1.0/setup/kubernetes-aks.md
@@ -52,4 +52,21 @@ If you intend to use this feature, you'd have to set up and deploy PostgREST ser
kubectl apply -f https://raw.githubusercontent.com/ToolJet/ToolJet/main/deploy/kubernetes/AKS/postgrest.yaml
```
-2. Update ToolJet deployment with the appropriate env variables [here](https://raw.githubusercontent.com/ToolJet/ToolJet/main/deploy/kubernetes/AKS/deployment.yaml) and apply the changes.
\ No newline at end of file
+2. Update ToolJet deployment with the appropriate env variables [here](https://raw.githubusercontent.com/ToolJet/ToolJet/main/deploy/kubernetes/AKS/deployment.yaml) and apply the changes.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
+
diff --git a/docs/versioned_docs/version-2.1.0/setup/kubernetes-gke.md b/docs/versioned_docs/version-2.1.0/setup/kubernetes-gke.md
index af86339fec..2fd124631d 100644
--- a/docs/versioned_docs/version-2.1.0/setup/kubernetes-gke.md
+++ b/docs/versioned_docs/version-2.1.0/setup/kubernetes-gke.md
@@ -79,3 +79,19 @@ If you intend to use this feature, you'd have to set up and deploy PostgREST ser
```
2. Update ToolJet deployment with the appropriate env variables [here](https://raw.githubusercontent.com/ToolJet/ToolJet/main/deploy/kubernetes/GKE/deployment.yaml) and apply the changes.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.1.0/setup/kubernetes.md b/docs/versioned_docs/version-2.1.0/setup/kubernetes.md
index f3caf2b871..b3bd0050f2 100644
--- a/docs/versioned_docs/version-2.1.0/setup/kubernetes.md
+++ b/docs/versioned_docs/version-2.1.0/setup/kubernetes.md
@@ -61,3 +61,19 @@ If you intend to use this feature, you'd have to set up and deploy PostgREST ser
```
2. Update ToolJet deployment with the appropriate env variables [here](https://raw.githubusercontent.com/ToolJet/ToolJet/main/deploy/kubernetes/deployment.yaml) and apply the changes.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.1.0/setup/openshift.md b/docs/versioned_docs/version-2.1.0/setup/openshift.md
index 1cdb3dd674..28a318e14f 100644
--- a/docs/versioned_docs/version-2.1.0/setup/openshift.md
+++ b/docs/versioned_docs/version-2.1.0/setup/openshift.md
@@ -67,4 +67,20 @@ If you intend to use this feature, you'd have to set up and deploy PostgREST ser
```
https://raw.githubusercontent.com/ToolJet/ToolJet/main/deploy/openshift/postgrest.yaml
-```
\ No newline at end of file
+```
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.1.0/setup/tooljet-subpath.md b/docs/versioned_docs/version-2.1.0/setup/tooljet-subpath.md
index e05625d5d6..51c8a438ad 100644
--- a/docs/versioned_docs/version-2.1.0/setup/tooljet-subpath.md
+++ b/docs/versioned_docs/version-2.1.0/setup/tooljet-subpath.md
@@ -20,4 +20,20 @@ You'll need to setup the following environment variables if ToolJet installation
See all **[Environment Variables](/docs/setup/env-vars)** here.
:::
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
+
diff --git a/docs/versioned_docs/version-2.1.0/setup/try-tooljet.md b/docs/versioned_docs/version-2.1.0/setup/try-tooljet.md
index 7ba26756aa..e2158d85fd 100644
--- a/docs/versioned_docs/version-2.1.0/setup/try-tooljet.md
+++ b/docs/versioned_docs/version-2.1.0/setup/try-tooljet.md
@@ -9,10 +9,11 @@ title: Try ToolJet
You can run the command below to have ToolJet up and running right away.
```bash
-docker run \
+docker run -d \
--name tooljet \
--restart unless-stopped \
-p 80:80 \
+ --platform linux/amd64 \
-v tooljet_data:/var/lib/postgresql/13/main \
tooljet/try:latest
```
diff --git a/docs/versioned_docs/version-2.10.0/setup/azure-container.md b/docs/versioned_docs/version-2.10.0/setup/azure-container.md
index b9e9f9947f..c0d9138d6e 100644
--- a/docs/versioned_docs/version-2.10.0/setup/azure-container.md
+++ b/docs/versioned_docs/version-2.10.0/setup/azure-container.md
@@ -65,3 +65,19 @@ Please note that you need to set up a PostgreSQL database manually to be used by
You can access ToolJet via the application URL provided in the overview tab.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
diff --git a/docs/versioned_docs/version-2.10.0/setup/client.md b/docs/versioned_docs/version-2.10.0/setup/client.md
index ebea627ad9..a29cfb1b60 100644
--- a/docs/versioned_docs/version-2.10.0/setup/client.md
+++ b/docs/versioned_docs/version-2.10.0/setup/client.md
@@ -96,3 +96,19 @@ Summarising the steps below:
```bash
cd tooljet-assets && gcloud app deploy
```
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
diff --git a/docs/versioned_docs/version-2.10.0/setup/digitalocean.md b/docs/versioned_docs/version-2.10.0/setup/digitalocean.md
index a4143f9e4f..ab64f0b3bd 100644
--- a/docs/versioned_docs/version-2.10.0/setup/digitalocean.md
+++ b/docs/versioned_docs/version-2.10.0/setup/digitalocean.md
@@ -64,3 +64,19 @@ Follow the steps below to deploy ToolJet Database on DigitalOcean:
4. Add your newly created PostgREST app to the trusted sources of your managed or separate database.
5. Update your existing ToolJet application deployment with [environment variables](/docs/setup/env-vars#tooljet-database-feature-enable--optional-) required for PostgREST.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.10.0/setup/docker.md b/docs/versioned_docs/version-2.10.0/setup/docker.md
index 9ae083200c..218f995327 100644
--- a/docs/versioned_docs/version-2.10.0/setup/docker.md
+++ b/docs/versioned_docs/version-2.10.0/setup/docker.md
@@ -126,11 +126,29 @@ Confused about which setup to select? Feel free to ask the community via Slack:
`sudo docker-compose up -d`
iv. Setup docker to run without root privileges by following the instructions written here https://docs.docker.com/engine/install/linux-postinstall/
- :::
+:::
-
-
-
-
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
+
+
+
+
+
+
diff --git a/docs/versioned_docs/version-2.10.0/setup/ec2.md b/docs/versioned_docs/version-2.10.0/setup/ec2.md
index 540b16c50d..55b0cdb563 100644
--- a/docs/versioned_docs/version-2.10.0/setup/ec2.md
+++ b/docs/versioned_docs/version-2.10.0/setup/ec2.md
@@ -77,4 +77,26 @@ Follow the steps below to deploy ToolJet on AWS EC2 instances.
ToolJet AMI comes inbuilt with PostgREST. If you intend to use this feature, you'd only have to setup the environment variables in `~/app/.env` file and run `./setup_app` script.
-You can learn more about this feature [here](/docs/tooljet-database).
\ No newline at end of file
+You can learn more about this feature [here](/docs/tooljet-database).
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
+
+
+
+
+
+
diff --git a/docs/versioned_docs/version-2.10.0/setup/ecs.md b/docs/versioned_docs/version-2.10.0/setup/ecs.md
index b16770014a..a21236d5e0 100644
--- a/docs/versioned_docs/version-2.10.0/setup/ecs.md
+++ b/docs/versioned_docs/version-2.10.0/setup/ecs.md
@@ -77,3 +77,18 @@ Follow the steps below to deploy ToolJet on a ECS cluster.
The setup above is just a template. Feel free to update the task definition and configure parameters for resources and environment variables according to your needs.
:::
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.10.0/setup/google-cloud-run.md b/docs/versioned_docs/version-2.10.0/setup/google-cloud-run.md
index fc7dd35617..3d5e7e0344 100644
--- a/docs/versioned_docs/version-2.10.0/setup/google-cloud-run.md
+++ b/docs/versioned_docs/version-2.10.0/setup/google-cloud-run.md
@@ -151,3 +151,20 @@ Once the Service is created and live, to make the Cloud Service URL public. Ple
+
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.10.0/setup/helm.md b/docs/versioned_docs/version-2.10.0/setup/helm.md
index cca63346c1..ce2632a837 100644
--- a/docs/versioned_docs/version-2.10.0/setup/helm.md
+++ b/docs/versioned_docs/version-2.10.0/setup/helm.md
@@ -33,4 +33,20 @@ For more information about the ToolJet database, you can visit [here](/docs/tool
If you plan to use this feature, you need to set up and deploy the PostgREST server, which facilitates querying the ToolJet Database.
-To enable the ToolJet database, please set the environment variable `ENABLE_TOOLJET_DB` to true in the `values.yaml` file.
\ No newline at end of file
+To enable the ToolJet database, please set the environment variable `ENABLE_TOOLJET_DB` to true in the `values.yaml` file.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.10.0/setup/heroku.md b/docs/versioned_docs/version-2.10.0/setup/heroku.md
index 80e14d2c06..eeafb5aa46 100644
--- a/docs/versioned_docs/version-2.10.0/setup/heroku.md
+++ b/docs/versioned_docs/version-2.10.0/setup/heroku.md
@@ -143,3 +143,19 @@ Please install Heroku CLI on your local machine. Please refer Heroku CLI install
Please enter the below env variables in the Tooljet application, under the setting tab. You can also refer environment variable [**here**](/docs/setup/env-vars#tooljet-database).
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.10.0/setup/kubernetes-aks.md b/docs/versioned_docs/version-2.10.0/setup/kubernetes-aks.md
index 7c87caa19d..0dc295d422 100644
--- a/docs/versioned_docs/version-2.10.0/setup/kubernetes-aks.md
+++ b/docs/versioned_docs/version-2.10.0/setup/kubernetes-aks.md
@@ -53,3 +53,19 @@ If you intend to use this feature, you'd have to set up and deploy PostgREST ser
```
2. Update ToolJet deployment with the appropriate env variables [here](https://raw.githubusercontent.com/ToolJet/ToolJet/main/deploy/kubernetes/AKS/deployment.yaml) and apply the changes.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.10.0/setup/kubernetes-gke.md b/docs/versioned_docs/version-2.10.0/setup/kubernetes-gke.md
index af86339fec..2fd124631d 100644
--- a/docs/versioned_docs/version-2.10.0/setup/kubernetes-gke.md
+++ b/docs/versioned_docs/version-2.10.0/setup/kubernetes-gke.md
@@ -79,3 +79,19 @@ If you intend to use this feature, you'd have to set up and deploy PostgREST ser
```
2. Update ToolJet deployment with the appropriate env variables [here](https://raw.githubusercontent.com/ToolJet/ToolJet/main/deploy/kubernetes/GKE/deployment.yaml) and apply the changes.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.10.0/setup/kubernetes.md b/docs/versioned_docs/version-2.10.0/setup/kubernetes.md
index f3caf2b871..b3bd0050f2 100644
--- a/docs/versioned_docs/version-2.10.0/setup/kubernetes.md
+++ b/docs/versioned_docs/version-2.10.0/setup/kubernetes.md
@@ -61,3 +61,19 @@ If you intend to use this feature, you'd have to set up and deploy PostgREST ser
```
2. Update ToolJet deployment with the appropriate env variables [here](https://raw.githubusercontent.com/ToolJet/ToolJet/main/deploy/kubernetes/deployment.yaml) and apply the changes.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.10.0/setup/openshift.md b/docs/versioned_docs/version-2.10.0/setup/openshift.md
index 1cdb3dd674..28a318e14f 100644
--- a/docs/versioned_docs/version-2.10.0/setup/openshift.md
+++ b/docs/versioned_docs/version-2.10.0/setup/openshift.md
@@ -67,4 +67,20 @@ If you intend to use this feature, you'd have to set up and deploy PostgREST ser
```
https://raw.githubusercontent.com/ToolJet/ToolJet/main/deploy/openshift/postgrest.yaml
-```
\ No newline at end of file
+```
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.10.0/setup/tooljet-subpath.md b/docs/versioned_docs/version-2.10.0/setup/tooljet-subpath.md
index e05625d5d6..51c8a438ad 100644
--- a/docs/versioned_docs/version-2.10.0/setup/tooljet-subpath.md
+++ b/docs/versioned_docs/version-2.10.0/setup/tooljet-subpath.md
@@ -20,4 +20,20 @@ You'll need to setup the following environment variables if ToolJet installation
See all **[Environment Variables](/docs/setup/env-vars)** here.
:::
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
+
diff --git a/docs/versioned_docs/version-2.10.0/setup/try-tooljet.md b/docs/versioned_docs/version-2.10.0/setup/try-tooljet.md
index 7ba26756aa..e2158d85fd 100644
--- a/docs/versioned_docs/version-2.10.0/setup/try-tooljet.md
+++ b/docs/versioned_docs/version-2.10.0/setup/try-tooljet.md
@@ -9,10 +9,11 @@ title: Try ToolJet
You can run the command below to have ToolJet up and running right away.
```bash
-docker run \
+docker run -d \
--name tooljet \
--restart unless-stopped \
-p 80:80 \
+ --platform linux/amd64 \
-v tooljet_data:/var/lib/postgresql/13/main \
tooljet/try:latest
```
diff --git a/docs/versioned_docs/version-2.11.0/setup/azure-container.md b/docs/versioned_docs/version-2.11.0/setup/azure-container.md
index b9e9f9947f..c0d9138d6e 100644
--- a/docs/versioned_docs/version-2.11.0/setup/azure-container.md
+++ b/docs/versioned_docs/version-2.11.0/setup/azure-container.md
@@ -65,3 +65,19 @@ Please note that you need to set up a PostgreSQL database manually to be used by
You can access ToolJet via the application URL provided in the overview tab.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
diff --git a/docs/versioned_docs/version-2.11.0/setup/client.md b/docs/versioned_docs/version-2.11.0/setup/client.md
index ebea627ad9..a29cfb1b60 100644
--- a/docs/versioned_docs/version-2.11.0/setup/client.md
+++ b/docs/versioned_docs/version-2.11.0/setup/client.md
@@ -96,3 +96,19 @@ Summarising the steps below:
```bash
cd tooljet-assets && gcloud app deploy
```
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
diff --git a/docs/versioned_docs/version-2.11.0/setup/digitalocean.md b/docs/versioned_docs/version-2.11.0/setup/digitalocean.md
index a4143f9e4f..ab64f0b3bd 100644
--- a/docs/versioned_docs/version-2.11.0/setup/digitalocean.md
+++ b/docs/versioned_docs/version-2.11.0/setup/digitalocean.md
@@ -64,3 +64,19 @@ Follow the steps below to deploy ToolJet Database on DigitalOcean:
4. Add your newly created PostgREST app to the trusted sources of your managed or separate database.
5. Update your existing ToolJet application deployment with [environment variables](/docs/setup/env-vars#tooljet-database-feature-enable--optional-) required for PostgREST.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.11.0/setup/docker.md b/docs/versioned_docs/version-2.11.0/setup/docker.md
index 92f6ffa342..7c36a543fd 100644
--- a/docs/versioned_docs/version-2.11.0/setup/docker.md
+++ b/docs/versioned_docs/version-2.11.0/setup/docker.md
@@ -126,11 +126,29 @@ Confused about which setup to select? Feel free to ask the community via Slack:
`sudo docker-compose up -d`
iv. Setup docker to run without root privileges by following the instructions written here https://docs.docker.com/engine/install/linux-postinstall/
- :::
+:::
-
-
-
-
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
+
+
+
+
+
+
diff --git a/docs/versioned_docs/version-2.11.0/setup/ec2.md b/docs/versioned_docs/version-2.11.0/setup/ec2.md
index 540b16c50d..55b0cdb563 100644
--- a/docs/versioned_docs/version-2.11.0/setup/ec2.md
+++ b/docs/versioned_docs/version-2.11.0/setup/ec2.md
@@ -77,4 +77,26 @@ Follow the steps below to deploy ToolJet on AWS EC2 instances.
ToolJet AMI comes inbuilt with PostgREST. If you intend to use this feature, you'd only have to setup the environment variables in `~/app/.env` file and run `./setup_app` script.
-You can learn more about this feature [here](/docs/tooljet-database).
\ No newline at end of file
+You can learn more about this feature [here](/docs/tooljet-database).
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
+
+
+
+
+
+
diff --git a/docs/versioned_docs/version-2.11.0/setup/ecs.md b/docs/versioned_docs/version-2.11.0/setup/ecs.md
index b16770014a..a21236d5e0 100644
--- a/docs/versioned_docs/version-2.11.0/setup/ecs.md
+++ b/docs/versioned_docs/version-2.11.0/setup/ecs.md
@@ -77,3 +77,18 @@ Follow the steps below to deploy ToolJet on a ECS cluster.
The setup above is just a template. Feel free to update the task definition and configure parameters for resources and environment variables according to your needs.
:::
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.11.0/setup/google-cloud-run.md b/docs/versioned_docs/version-2.11.0/setup/google-cloud-run.md
index fc7dd35617..3d5e7e0344 100644
--- a/docs/versioned_docs/version-2.11.0/setup/google-cloud-run.md
+++ b/docs/versioned_docs/version-2.11.0/setup/google-cloud-run.md
@@ -151,3 +151,20 @@ Once the Service is created and live, to make the Cloud Service URL public. Ple
+
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.11.0/setup/helm.md b/docs/versioned_docs/version-2.11.0/setup/helm.md
index 012819d1f1..ccd6a37c03 100644
--- a/docs/versioned_docs/version-2.11.0/setup/helm.md
+++ b/docs/versioned_docs/version-2.11.0/setup/helm.md
@@ -34,3 +34,19 @@ For more information about the ToolJet database, you can visit [here](/docs/tool
If you plan to use this feature, you need to set up and deploy the PostgREST server, which facilitates querying the ToolJet Database.
To enable the ToolJet database, please set the environment variable `ENABLE_TOOLJET_DB` to true in the `values.yaml` file.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
diff --git a/docs/versioned_docs/version-2.11.0/setup/heroku.md b/docs/versioned_docs/version-2.11.0/setup/heroku.md
index d5f588a5c8..f55ba3b559 100644
--- a/docs/versioned_docs/version-2.11.0/setup/heroku.md
+++ b/docs/versioned_docs/version-2.11.0/setup/heroku.md
@@ -143,3 +143,19 @@ Please install Heroku CLI on your local machine. Please refer Heroku CLI install
Please enter the below env variables in the Tooljet application, under the setting tab. You can also refer environment variable [**here**](/docs/setup/env-vars#tooljet-database).
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.11.0/setup/kubernetes-aks.md b/docs/versioned_docs/version-2.11.0/setup/kubernetes-aks.md
index 7c87caa19d..0dc295d422 100644
--- a/docs/versioned_docs/version-2.11.0/setup/kubernetes-aks.md
+++ b/docs/versioned_docs/version-2.11.0/setup/kubernetes-aks.md
@@ -53,3 +53,19 @@ If you intend to use this feature, you'd have to set up and deploy PostgREST ser
```
2. Update ToolJet deployment with the appropriate env variables [here](https://raw.githubusercontent.com/ToolJet/ToolJet/main/deploy/kubernetes/AKS/deployment.yaml) and apply the changes.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.11.0/setup/kubernetes-gke.md b/docs/versioned_docs/version-2.11.0/setup/kubernetes-gke.md
index af86339fec..2fd124631d 100644
--- a/docs/versioned_docs/version-2.11.0/setup/kubernetes-gke.md
+++ b/docs/versioned_docs/version-2.11.0/setup/kubernetes-gke.md
@@ -79,3 +79,19 @@ If you intend to use this feature, you'd have to set up and deploy PostgREST ser
```
2. Update ToolJet deployment with the appropriate env variables [here](https://raw.githubusercontent.com/ToolJet/ToolJet/main/deploy/kubernetes/GKE/deployment.yaml) and apply the changes.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.11.0/setup/kubernetes.md b/docs/versioned_docs/version-2.11.0/setup/kubernetes.md
index f3caf2b871..b3bd0050f2 100644
--- a/docs/versioned_docs/version-2.11.0/setup/kubernetes.md
+++ b/docs/versioned_docs/version-2.11.0/setup/kubernetes.md
@@ -61,3 +61,19 @@ If you intend to use this feature, you'd have to set up and deploy PostgREST ser
```
2. Update ToolJet deployment with the appropriate env variables [here](https://raw.githubusercontent.com/ToolJet/ToolJet/main/deploy/kubernetes/deployment.yaml) and apply the changes.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.11.0/setup/openshift.md b/docs/versioned_docs/version-2.11.0/setup/openshift.md
index 37031e08d3..0be01d8eb1 100644
--- a/docs/versioned_docs/version-2.11.0/setup/openshift.md
+++ b/docs/versioned_docs/version-2.11.0/setup/openshift.md
@@ -67,4 +67,20 @@ If you intend to use this feature, you'd have to set up and deploy PostgREST ser
```
https://raw.githubusercontent.com/ToolJet/ToolJet/main/deploy/openshift/postgrest.yaml
-```
\ No newline at end of file
+```
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.11.0/setup/tooljet-subpath.md b/docs/versioned_docs/version-2.11.0/setup/tooljet-subpath.md
index e05625d5d6..51c8a438ad 100644
--- a/docs/versioned_docs/version-2.11.0/setup/tooljet-subpath.md
+++ b/docs/versioned_docs/version-2.11.0/setup/tooljet-subpath.md
@@ -20,4 +20,20 @@ You'll need to setup the following environment variables if ToolJet installation
See all **[Environment Variables](/docs/setup/env-vars)** here.
:::
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
+
diff --git a/docs/versioned_docs/version-2.11.0/setup/try-tooljet.md b/docs/versioned_docs/version-2.11.0/setup/try-tooljet.md
index 7ba26756aa..e2158d85fd 100644
--- a/docs/versioned_docs/version-2.11.0/setup/try-tooljet.md
+++ b/docs/versioned_docs/version-2.11.0/setup/try-tooljet.md
@@ -9,10 +9,11 @@ title: Try ToolJet
You can run the command below to have ToolJet up and running right away.
```bash
-docker run \
+docker run -d \
--name tooljet \
--restart unless-stopped \
-p 80:80 \
+ --platform linux/amd64 \
-v tooljet_data:/var/lib/postgresql/13/main \
tooljet/try:latest
```
diff --git a/docs/versioned_docs/version-2.12.0/setup/azure-container.md b/docs/versioned_docs/version-2.12.0/setup/azure-container.md
index b9e9f9947f..c0d9138d6e 100644
--- a/docs/versioned_docs/version-2.12.0/setup/azure-container.md
+++ b/docs/versioned_docs/version-2.12.0/setup/azure-container.md
@@ -65,3 +65,19 @@ Please note that you need to set up a PostgreSQL database manually to be used by
You can access ToolJet via the application URL provided in the overview tab.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
diff --git a/docs/versioned_docs/version-2.12.0/setup/client.md b/docs/versioned_docs/version-2.12.0/setup/client.md
index ebea627ad9..a29cfb1b60 100644
--- a/docs/versioned_docs/version-2.12.0/setup/client.md
+++ b/docs/versioned_docs/version-2.12.0/setup/client.md
@@ -96,3 +96,19 @@ Summarising the steps below:
```bash
cd tooljet-assets && gcloud app deploy
```
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
diff --git a/docs/versioned_docs/version-2.12.0/setup/digitalocean.md b/docs/versioned_docs/version-2.12.0/setup/digitalocean.md
index a4143f9e4f..ab64f0b3bd 100644
--- a/docs/versioned_docs/version-2.12.0/setup/digitalocean.md
+++ b/docs/versioned_docs/version-2.12.0/setup/digitalocean.md
@@ -64,3 +64,19 @@ Follow the steps below to deploy ToolJet Database on DigitalOcean:
4. Add your newly created PostgREST app to the trusted sources of your managed or separate database.
5. Update your existing ToolJet application deployment with [environment variables](/docs/setup/env-vars#tooljet-database-feature-enable--optional-) required for PostgREST.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.12.0/setup/docker.md b/docs/versioned_docs/version-2.12.0/setup/docker.md
index 0308312d21..76bd557503 100644
--- a/docs/versioned_docs/version-2.12.0/setup/docker.md
+++ b/docs/versioned_docs/version-2.12.0/setup/docker.md
@@ -126,11 +126,29 @@ Confused about which setup to select? Feel free to ask the community via Slack:
`sudo docker-compose up -d`
iv. Setup docker to run without root privileges by following the instructions written here https://docs.docker.com/engine/install/linux-postinstall/
- :::
+:::
-
-
-
-
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
+
+
+
+
+
+
diff --git a/docs/versioned_docs/version-2.12.0/setup/ec2.md b/docs/versioned_docs/version-2.12.0/setup/ec2.md
index 540b16c50d..55b0cdb563 100644
--- a/docs/versioned_docs/version-2.12.0/setup/ec2.md
+++ b/docs/versioned_docs/version-2.12.0/setup/ec2.md
@@ -77,4 +77,26 @@ Follow the steps below to deploy ToolJet on AWS EC2 instances.
ToolJet AMI comes inbuilt with PostgREST. If you intend to use this feature, you'd only have to setup the environment variables in `~/app/.env` file and run `./setup_app` script.
-You can learn more about this feature [here](/docs/tooljet-database).
\ No newline at end of file
+You can learn more about this feature [here](/docs/tooljet-database).
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
+
+
+
+
+
+
diff --git a/docs/versioned_docs/version-2.12.0/setup/ecs.md b/docs/versioned_docs/version-2.12.0/setup/ecs.md
index b16770014a..a21236d5e0 100644
--- a/docs/versioned_docs/version-2.12.0/setup/ecs.md
+++ b/docs/versioned_docs/version-2.12.0/setup/ecs.md
@@ -77,3 +77,18 @@ Follow the steps below to deploy ToolJet on a ECS cluster.
The setup above is just a template. Feel free to update the task definition and configure parameters for resources and environment variables according to your needs.
:::
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.12.0/setup/google-cloud-run.md b/docs/versioned_docs/version-2.12.0/setup/google-cloud-run.md
index fc7dd35617..3d5e7e0344 100644
--- a/docs/versioned_docs/version-2.12.0/setup/google-cloud-run.md
+++ b/docs/versioned_docs/version-2.12.0/setup/google-cloud-run.md
@@ -151,3 +151,20 @@ Once the Service is created and live, to make the Cloud Service URL public. Ple
+
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.12.0/setup/helm.md b/docs/versioned_docs/version-2.12.0/setup/helm.md
index cca63346c1..ce2632a837 100644
--- a/docs/versioned_docs/version-2.12.0/setup/helm.md
+++ b/docs/versioned_docs/version-2.12.0/setup/helm.md
@@ -33,4 +33,20 @@ For more information about the ToolJet database, you can visit [here](/docs/tool
If you plan to use this feature, you need to set up and deploy the PostgREST server, which facilitates querying the ToolJet Database.
-To enable the ToolJet database, please set the environment variable `ENABLE_TOOLJET_DB` to true in the `values.yaml` file.
\ No newline at end of file
+To enable the ToolJet database, please set the environment variable `ENABLE_TOOLJET_DB` to true in the `values.yaml` file.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.12.0/setup/heroku.md b/docs/versioned_docs/version-2.12.0/setup/heroku.md
index 80e14d2c06..eeafb5aa46 100644
--- a/docs/versioned_docs/version-2.12.0/setup/heroku.md
+++ b/docs/versioned_docs/version-2.12.0/setup/heroku.md
@@ -143,3 +143,19 @@ Please install Heroku CLI on your local machine. Please refer Heroku CLI install
Please enter the below env variables in the Tooljet application, under the setting tab. You can also refer environment variable [**here**](/docs/setup/env-vars#tooljet-database).
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.12.0/setup/kubernetes-aks.md b/docs/versioned_docs/version-2.12.0/setup/kubernetes-aks.md
index 7c87caa19d..0dc295d422 100644
--- a/docs/versioned_docs/version-2.12.0/setup/kubernetes-aks.md
+++ b/docs/versioned_docs/version-2.12.0/setup/kubernetes-aks.md
@@ -53,3 +53,19 @@ If you intend to use this feature, you'd have to set up and deploy PostgREST ser
```
2. Update ToolJet deployment with the appropriate env variables [here](https://raw.githubusercontent.com/ToolJet/ToolJet/main/deploy/kubernetes/AKS/deployment.yaml) and apply the changes.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.12.0/setup/kubernetes-gke.md b/docs/versioned_docs/version-2.12.0/setup/kubernetes-gke.md
index af86339fec..2fd124631d 100644
--- a/docs/versioned_docs/version-2.12.0/setup/kubernetes-gke.md
+++ b/docs/versioned_docs/version-2.12.0/setup/kubernetes-gke.md
@@ -79,3 +79,19 @@ If you intend to use this feature, you'd have to set up and deploy PostgREST ser
```
2. Update ToolJet deployment with the appropriate env variables [here](https://raw.githubusercontent.com/ToolJet/ToolJet/main/deploy/kubernetes/GKE/deployment.yaml) and apply the changes.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.12.0/setup/kubernetes.md b/docs/versioned_docs/version-2.12.0/setup/kubernetes.md
index f3caf2b871..b3bd0050f2 100644
--- a/docs/versioned_docs/version-2.12.0/setup/kubernetes.md
+++ b/docs/versioned_docs/version-2.12.0/setup/kubernetes.md
@@ -61,3 +61,19 @@ If you intend to use this feature, you'd have to set up and deploy PostgREST ser
```
2. Update ToolJet deployment with the appropriate env variables [here](https://raw.githubusercontent.com/ToolJet/ToolJet/main/deploy/kubernetes/deployment.yaml) and apply the changes.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.12.0/setup/openshift.md b/docs/versioned_docs/version-2.12.0/setup/openshift.md
index 1cdb3dd674..28a318e14f 100644
--- a/docs/versioned_docs/version-2.12.0/setup/openshift.md
+++ b/docs/versioned_docs/version-2.12.0/setup/openshift.md
@@ -67,4 +67,20 @@ If you intend to use this feature, you'd have to set up and deploy PostgREST ser
```
https://raw.githubusercontent.com/ToolJet/ToolJet/main/deploy/openshift/postgrest.yaml
-```
\ No newline at end of file
+```
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.12.0/setup/tooljet-subpath.md b/docs/versioned_docs/version-2.12.0/setup/tooljet-subpath.md
index e05625d5d6..51c8a438ad 100644
--- a/docs/versioned_docs/version-2.12.0/setup/tooljet-subpath.md
+++ b/docs/versioned_docs/version-2.12.0/setup/tooljet-subpath.md
@@ -20,4 +20,20 @@ You'll need to setup the following environment variables if ToolJet installation
See all **[Environment Variables](/docs/setup/env-vars)** here.
:::
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
+
diff --git a/docs/versioned_docs/version-2.12.0/setup/try-tooljet.md b/docs/versioned_docs/version-2.12.0/setup/try-tooljet.md
index eb60b5323a..59c9108cf2 100644
--- a/docs/versioned_docs/version-2.12.0/setup/try-tooljet.md
+++ b/docs/versioned_docs/version-2.12.0/setup/try-tooljet.md
@@ -10,16 +10,16 @@ title: Try ToolJet
You can run the command below to have ToolJet up and running right away.
```bash
-docker run \
+docker run -d \
--name tooljet \
--restart unless-stopped \
-p 80:80 \
+ --platform linux/amd64 \
-v tooljet_data:/var/lib/postgresql/13/main \
tooljet/try:latest
```
*If you have any questions feel free to join our [Slack Community](https://tooljet.com/slack) or send us an email at hello@tooljet.com.*
-
#### Setup information
- Runs the ToolJet server on the port 80 on your machine.
diff --git a/docs/versioned_docs/version-2.13.0/setup/azure-container.md b/docs/versioned_docs/version-2.13.0/setup/azure-container.md
index b9e9f9947f..c0d9138d6e 100644
--- a/docs/versioned_docs/version-2.13.0/setup/azure-container.md
+++ b/docs/versioned_docs/version-2.13.0/setup/azure-container.md
@@ -65,3 +65,19 @@ Please note that you need to set up a PostgreSQL database manually to be used by
You can access ToolJet via the application URL provided in the overview tab.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
diff --git a/docs/versioned_docs/version-2.13.0/setup/client.md b/docs/versioned_docs/version-2.13.0/setup/client.md
index ebea627ad9..a29cfb1b60 100644
--- a/docs/versioned_docs/version-2.13.0/setup/client.md
+++ b/docs/versioned_docs/version-2.13.0/setup/client.md
@@ -96,3 +96,19 @@ Summarising the steps below:
```bash
cd tooljet-assets && gcloud app deploy
```
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
diff --git a/docs/versioned_docs/version-2.13.0/setup/digitalocean.md b/docs/versioned_docs/version-2.13.0/setup/digitalocean.md
index a4143f9e4f..ab64f0b3bd 100644
--- a/docs/versioned_docs/version-2.13.0/setup/digitalocean.md
+++ b/docs/versioned_docs/version-2.13.0/setup/digitalocean.md
@@ -64,3 +64,19 @@ Follow the steps below to deploy ToolJet Database on DigitalOcean:
4. Add your newly created PostgREST app to the trusted sources of your managed or separate database.
5. Update your existing ToolJet application deployment with [environment variables](/docs/setup/env-vars#tooljet-database-feature-enable--optional-) required for PostgREST.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.13.0/setup/docker.md b/docs/versioned_docs/version-2.13.0/setup/docker.md
index 0308312d21..76bd557503 100644
--- a/docs/versioned_docs/version-2.13.0/setup/docker.md
+++ b/docs/versioned_docs/version-2.13.0/setup/docker.md
@@ -126,11 +126,29 @@ Confused about which setup to select? Feel free to ask the community via Slack:
`sudo docker-compose up -d`
iv. Setup docker to run without root privileges by following the instructions written here https://docs.docker.com/engine/install/linux-postinstall/
- :::
+:::
-
-
-
-
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
+
+
+
+
+
+
diff --git a/docs/versioned_docs/version-2.13.0/setup/ec2.md b/docs/versioned_docs/version-2.13.0/setup/ec2.md
index 540b16c50d..55b0cdb563 100644
--- a/docs/versioned_docs/version-2.13.0/setup/ec2.md
+++ b/docs/versioned_docs/version-2.13.0/setup/ec2.md
@@ -77,4 +77,26 @@ Follow the steps below to deploy ToolJet on AWS EC2 instances.
ToolJet AMI comes inbuilt with PostgREST. If you intend to use this feature, you'd only have to setup the environment variables in `~/app/.env` file and run `./setup_app` script.
-You can learn more about this feature [here](/docs/tooljet-database).
\ No newline at end of file
+You can learn more about this feature [here](/docs/tooljet-database).
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
+
+
+
+
+
+
diff --git a/docs/versioned_docs/version-2.13.0/setup/ecs.md b/docs/versioned_docs/version-2.13.0/setup/ecs.md
index b16770014a..a21236d5e0 100644
--- a/docs/versioned_docs/version-2.13.0/setup/ecs.md
+++ b/docs/versioned_docs/version-2.13.0/setup/ecs.md
@@ -77,3 +77,18 @@ Follow the steps below to deploy ToolJet on a ECS cluster.
The setup above is just a template. Feel free to update the task definition and configure parameters for resources and environment variables according to your needs.
:::
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.13.0/setup/google-cloud-run.md b/docs/versioned_docs/version-2.13.0/setup/google-cloud-run.md
index fc7dd35617..3d5e7e0344 100644
--- a/docs/versioned_docs/version-2.13.0/setup/google-cloud-run.md
+++ b/docs/versioned_docs/version-2.13.0/setup/google-cloud-run.md
@@ -151,3 +151,20 @@ Once the Service is created and live, to make the Cloud Service URL public. Ple
+
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.13.0/setup/helm.md b/docs/versioned_docs/version-2.13.0/setup/helm.md
index cca63346c1..ce2632a837 100644
--- a/docs/versioned_docs/version-2.13.0/setup/helm.md
+++ b/docs/versioned_docs/version-2.13.0/setup/helm.md
@@ -33,4 +33,20 @@ For more information about the ToolJet database, you can visit [here](/docs/tool
If you plan to use this feature, you need to set up and deploy the PostgREST server, which facilitates querying the ToolJet Database.
-To enable the ToolJet database, please set the environment variable `ENABLE_TOOLJET_DB` to true in the `values.yaml` file.
\ No newline at end of file
+To enable the ToolJet database, please set the environment variable `ENABLE_TOOLJET_DB` to true in the `values.yaml` file.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.13.0/setup/heroku.md b/docs/versioned_docs/version-2.13.0/setup/heroku.md
index 80e14d2c06..eeafb5aa46 100644
--- a/docs/versioned_docs/version-2.13.0/setup/heroku.md
+++ b/docs/versioned_docs/version-2.13.0/setup/heroku.md
@@ -143,3 +143,19 @@ Please install Heroku CLI on your local machine. Please refer Heroku CLI install
Please enter the below env variables in the Tooljet application, under the setting tab. You can also refer environment variable [**here**](/docs/setup/env-vars#tooljet-database).
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.13.0/setup/kubernetes-aks.md b/docs/versioned_docs/version-2.13.0/setup/kubernetes-aks.md
index 7c87caa19d..0dc295d422 100644
--- a/docs/versioned_docs/version-2.13.0/setup/kubernetes-aks.md
+++ b/docs/versioned_docs/version-2.13.0/setup/kubernetes-aks.md
@@ -53,3 +53,19 @@ If you intend to use this feature, you'd have to set up and deploy PostgREST ser
```
2. Update ToolJet deployment with the appropriate env variables [here](https://raw.githubusercontent.com/ToolJet/ToolJet/main/deploy/kubernetes/AKS/deployment.yaml) and apply the changes.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.13.0/setup/kubernetes-gke.md b/docs/versioned_docs/version-2.13.0/setup/kubernetes-gke.md
index af86339fec..2fd124631d 100644
--- a/docs/versioned_docs/version-2.13.0/setup/kubernetes-gke.md
+++ b/docs/versioned_docs/version-2.13.0/setup/kubernetes-gke.md
@@ -79,3 +79,19 @@ If you intend to use this feature, you'd have to set up and deploy PostgREST ser
```
2. Update ToolJet deployment with the appropriate env variables [here](https://raw.githubusercontent.com/ToolJet/ToolJet/main/deploy/kubernetes/GKE/deployment.yaml) and apply the changes.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.13.0/setup/kubernetes.md b/docs/versioned_docs/version-2.13.0/setup/kubernetes.md
index 1f8991660b..6a8ad54279 100644
--- a/docs/versioned_docs/version-2.13.0/setup/kubernetes.md
+++ b/docs/versioned_docs/version-2.13.0/setup/kubernetes.md
@@ -62,3 +62,19 @@ If you intend to use this feature, you'd have to set up and deploy PostgREST ser
```
2. Update ToolJet deployment with the appropriate env variables [here](https://raw.githubusercontent.com/ToolJet/ToolJet/main/deploy/kubernetes/deployment.yaml) and apply the changes.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.13.0/setup/openshift.md b/docs/versioned_docs/version-2.13.0/setup/openshift.md
index 1cdb3dd674..28a318e14f 100644
--- a/docs/versioned_docs/version-2.13.0/setup/openshift.md
+++ b/docs/versioned_docs/version-2.13.0/setup/openshift.md
@@ -67,4 +67,20 @@ If you intend to use this feature, you'd have to set up and deploy PostgREST ser
```
https://raw.githubusercontent.com/ToolJet/ToolJet/main/deploy/openshift/postgrest.yaml
-```
\ No newline at end of file
+```
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.13.0/setup/tooljet-subpath.md b/docs/versioned_docs/version-2.13.0/setup/tooljet-subpath.md
index e05625d5d6..51c8a438ad 100644
--- a/docs/versioned_docs/version-2.13.0/setup/tooljet-subpath.md
+++ b/docs/versioned_docs/version-2.13.0/setup/tooljet-subpath.md
@@ -20,4 +20,20 @@ You'll need to setup the following environment variables if ToolJet installation
See all **[Environment Variables](/docs/setup/env-vars)** here.
:::
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
+
diff --git a/docs/versioned_docs/version-2.13.0/setup/try-tooljet.md b/docs/versioned_docs/version-2.13.0/setup/try-tooljet.md
index eb60b5323a..59c9108cf2 100644
--- a/docs/versioned_docs/version-2.13.0/setup/try-tooljet.md
+++ b/docs/versioned_docs/version-2.13.0/setup/try-tooljet.md
@@ -10,16 +10,16 @@ title: Try ToolJet
You can run the command below to have ToolJet up and running right away.
```bash
-docker run \
+docker run -d \
--name tooljet \
--restart unless-stopped \
-p 80:80 \
+ --platform linux/amd64 \
-v tooljet_data:/var/lib/postgresql/13/main \
tooljet/try:latest
```
*If you have any questions feel free to join our [Slack Community](https://tooljet.com/slack) or send us an email at hello@tooljet.com.*
-
#### Setup information
- Runs the ToolJet server on the port 80 on your machine.
diff --git a/docs/versioned_docs/version-2.14.0/setup/azure-container.md b/docs/versioned_docs/version-2.14.0/setup/azure-container.md
index b9e9f9947f..c0d9138d6e 100644
--- a/docs/versioned_docs/version-2.14.0/setup/azure-container.md
+++ b/docs/versioned_docs/version-2.14.0/setup/azure-container.md
@@ -65,3 +65,19 @@ Please note that you need to set up a PostgreSQL database manually to be used by
You can access ToolJet via the application URL provided in the overview tab.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
diff --git a/docs/versioned_docs/version-2.14.0/setup/client.md b/docs/versioned_docs/version-2.14.0/setup/client.md
index ebea627ad9..a29cfb1b60 100644
--- a/docs/versioned_docs/version-2.14.0/setup/client.md
+++ b/docs/versioned_docs/version-2.14.0/setup/client.md
@@ -96,3 +96,19 @@ Summarising the steps below:
```bash
cd tooljet-assets && gcloud app deploy
```
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
diff --git a/docs/versioned_docs/version-2.14.0/setup/digitalocean.md b/docs/versioned_docs/version-2.14.0/setup/digitalocean.md
index a4143f9e4f..ab64f0b3bd 100644
--- a/docs/versioned_docs/version-2.14.0/setup/digitalocean.md
+++ b/docs/versioned_docs/version-2.14.0/setup/digitalocean.md
@@ -64,3 +64,19 @@ Follow the steps below to deploy ToolJet Database on DigitalOcean:
4. Add your newly created PostgREST app to the trusted sources of your managed or separate database.
5. Update your existing ToolJet application deployment with [environment variables](/docs/setup/env-vars#tooljet-database-feature-enable--optional-) required for PostgREST.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.14.0/setup/docker.md b/docs/versioned_docs/version-2.14.0/setup/docker.md
index 0308312d21..76bd557503 100644
--- a/docs/versioned_docs/version-2.14.0/setup/docker.md
+++ b/docs/versioned_docs/version-2.14.0/setup/docker.md
@@ -126,11 +126,29 @@ Confused about which setup to select? Feel free to ask the community via Slack:
`sudo docker-compose up -d`
iv. Setup docker to run without root privileges by following the instructions written here https://docs.docker.com/engine/install/linux-postinstall/
- :::
+:::
-
-
-
-
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
+
+
+
+
+
+
diff --git a/docs/versioned_docs/version-2.14.0/setup/ec2.md b/docs/versioned_docs/version-2.14.0/setup/ec2.md
index 540b16c50d..55b0cdb563 100644
--- a/docs/versioned_docs/version-2.14.0/setup/ec2.md
+++ b/docs/versioned_docs/version-2.14.0/setup/ec2.md
@@ -77,4 +77,26 @@ Follow the steps below to deploy ToolJet on AWS EC2 instances.
ToolJet AMI comes inbuilt with PostgREST. If you intend to use this feature, you'd only have to setup the environment variables in `~/app/.env` file and run `./setup_app` script.
-You can learn more about this feature [here](/docs/tooljet-database).
\ No newline at end of file
+You can learn more about this feature [here](/docs/tooljet-database).
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
+
+
+
+
+
+
diff --git a/docs/versioned_docs/version-2.14.0/setup/ecs.md b/docs/versioned_docs/version-2.14.0/setup/ecs.md
index b16770014a..a21236d5e0 100644
--- a/docs/versioned_docs/version-2.14.0/setup/ecs.md
+++ b/docs/versioned_docs/version-2.14.0/setup/ecs.md
@@ -77,3 +77,18 @@ Follow the steps below to deploy ToolJet on a ECS cluster.
The setup above is just a template. Feel free to update the task definition and configure parameters for resources and environment variables according to your needs.
:::
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.14.0/setup/google-cloud-run.md b/docs/versioned_docs/version-2.14.0/setup/google-cloud-run.md
index fc7dd35617..3d5e7e0344 100644
--- a/docs/versioned_docs/version-2.14.0/setup/google-cloud-run.md
+++ b/docs/versioned_docs/version-2.14.0/setup/google-cloud-run.md
@@ -151,3 +151,20 @@ Once the Service is created and live, to make the Cloud Service URL public. Ple
+
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.14.0/setup/helm.md b/docs/versioned_docs/version-2.14.0/setup/helm.md
index cca63346c1..ce2632a837 100644
--- a/docs/versioned_docs/version-2.14.0/setup/helm.md
+++ b/docs/versioned_docs/version-2.14.0/setup/helm.md
@@ -33,4 +33,20 @@ For more information about the ToolJet database, you can visit [here](/docs/tool
If you plan to use this feature, you need to set up and deploy the PostgREST server, which facilitates querying the ToolJet Database.
-To enable the ToolJet database, please set the environment variable `ENABLE_TOOLJET_DB` to true in the `values.yaml` file.
\ No newline at end of file
+To enable the ToolJet database, please set the environment variable `ENABLE_TOOLJET_DB` to true in the `values.yaml` file.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.14.0/setup/heroku.md b/docs/versioned_docs/version-2.14.0/setup/heroku.md
index 80e14d2c06..eeafb5aa46 100644
--- a/docs/versioned_docs/version-2.14.0/setup/heroku.md
+++ b/docs/versioned_docs/version-2.14.0/setup/heroku.md
@@ -143,3 +143,19 @@ Please install Heroku CLI on your local machine. Please refer Heroku CLI install
Please enter the below env variables in the Tooljet application, under the setting tab. You can also refer environment variable [**here**](/docs/setup/env-vars#tooljet-database).
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.14.0/setup/kubernetes-aks.md b/docs/versioned_docs/version-2.14.0/setup/kubernetes-aks.md
index 7c87caa19d..0dc295d422 100644
--- a/docs/versioned_docs/version-2.14.0/setup/kubernetes-aks.md
+++ b/docs/versioned_docs/version-2.14.0/setup/kubernetes-aks.md
@@ -53,3 +53,19 @@ If you intend to use this feature, you'd have to set up and deploy PostgREST ser
```
2. Update ToolJet deployment with the appropriate env variables [here](https://raw.githubusercontent.com/ToolJet/ToolJet/main/deploy/kubernetes/AKS/deployment.yaml) and apply the changes.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.14.0/setup/kubernetes-gke.md b/docs/versioned_docs/version-2.14.0/setup/kubernetes-gke.md
index af86339fec..2fd124631d 100644
--- a/docs/versioned_docs/version-2.14.0/setup/kubernetes-gke.md
+++ b/docs/versioned_docs/version-2.14.0/setup/kubernetes-gke.md
@@ -79,3 +79,19 @@ If you intend to use this feature, you'd have to set up and deploy PostgREST ser
```
2. Update ToolJet deployment with the appropriate env variables [here](https://raw.githubusercontent.com/ToolJet/ToolJet/main/deploy/kubernetes/GKE/deployment.yaml) and apply the changes.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.14.0/setup/kubernetes.md b/docs/versioned_docs/version-2.14.0/setup/kubernetes.md
index 1f8991660b..6a8ad54279 100644
--- a/docs/versioned_docs/version-2.14.0/setup/kubernetes.md
+++ b/docs/versioned_docs/version-2.14.0/setup/kubernetes.md
@@ -62,3 +62,19 @@ If you intend to use this feature, you'd have to set up and deploy PostgREST ser
```
2. Update ToolJet deployment with the appropriate env variables [here](https://raw.githubusercontent.com/ToolJet/ToolJet/main/deploy/kubernetes/deployment.yaml) and apply the changes.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.14.0/setup/openshift.md b/docs/versioned_docs/version-2.14.0/setup/openshift.md
index 1cdb3dd674..28a318e14f 100644
--- a/docs/versioned_docs/version-2.14.0/setup/openshift.md
+++ b/docs/versioned_docs/version-2.14.0/setup/openshift.md
@@ -67,4 +67,20 @@ If you intend to use this feature, you'd have to set up and deploy PostgREST ser
```
https://raw.githubusercontent.com/ToolJet/ToolJet/main/deploy/openshift/postgrest.yaml
-```
\ No newline at end of file
+```
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.14.0/setup/tooljet-subpath.md b/docs/versioned_docs/version-2.14.0/setup/tooljet-subpath.md
index e05625d5d6..51c8a438ad 100644
--- a/docs/versioned_docs/version-2.14.0/setup/tooljet-subpath.md
+++ b/docs/versioned_docs/version-2.14.0/setup/tooljet-subpath.md
@@ -20,4 +20,20 @@ You'll need to setup the following environment variables if ToolJet installation
See all **[Environment Variables](/docs/setup/env-vars)** here.
:::
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
+
diff --git a/docs/versioned_docs/version-2.14.0/setup/try-tooljet.md b/docs/versioned_docs/version-2.14.0/setup/try-tooljet.md
index eb60b5323a..59c9108cf2 100644
--- a/docs/versioned_docs/version-2.14.0/setup/try-tooljet.md
+++ b/docs/versioned_docs/version-2.14.0/setup/try-tooljet.md
@@ -10,16 +10,16 @@ title: Try ToolJet
You can run the command below to have ToolJet up and running right away.
```bash
-docker run \
+docker run -d \
--name tooljet \
--restart unless-stopped \
-p 80:80 \
+ --platform linux/amd64 \
-v tooljet_data:/var/lib/postgresql/13/main \
tooljet/try:latest
```
*If you have any questions feel free to join our [Slack Community](https://tooljet.com/slack) or send us an email at hello@tooljet.com.*
-
#### Setup information
- Runs the ToolJet server on the port 80 on your machine.
diff --git a/docs/versioned_docs/version-2.15.0/contributing-guide/setup/codespaces.md b/docs/versioned_docs/version-2.15.0/contributing-guide/setup/codespaces.md
new file mode 100644
index 0000000000..1204d71f63
--- /dev/null
+++ b/docs/versioned_docs/version-2.15.0/contributing-guide/setup/codespaces.md
@@ -0,0 +1,117 @@
+---
+id: codespaces
+title: GitHub Codespaces
+---
+
+Follow the steps below to set up ToolJet on GitHub Codespaces. We recommend reading our guide on [architecture](https://docs.tooljet.com/docs/contributing-guide/setup/architecture) of ToolJet before proceeding.
+
+Open the terminal and run the commands below.
+
+## Setting up
+
+### 1. Set up the environment
+
+1. Install Node.js ( version: v18.3.0 ) and npm (version: v8.11.0)
+
+```
+nvm install 18.3.0
+nvm use 18.3.0
+npm install -g npm@8.11.0
+```
+
+2. Install Postgres
+
+```
+sudo sh -c 'echo "deb [http://apt.postgresql.org/pub/repos/apt](http://apt.postgresql.org/pub/repos/apt) $(lsb_release -cs)-pgdg main" > /etc/apt/sources.list.d/pgdg.list'
+
+wget --quiet -O - [https://www.postgresql.org/media/keys/ACCC4CF8.asc](https://www.postgresql.org/media/keys/ACCC4CF8.asc) | sudo apt-key add -
+
+sudo apt-get update
+
+sudo apt-get install postgresql-13 postgresql-contrib-13
+```
+
+To start the postgresql service run the below command:
+
+```
+sudo service postgresql start
+```
+
+If you wish to change the password of the installed postresql service run the below commands:
+
+```
+sudo su
+
+sudo -u postgres psql
+
+\password postgres
+
+\q
+```
+
+### 2. Set up environment variables
+
+Create a `.env` file by running the command `touch .env`. More information on the variables that can be set is given in the [environment variables reference](https://docs.tooljet.com/docs/setup/env-vars)
+
+**For basic set-up you add the below env variables:**
+
+```
+TOOLJET_HOST=http://localhost:3000
+
+LOCKBOX_MASTER_KEY=
+
+SECRET_KEY_BASE=
+
+PG_USER=postgres
+
+PG_HOST=localhost
+
+PG_PASS=postgres
+
+PG_DB=tooljet_prod
+
+SUB_PATH=/apps/tooljet/
+
+NODE_ENV=production
+
+SERVE_CLIENT=true
+```
+
+> `SECRET_KEY_BASE` requires a 64 byte key. (If you have `openssl` installed, run `openssl rand -hex 64` to create a 64 byte secure random key)
+>
+> `LOCKBOX_MASTER_KEY` requires a 32 byte key. (Run `openssl rand -hex 32` to create a 32 byte secure random key)
+
+### 3. Install and build dependencies
+
+Make sure node version is set to 18.3.0 before running the below command:
+
+```
+npm install
+npm install --prefix server
+npm install --prefix frontend
+npm run build:plugins
+```
+
+
+### 4. Set up database
+
+```
+npm run --prefix server db:create
+npm run --prefix server db:mirgate
+```
+
+If at any point you need to reset the database, use this command `npm run --prefix server db:reset`
+
+### 5. Build client
+
+```
+cd ./frontend && NODE=production npm run build
+```
+
+### 6. Run server
+
+```
+cd ./server && npm run start:prod
+```
+
+The client will start on the **port 3000**, you can access the client by visiting the url created by codespace - `https:///apps/tooljet`
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.15.0/setup/azure-container.md b/docs/versioned_docs/version-2.15.0/setup/azure-container.md
index 60bdc0aaa5..fe19e718dc 100644
--- a/docs/versioned_docs/version-2.15.0/setup/azure-container.md
+++ b/docs/versioned_docs/version-2.15.0/setup/azure-container.md
@@ -68,3 +68,19 @@ Please note that you need to set up a PostgreSQL database manually to be used by
You can access ToolJet via the application URL provided in the overview tab.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
diff --git a/docs/versioned_docs/version-2.15.0/setup/client.md b/docs/versioned_docs/version-2.15.0/setup/client.md
index ebea627ad9..a29cfb1b60 100644
--- a/docs/versioned_docs/version-2.15.0/setup/client.md
+++ b/docs/versioned_docs/version-2.15.0/setup/client.md
@@ -96,3 +96,19 @@ Summarising the steps below:
```bash
cd tooljet-assets && gcloud app deploy
```
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
diff --git a/docs/versioned_docs/version-2.15.0/setup/digitalocean.md b/docs/versioned_docs/version-2.15.0/setup/digitalocean.md
index 0030942f83..03c485dcf5 100644
--- a/docs/versioned_docs/version-2.15.0/setup/digitalocean.md
+++ b/docs/versioned_docs/version-2.15.0/setup/digitalocean.md
@@ -107,3 +107,19 @@ Follow the steps below to deploy ToolJet Database on DigitalOcean:
4. Add your newly created PostgREST app to the trusted sources of your managed or separate database.
5. Update your existing ToolJet application deployment with [environment variables](/docs/setup/env-vars#enable-tooljet-database--optional-) required for PostgREST.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.15.0/setup/docker.md b/docs/versioned_docs/version-2.15.0/setup/docker.md
index 0308312d21..76bd557503 100644
--- a/docs/versioned_docs/version-2.15.0/setup/docker.md
+++ b/docs/versioned_docs/version-2.15.0/setup/docker.md
@@ -126,11 +126,29 @@ Confused about which setup to select? Feel free to ask the community via Slack:
`sudo docker-compose up -d`
iv. Setup docker to run without root privileges by following the instructions written here https://docs.docker.com/engine/install/linux-postinstall/
- :::
+:::
-
-
-
-
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
+
+
+
+
+
+
diff --git a/docs/versioned_docs/version-2.15.0/setup/ec2.md b/docs/versioned_docs/version-2.15.0/setup/ec2.md
index 662b4f2d56..1c10b0e918 100644
--- a/docs/versioned_docs/version-2.15.0/setup/ec2.md
+++ b/docs/versioned_docs/version-2.15.0/setup/ec2.md
@@ -11,6 +11,13 @@ You should setup a PostgreSQL database manually to be used by the ToolJet server
*If you have any questions feel free to join our [Slack Community](https://tooljet.com/slack) or send us an email at hello@tooljet.com.*
+You can effortlessly deploy Amazon Elastic Compute Cloud Service (EC2) by utilizing a **CloudFormation template**. This template will deploy all the services required to run ToolJet on AWS EC2 instances.
+
+To deploy all the services at once, simply employ the following template:
+```
+curl -LO https://tooljet-deployments.s3.us-west-1.amazonaws.com/cloudformation/EC2-cloudfomration.yml
+```
+
Follow the steps below to deploy ToolJet on AWS EC2 instances.
1. Setup a PostgreSQL database and make sure that the database is accessible from the EC2 instance.
@@ -77,4 +84,26 @@ Follow the steps below to deploy ToolJet on AWS EC2 instances.
ToolJet AMI comes inbuilt with PostgREST. If you intend to use this feature, you'd only have to setup the environment variables in `~/app/.env` file and run `./setup_app` script.
-You can learn more about this feature [here](/docs/tooljet-database).
\ No newline at end of file
+You can learn more about this feature [here](/docs/tooljet-database).
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
+
+
+
+
+
+
diff --git a/docs/versioned_docs/version-2.15.0/setup/ecs.md b/docs/versioned_docs/version-2.15.0/setup/ecs.md
index c3eb758aa0..b4f3073222 100644
--- a/docs/versioned_docs/version-2.15.0/setup/ecs.md
+++ b/docs/versioned_docs/version-2.15.0/setup/ecs.md
@@ -228,3 +228,18 @@ Follow the steps below to deploy PostgREST on a ECS cluster.
Update ToolJet deployment with the appropriate env variables [here](https://docs.tooljet.com/docs/setup/env-vars/#enable-tooljet-database--optional-) and apply the changes.
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.15.0/setup/google-cloud-run.md b/docs/versioned_docs/version-2.15.0/setup/google-cloud-run.md
index fc7dd35617..3d5e7e0344 100644
--- a/docs/versioned_docs/version-2.15.0/setup/google-cloud-run.md
+++ b/docs/versioned_docs/version-2.15.0/setup/google-cloud-run.md
@@ -151,3 +151,20 @@ Once the Service is created and live, to make the Cloud Service URL public. Ple
+
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.15.0/setup/helm.md b/docs/versioned_docs/version-2.15.0/setup/helm.md
index cca63346c1..ce2632a837 100644
--- a/docs/versioned_docs/version-2.15.0/setup/helm.md
+++ b/docs/versioned_docs/version-2.15.0/setup/helm.md
@@ -33,4 +33,20 @@ For more information about the ToolJet database, you can visit [here](/docs/tool
If you plan to use this feature, you need to set up and deploy the PostgREST server, which facilitates querying the ToolJet Database.
-To enable the ToolJet database, please set the environment variable `ENABLE_TOOLJET_DB` to true in the `values.yaml` file.
\ No newline at end of file
+To enable the ToolJet database, please set the environment variable `ENABLE_TOOLJET_DB` to true in the `values.yaml` file.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.15.0/setup/kubernetes-aks.md b/docs/versioned_docs/version-2.15.0/setup/kubernetes-aks.md
index 7c87caa19d..0dc295d422 100644
--- a/docs/versioned_docs/version-2.15.0/setup/kubernetes-aks.md
+++ b/docs/versioned_docs/version-2.15.0/setup/kubernetes-aks.md
@@ -53,3 +53,19 @@ If you intend to use this feature, you'd have to set up and deploy PostgREST ser
```
2. Update ToolJet deployment with the appropriate env variables [here](https://raw.githubusercontent.com/ToolJet/ToolJet/main/deploy/kubernetes/AKS/deployment.yaml) and apply the changes.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.15.0/setup/kubernetes-gke.md b/docs/versioned_docs/version-2.15.0/setup/kubernetes-gke.md
index af86339fec..2fd124631d 100644
--- a/docs/versioned_docs/version-2.15.0/setup/kubernetes-gke.md
+++ b/docs/versioned_docs/version-2.15.0/setup/kubernetes-gke.md
@@ -79,3 +79,19 @@ If you intend to use this feature, you'd have to set up and deploy PostgREST ser
```
2. Update ToolJet deployment with the appropriate env variables [here](https://raw.githubusercontent.com/ToolJet/ToolJet/main/deploy/kubernetes/GKE/deployment.yaml) and apply the changes.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.15.0/setup/kubernetes.md b/docs/versioned_docs/version-2.15.0/setup/kubernetes.md
index 1f8991660b..6a8ad54279 100644
--- a/docs/versioned_docs/version-2.15.0/setup/kubernetes.md
+++ b/docs/versioned_docs/version-2.15.0/setup/kubernetes.md
@@ -62,3 +62,19 @@ If you intend to use this feature, you'd have to set up and deploy PostgREST ser
```
2. Update ToolJet deployment with the appropriate env variables [here](https://raw.githubusercontent.com/ToolJet/ToolJet/main/deploy/kubernetes/deployment.yaml) and apply the changes.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.15.0/setup/openshift.md b/docs/versioned_docs/version-2.15.0/setup/openshift.md
index 1cdb3dd674..28a318e14f 100644
--- a/docs/versioned_docs/version-2.15.0/setup/openshift.md
+++ b/docs/versioned_docs/version-2.15.0/setup/openshift.md
@@ -67,4 +67,20 @@ If you intend to use this feature, you'd have to set up and deploy PostgREST ser
```
https://raw.githubusercontent.com/ToolJet/ToolJet/main/deploy/openshift/postgrest.yaml
-```
\ No newline at end of file
+```
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.15.0/setup/tooljet-subpath.md b/docs/versioned_docs/version-2.15.0/setup/tooljet-subpath.md
index e05625d5d6..51c8a438ad 100644
--- a/docs/versioned_docs/version-2.15.0/setup/tooljet-subpath.md
+++ b/docs/versioned_docs/version-2.15.0/setup/tooljet-subpath.md
@@ -20,4 +20,20 @@ You'll need to setup the following environment variables if ToolJet installation
See all **[Environment Variables](/docs/setup/env-vars)** here.
:::
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
+
diff --git a/docs/versioned_docs/version-2.15.0/setup/try-tooljet.md b/docs/versioned_docs/version-2.15.0/setup/try-tooljet.md
index eb60b5323a..59c9108cf2 100644
--- a/docs/versioned_docs/version-2.15.0/setup/try-tooljet.md
+++ b/docs/versioned_docs/version-2.15.0/setup/try-tooljet.md
@@ -10,16 +10,16 @@ title: Try ToolJet
You can run the command below to have ToolJet up and running right away.
```bash
-docker run \
+docker run -d \
--name tooljet \
--restart unless-stopped \
-p 80:80 \
+ --platform linux/amd64 \
-v tooljet_data:/var/lib/postgresql/13/main \
tooljet/try:latest
```
*If you have any questions feel free to join our [Slack Community](https://tooljet.com/slack) or send us an email at hello@tooljet.com.*
-
#### Setup information
- Runs the ToolJet server on the port 80 on your machine.
diff --git a/docs/versioned_docs/version-2.16.0/contributing-guide/setup/codespaces.md b/docs/versioned_docs/version-2.16.0/contributing-guide/setup/codespaces.md
new file mode 100644
index 0000000000..1204d71f63
--- /dev/null
+++ b/docs/versioned_docs/version-2.16.0/contributing-guide/setup/codespaces.md
@@ -0,0 +1,117 @@
+---
+id: codespaces
+title: GitHub Codespaces
+---
+
+Follow the steps below to set up ToolJet on GitHub Codespaces. We recommend reading our guide on [architecture](https://docs.tooljet.com/docs/contributing-guide/setup/architecture) of ToolJet before proceeding.
+
+Open the terminal and run the commands below.
+
+## Setting up
+
+### 1. Set up the environment
+
+1. Install Node.js ( version: v18.3.0 ) and npm (version: v8.11.0)
+
+```
+nvm install 18.3.0
+nvm use 18.3.0
+npm install -g npm@8.11.0
+```
+
+2. Install Postgres
+
+```
+sudo sh -c 'echo "deb [http://apt.postgresql.org/pub/repos/apt](http://apt.postgresql.org/pub/repos/apt) $(lsb_release -cs)-pgdg main" > /etc/apt/sources.list.d/pgdg.list'
+
+wget --quiet -O - [https://www.postgresql.org/media/keys/ACCC4CF8.asc](https://www.postgresql.org/media/keys/ACCC4CF8.asc) | sudo apt-key add -
+
+sudo apt-get update
+
+sudo apt-get install postgresql-13 postgresql-contrib-13
+```
+
+To start the postgresql service run the below command:
+
+```
+sudo service postgresql start
+```
+
+If you wish to change the password of the installed postresql service run the below commands:
+
+```
+sudo su
+
+sudo -u postgres psql
+
+\password postgres
+
+\q
+```
+
+### 2. Set up environment variables
+
+Create a `.env` file by running the command `touch .env`. More information on the variables that can be set is given in the [environment variables reference](https://docs.tooljet.com/docs/setup/env-vars)
+
+**For basic set-up you add the below env variables:**
+
+```
+TOOLJET_HOST=http://localhost:3000
+
+LOCKBOX_MASTER_KEY=
+
+SECRET_KEY_BASE=
+
+PG_USER=postgres
+
+PG_HOST=localhost
+
+PG_PASS=postgres
+
+PG_DB=tooljet_prod
+
+SUB_PATH=/apps/tooljet/
+
+NODE_ENV=production
+
+SERVE_CLIENT=true
+```
+
+> `SECRET_KEY_BASE` requires a 64 byte key. (If you have `openssl` installed, run `openssl rand -hex 64` to create a 64 byte secure random key)
+>
+> `LOCKBOX_MASTER_KEY` requires a 32 byte key. (Run `openssl rand -hex 32` to create a 32 byte secure random key)
+
+### 3. Install and build dependencies
+
+Make sure node version is set to 18.3.0 before running the below command:
+
+```
+npm install
+npm install --prefix server
+npm install --prefix frontend
+npm run build:plugins
+```
+
+
+### 4. Set up database
+
+```
+npm run --prefix server db:create
+npm run --prefix server db:mirgate
+```
+
+If at any point you need to reset the database, use this command `npm run --prefix server db:reset`
+
+### 5. Build client
+
+```
+cd ./frontend && NODE=production npm run build
+```
+
+### 6. Run server
+
+```
+cd ./server && npm run start:prod
+```
+
+The client will start on the **port 3000**, you can access the client by visiting the url created by codespace - `https:///apps/tooljet`
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.16.0/how-to/bulk-update-multiple-rows-in-table.md b/docs/versioned_docs/version-2.16.0/how-to/bulk-update-multiple-rows-in-table.md
index b29e582b46..f518b117ac 100644
--- a/docs/versioned_docs/version-2.16.0/how-to/bulk-update-multiple-rows-in-table.md
+++ b/docs/versioned_docs/version-2.16.0/how-to/bulk-update-multiple-rows-in-table.md
@@ -5,56 +5,62 @@ title: Bulk update multiple rows in table
# Bulk update multiple rows in table
-Currently, the datasources in ToolJet have operation for **bulk update(GUI mode)** but that only works for changes made in the single row. We will soon be adding a new operation for bulk updating the multiple rows but for now we can bulk update multiple rows by creating a Custom JS query.
+Currently, the data sources in ToolJet have operation for **bulk update(GUI mode)** but that only works for changes made in the single row. We will soon be adding a new operation for bulk updating the multiple rows but for now we can bulk update multiple rows by creating a Custom JS query.
-In this guide, We have assumed that you have successfully connected the data source. For this guide, we will be using the PostgreSQL data source as an example database, currently, this workaround can be used only for PostgreSQL and MySQL.
+In this guide, We have assumed that you have successfully connected the data source. For this guide, we will be using the PostgreSQL data source as an example database. Currently, this workaround can be used only for PostgreSQL and MySQL.
## 1. Create a query to get the data from the database
-Let's create the query that will be getting the data from the database:
+- Create a postgresql query in **SQL mode** and enter
+
+```sql
+SELECT * FROM tooljet // replace tooljet with your table name
+```
+
+- Hit **Run** to fetch the data from the database
-
+
## 2. Display the data on the table
-- Drag a **Table** widget on the canvas and click on its handle to open the properties on the left sidebar
-- Edit the **Table data** field value and enter **`{{queries.postgresql1.data}}`**
+- Go to the **Components** library on the right and drag a **Table** component onto the canvas
+- Click on the handle of the **Table** component to open its properties on the right sidebar
+- Populate the table with the data from the query by entering **`{{queries..data}}`** in the **Data** field
-
+
## 3. Make the columns editable
-- Go to the **Columns**, Add or edit columns section and enter the **Column Name** that you want to display on the table and the **Key** name. Key is the name of the column in your database.
-- Enable the toggle for **Make editable** for the columns that you want to be editable.
+- Under the **Columns** accordion, click on the column name that you want to make editable
+- On clicking the column name, a new section will open. Enable the toggle for **Make editable** to make the column editable
-
+
-## 4. Enable bulk update options for table widget
+## 4. Enable Multiple Row Selection
-- Go to the **Options** section and enable the **Show update buttons**. Enabling this will add two buttons - **Save Changes** and **Discard Changes** at the bottom of the table, only when any cell in the table is edited.
-- You can also enable highlight selected row.(**Optional**)
+- Under the **Row Selection** accordion, enable the **Allow Selection**, **Highlight Selected Row**, and **Bulk Selection** option
-
+
## 5. Create a Custom JS query
-We will create a new Custom JS query(**runjs1**) that will generate SQL query for updating multiple rows.
+- Create a new Run Javascript query and use the code below to generate the SQL query for updating multiple rows.
```js
const uniqueIdentifier = "id"
@@ -81,36 +87,47 @@ Update **table1** with the name of the table you are using.
:::
-
+
## 6. Create an Update query
-Let's create a new PostgreSQL query and name it `update`. In **SQL mode**, enter `{{queries.runjs1.data.join(' ')}}` and **Save** it.
+- Create a postgresql query in **SQL mode** and rename it as **update**:
+
+```sql
+{{queries.runjs1.data.join(' ')}}
+```
+
+- This query will run the SQL query generated by the runjs1 query.
-
+
-## 7. Creating a flow for queries
+## 7. Adding event handlers to execute queries in sequence
-- Click on the handle of the **Table** widget to open its properties
-- Go to the **Events**, and add a handler
-- Select **Bulk Update** in Events, **Run Query** in Actions, and then select the **runjs1** query in Query. Now whenever a user will edit the table and hit the **Save Changes** button runjs1 will run.
+- Edit the **Table** component and add the event handler for **Save Changes** event so that whenever a user will edit the table and hit the **Save Changes** button the runjs1 query will run.
+- Add **loading state** to table so that whenever the **users** or **update** query is running the table will show a loading state.
+
+```js
+{{queries.users.isLoading || queries.update.isLoading}} // add this in the loading state field of the table
+```
-
+
-- Now, go to the **Advanced** tab of **runjs1** and add a handler to run update query for **Query Success** Event. Now whenever the runjs1 query will be run - the update operation will be performed on the database.
+- Now, go to the **runjs1** query and add a **Event** to run update query for **Query Success** Event. This will run the update query whenever the runjs1 query will be run.
-
+
-
\ No newline at end of file
+
+
+- Finally, go to the **update** query and add a **Event** to run the users query for **Query Success** Event. This will refresh the table whenever the update query will be run.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.16.0/setup/azure-container.md b/docs/versioned_docs/version-2.16.0/setup/azure-container.md
index 60bdc0aaa5..fe19e718dc 100644
--- a/docs/versioned_docs/version-2.16.0/setup/azure-container.md
+++ b/docs/versioned_docs/version-2.16.0/setup/azure-container.md
@@ -68,3 +68,19 @@ Please note that you need to set up a PostgreSQL database manually to be used by
You can access ToolJet via the application URL provided in the overview tab.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
diff --git a/docs/versioned_docs/version-2.16.0/setup/client.md b/docs/versioned_docs/version-2.16.0/setup/client.md
index ebea627ad9..a29cfb1b60 100644
--- a/docs/versioned_docs/version-2.16.0/setup/client.md
+++ b/docs/versioned_docs/version-2.16.0/setup/client.md
@@ -96,3 +96,19 @@ Summarising the steps below:
```bash
cd tooljet-assets && gcloud app deploy
```
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
diff --git a/docs/versioned_docs/version-2.16.0/setup/digitalocean.md b/docs/versioned_docs/version-2.16.0/setup/digitalocean.md
index 0030942f83..03c485dcf5 100644
--- a/docs/versioned_docs/version-2.16.0/setup/digitalocean.md
+++ b/docs/versioned_docs/version-2.16.0/setup/digitalocean.md
@@ -107,3 +107,19 @@ Follow the steps below to deploy ToolJet Database on DigitalOcean:
4. Add your newly created PostgREST app to the trusted sources of your managed or separate database.
5. Update your existing ToolJet application deployment with [environment variables](/docs/setup/env-vars#enable-tooljet-database--optional-) required for PostgREST.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.16.0/setup/docker.md b/docs/versioned_docs/version-2.16.0/setup/docker.md
index 0308312d21..76bd557503 100644
--- a/docs/versioned_docs/version-2.16.0/setup/docker.md
+++ b/docs/versioned_docs/version-2.16.0/setup/docker.md
@@ -126,11 +126,29 @@ Confused about which setup to select? Feel free to ask the community via Slack:
`sudo docker-compose up -d`
iv. Setup docker to run without root privileges by following the instructions written here https://docs.docker.com/engine/install/linux-postinstall/
- :::
+:::
-
-
-
-
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
+
+
+
+
+
+
diff --git a/docs/versioned_docs/version-2.16.0/setup/ec2.md b/docs/versioned_docs/version-2.16.0/setup/ec2.md
index 662b4f2d56..1c10b0e918 100644
--- a/docs/versioned_docs/version-2.16.0/setup/ec2.md
+++ b/docs/versioned_docs/version-2.16.0/setup/ec2.md
@@ -11,6 +11,13 @@ You should setup a PostgreSQL database manually to be used by the ToolJet server
*If you have any questions feel free to join our [Slack Community](https://tooljet.com/slack) or send us an email at hello@tooljet.com.*
+You can effortlessly deploy Amazon Elastic Compute Cloud Service (EC2) by utilizing a **CloudFormation template**. This template will deploy all the services required to run ToolJet on AWS EC2 instances.
+
+To deploy all the services at once, simply employ the following template:
+```
+curl -LO https://tooljet-deployments.s3.us-west-1.amazonaws.com/cloudformation/EC2-cloudfomration.yml
+```
+
Follow the steps below to deploy ToolJet on AWS EC2 instances.
1. Setup a PostgreSQL database and make sure that the database is accessible from the EC2 instance.
@@ -77,4 +84,26 @@ Follow the steps below to deploy ToolJet on AWS EC2 instances.
ToolJet AMI comes inbuilt with PostgREST. If you intend to use this feature, you'd only have to setup the environment variables in `~/app/.env` file and run `./setup_app` script.
-You can learn more about this feature [here](/docs/tooljet-database).
\ No newline at end of file
+You can learn more about this feature [here](/docs/tooljet-database).
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
+
+
+
+
+
+
diff --git a/docs/versioned_docs/version-2.16.0/setup/ecs.md b/docs/versioned_docs/version-2.16.0/setup/ecs.md
index c3eb758aa0..b4f3073222 100644
--- a/docs/versioned_docs/version-2.16.0/setup/ecs.md
+++ b/docs/versioned_docs/version-2.16.0/setup/ecs.md
@@ -228,3 +228,18 @@ Follow the steps below to deploy PostgREST on a ECS cluster.
Update ToolJet deployment with the appropriate env variables [here](https://docs.tooljet.com/docs/setup/env-vars/#enable-tooljet-database--optional-) and apply the changes.
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.16.0/setup/google-cloud-run.md b/docs/versioned_docs/version-2.16.0/setup/google-cloud-run.md
index fc7dd35617..3d5e7e0344 100644
--- a/docs/versioned_docs/version-2.16.0/setup/google-cloud-run.md
+++ b/docs/versioned_docs/version-2.16.0/setup/google-cloud-run.md
@@ -151,3 +151,20 @@ Once the Service is created and live, to make the Cloud Service URL public. Ple
+
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.16.0/setup/helm.md b/docs/versioned_docs/version-2.16.0/setup/helm.md
index cca63346c1..ce2632a837 100644
--- a/docs/versioned_docs/version-2.16.0/setup/helm.md
+++ b/docs/versioned_docs/version-2.16.0/setup/helm.md
@@ -33,4 +33,20 @@ For more information about the ToolJet database, you can visit [here](/docs/tool
If you plan to use this feature, you need to set up and deploy the PostgREST server, which facilitates querying the ToolJet Database.
-To enable the ToolJet database, please set the environment variable `ENABLE_TOOLJET_DB` to true in the `values.yaml` file.
\ No newline at end of file
+To enable the ToolJet database, please set the environment variable `ENABLE_TOOLJET_DB` to true in the `values.yaml` file.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.16.0/setup/kubernetes-aks.md b/docs/versioned_docs/version-2.16.0/setup/kubernetes-aks.md
index 7c87caa19d..0dc295d422 100644
--- a/docs/versioned_docs/version-2.16.0/setup/kubernetes-aks.md
+++ b/docs/versioned_docs/version-2.16.0/setup/kubernetes-aks.md
@@ -53,3 +53,19 @@ If you intend to use this feature, you'd have to set up and deploy PostgREST ser
```
2. Update ToolJet deployment with the appropriate env variables [here](https://raw.githubusercontent.com/ToolJet/ToolJet/main/deploy/kubernetes/AKS/deployment.yaml) and apply the changes.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.16.0/setup/kubernetes-gke.md b/docs/versioned_docs/version-2.16.0/setup/kubernetes-gke.md
index af86339fec..2fd124631d 100644
--- a/docs/versioned_docs/version-2.16.0/setup/kubernetes-gke.md
+++ b/docs/versioned_docs/version-2.16.0/setup/kubernetes-gke.md
@@ -79,3 +79,19 @@ If you intend to use this feature, you'd have to set up and deploy PostgREST ser
```
2. Update ToolJet deployment with the appropriate env variables [here](https://raw.githubusercontent.com/ToolJet/ToolJet/main/deploy/kubernetes/GKE/deployment.yaml) and apply the changes.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.16.0/setup/kubernetes.md b/docs/versioned_docs/version-2.16.0/setup/kubernetes.md
index 1f8991660b..6a8ad54279 100644
--- a/docs/versioned_docs/version-2.16.0/setup/kubernetes.md
+++ b/docs/versioned_docs/version-2.16.0/setup/kubernetes.md
@@ -62,3 +62,19 @@ If you intend to use this feature, you'd have to set up and deploy PostgREST ser
```
2. Update ToolJet deployment with the appropriate env variables [here](https://raw.githubusercontent.com/ToolJet/ToolJet/main/deploy/kubernetes/deployment.yaml) and apply the changes.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.16.0/setup/openshift.md b/docs/versioned_docs/version-2.16.0/setup/openshift.md
index 1cdb3dd674..28a318e14f 100644
--- a/docs/versioned_docs/version-2.16.0/setup/openshift.md
+++ b/docs/versioned_docs/version-2.16.0/setup/openshift.md
@@ -67,4 +67,20 @@ If you intend to use this feature, you'd have to set up and deploy PostgREST ser
```
https://raw.githubusercontent.com/ToolJet/ToolJet/main/deploy/openshift/postgrest.yaml
-```
\ No newline at end of file
+```
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.16.0/setup/tooljet-subpath.md b/docs/versioned_docs/version-2.16.0/setup/tooljet-subpath.md
index e05625d5d6..51c8a438ad 100644
--- a/docs/versioned_docs/version-2.16.0/setup/tooljet-subpath.md
+++ b/docs/versioned_docs/version-2.16.0/setup/tooljet-subpath.md
@@ -20,4 +20,20 @@ You'll need to setup the following environment variables if ToolJet installation
See all **[Environment Variables](/docs/setup/env-vars)** here.
:::
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
+
diff --git a/docs/versioned_docs/version-2.16.0/setup/try-tooljet.md b/docs/versioned_docs/version-2.16.0/setup/try-tooljet.md
index eb60b5323a..59c9108cf2 100644
--- a/docs/versioned_docs/version-2.16.0/setup/try-tooljet.md
+++ b/docs/versioned_docs/version-2.16.0/setup/try-tooljet.md
@@ -10,16 +10,16 @@ title: Try ToolJet
You can run the command below to have ToolJet up and running right away.
```bash
-docker run \
+docker run -d \
--name tooljet \
--restart unless-stopped \
-p 80:80 \
+ --platform linux/amd64 \
-v tooljet_data:/var/lib/postgresql/13/main \
tooljet/try:latest
```
*If you have any questions feel free to join our [Slack Community](https://tooljet.com/slack) or send us an email at hello@tooljet.com.*
-
#### Setup information
- Runs the ToolJet server on the port 80 on your machine.
diff --git a/docs/versioned_docs/version-2.17.0/contributing-guide/setup/codespaces.md b/docs/versioned_docs/version-2.17.0/contributing-guide/setup/codespaces.md
new file mode 100644
index 0000000000..1204d71f63
--- /dev/null
+++ b/docs/versioned_docs/version-2.17.0/contributing-guide/setup/codespaces.md
@@ -0,0 +1,117 @@
+---
+id: codespaces
+title: GitHub Codespaces
+---
+
+Follow the steps below to set up ToolJet on GitHub Codespaces. We recommend reading our guide on [architecture](https://docs.tooljet.com/docs/contributing-guide/setup/architecture) of ToolJet before proceeding.
+
+Open the terminal and run the commands below.
+
+## Setting up
+
+### 1. Set up the environment
+
+1. Install Node.js ( version: v18.3.0 ) and npm (version: v8.11.0)
+
+```
+nvm install 18.3.0
+nvm use 18.3.0
+npm install -g npm@8.11.0
+```
+
+2. Install Postgres
+
+```
+sudo sh -c 'echo "deb [http://apt.postgresql.org/pub/repos/apt](http://apt.postgresql.org/pub/repos/apt) $(lsb_release -cs)-pgdg main" > /etc/apt/sources.list.d/pgdg.list'
+
+wget --quiet -O - [https://www.postgresql.org/media/keys/ACCC4CF8.asc](https://www.postgresql.org/media/keys/ACCC4CF8.asc) | sudo apt-key add -
+
+sudo apt-get update
+
+sudo apt-get install postgresql-13 postgresql-contrib-13
+```
+
+To start the postgresql service run the below command:
+
+```
+sudo service postgresql start
+```
+
+If you wish to change the password of the installed postresql service run the below commands:
+
+```
+sudo su
+
+sudo -u postgres psql
+
+\password postgres
+
+\q
+```
+
+### 2. Set up environment variables
+
+Create a `.env` file by running the command `touch .env`. More information on the variables that can be set is given in the [environment variables reference](https://docs.tooljet.com/docs/setup/env-vars)
+
+**For basic set-up you add the below env variables:**
+
+```
+TOOLJET_HOST=http://localhost:3000
+
+LOCKBOX_MASTER_KEY=
+
+SECRET_KEY_BASE=
+
+PG_USER=postgres
+
+PG_HOST=localhost
+
+PG_PASS=postgres
+
+PG_DB=tooljet_prod
+
+SUB_PATH=/apps/tooljet/
+
+NODE_ENV=production
+
+SERVE_CLIENT=true
+```
+
+> `SECRET_KEY_BASE` requires a 64 byte key. (If you have `openssl` installed, run `openssl rand -hex 64` to create a 64 byte secure random key)
+>
+> `LOCKBOX_MASTER_KEY` requires a 32 byte key. (Run `openssl rand -hex 32` to create a 32 byte secure random key)
+
+### 3. Install and build dependencies
+
+Make sure node version is set to 18.3.0 before running the below command:
+
+```
+npm install
+npm install --prefix server
+npm install --prefix frontend
+npm run build:plugins
+```
+
+
+### 4. Set up database
+
+```
+npm run --prefix server db:create
+npm run --prefix server db:mirgate
+```
+
+If at any point you need to reset the database, use this command `npm run --prefix server db:reset`
+
+### 5. Build client
+
+```
+cd ./frontend && NODE=production npm run build
+```
+
+### 6. Run server
+
+```
+cd ./server && npm run start:prod
+```
+
+The client will start on the **port 3000**, you can access the client by visiting the url created by codespace - `https:///apps/tooljet`
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.17.0/how-to/bulk-update-multiple-rows-in-table.md b/docs/versioned_docs/version-2.17.0/how-to/bulk-update-multiple-rows-in-table.md
index b29e582b46..f518b117ac 100644
--- a/docs/versioned_docs/version-2.17.0/how-to/bulk-update-multiple-rows-in-table.md
+++ b/docs/versioned_docs/version-2.17.0/how-to/bulk-update-multiple-rows-in-table.md
@@ -5,56 +5,62 @@ title: Bulk update multiple rows in table
# Bulk update multiple rows in table
-Currently, the datasources in ToolJet have operation for **bulk update(GUI mode)** but that only works for changes made in the single row. We will soon be adding a new operation for bulk updating the multiple rows but for now we can bulk update multiple rows by creating a Custom JS query.
+Currently, the data sources in ToolJet have operation for **bulk update(GUI mode)** but that only works for changes made in the single row. We will soon be adding a new operation for bulk updating the multiple rows but for now we can bulk update multiple rows by creating a Custom JS query.
-In this guide, We have assumed that you have successfully connected the data source. For this guide, we will be using the PostgreSQL data source as an example database, currently, this workaround can be used only for PostgreSQL and MySQL.
+In this guide, We have assumed that you have successfully connected the data source. For this guide, we will be using the PostgreSQL data source as an example database. Currently, this workaround can be used only for PostgreSQL and MySQL.
## 1. Create a query to get the data from the database
-Let's create the query that will be getting the data from the database:
+- Create a postgresql query in **SQL mode** and enter
+
+```sql
+SELECT * FROM tooljet // replace tooljet with your table name
+```
+
+- Hit **Run** to fetch the data from the database
-
+
## 2. Display the data on the table
-- Drag a **Table** widget on the canvas and click on its handle to open the properties on the left sidebar
-- Edit the **Table data** field value and enter **`{{queries.postgresql1.data}}`**
+- Go to the **Components** library on the right and drag a **Table** component onto the canvas
+- Click on the handle of the **Table** component to open its properties on the right sidebar
+- Populate the table with the data from the query by entering **`{{queries..data}}`** in the **Data** field
-
+
## 3. Make the columns editable
-- Go to the **Columns**, Add or edit columns section and enter the **Column Name** that you want to display on the table and the **Key** name. Key is the name of the column in your database.
-- Enable the toggle for **Make editable** for the columns that you want to be editable.
+- Under the **Columns** accordion, click on the column name that you want to make editable
+- On clicking the column name, a new section will open. Enable the toggle for **Make editable** to make the column editable
-
+
-## 4. Enable bulk update options for table widget
+## 4. Enable Multiple Row Selection
-- Go to the **Options** section and enable the **Show update buttons**. Enabling this will add two buttons - **Save Changes** and **Discard Changes** at the bottom of the table, only when any cell in the table is edited.
-- You can also enable highlight selected row.(**Optional**)
+- Under the **Row Selection** accordion, enable the **Allow Selection**, **Highlight Selected Row**, and **Bulk Selection** option
-
+
## 5. Create a Custom JS query
-We will create a new Custom JS query(**runjs1**) that will generate SQL query for updating multiple rows.
+- Create a new Run Javascript query and use the code below to generate the SQL query for updating multiple rows.
```js
const uniqueIdentifier = "id"
@@ -81,36 +87,47 @@ Update **table1** with the name of the table you are using.
:::
-
+
## 6. Create an Update query
-Let's create a new PostgreSQL query and name it `update`. In **SQL mode**, enter `{{queries.runjs1.data.join(' ')}}` and **Save** it.
+- Create a postgresql query in **SQL mode** and rename it as **update**:
+
+```sql
+{{queries.runjs1.data.join(' ')}}
+```
+
+- This query will run the SQL query generated by the runjs1 query.
-
+
-## 7. Creating a flow for queries
+## 7. Adding event handlers to execute queries in sequence
-- Click on the handle of the **Table** widget to open its properties
-- Go to the **Events**, and add a handler
-- Select **Bulk Update** in Events, **Run Query** in Actions, and then select the **runjs1** query in Query. Now whenever a user will edit the table and hit the **Save Changes** button runjs1 will run.
+- Edit the **Table** component and add the event handler for **Save Changes** event so that whenever a user will edit the table and hit the **Save Changes** button the runjs1 query will run.
+- Add **loading state** to table so that whenever the **users** or **update** query is running the table will show a loading state.
+
+```js
+{{queries.users.isLoading || queries.update.isLoading}} // add this in the loading state field of the table
+```
-
+
-- Now, go to the **Advanced** tab of **runjs1** and add a handler to run update query for **Query Success** Event. Now whenever the runjs1 query will be run - the update operation will be performed on the database.
+- Now, go to the **runjs1** query and add a **Event** to run update query for **Query Success** Event. This will run the update query whenever the runjs1 query will be run.
-
+
-
\ No newline at end of file
+
+
+- Finally, go to the **update** query and add a **Event** to run the users query for **Query Success** Event. This will refresh the table whenever the update query will be run.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.17.0/setup/azure-container.md b/docs/versioned_docs/version-2.17.0/setup/azure-container.md
index 60bdc0aaa5..fe19e718dc 100644
--- a/docs/versioned_docs/version-2.17.0/setup/azure-container.md
+++ b/docs/versioned_docs/version-2.17.0/setup/azure-container.md
@@ -68,3 +68,19 @@ Please note that you need to set up a PostgreSQL database manually to be used by
You can access ToolJet via the application URL provided in the overview tab.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
diff --git a/docs/versioned_docs/version-2.17.0/setup/client.md b/docs/versioned_docs/version-2.17.0/setup/client.md
index ebea627ad9..a29cfb1b60 100644
--- a/docs/versioned_docs/version-2.17.0/setup/client.md
+++ b/docs/versioned_docs/version-2.17.0/setup/client.md
@@ -96,3 +96,19 @@ Summarising the steps below:
```bash
cd tooljet-assets && gcloud app deploy
```
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
diff --git a/docs/versioned_docs/version-2.17.0/setup/docker.md b/docs/versioned_docs/version-2.17.0/setup/docker.md
index ea1671ef1f..8a80874ba0 100644
--- a/docs/versioned_docs/version-2.17.0/setup/docker.md
+++ b/docs/versioned_docs/version-2.17.0/setup/docker.md
@@ -128,11 +128,29 @@ Confused about which setup to select? Feel free to ask the community via Slack:
`sudo docker-compose up -d`
iv. Setup docker to run without root privileges by following the instructions written here https://docs.docker.com/engine/install/linux-postinstall/
- :::
+:::
-
-
-
-
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
+
+
+
+
+
+
diff --git a/docs/versioned_docs/version-2.17.0/setup/ec2.md b/docs/versioned_docs/version-2.17.0/setup/ec2.md
index 662b4f2d56..1c10b0e918 100644
--- a/docs/versioned_docs/version-2.17.0/setup/ec2.md
+++ b/docs/versioned_docs/version-2.17.0/setup/ec2.md
@@ -11,6 +11,13 @@ You should setup a PostgreSQL database manually to be used by the ToolJet server
*If you have any questions feel free to join our [Slack Community](https://tooljet.com/slack) or send us an email at hello@tooljet.com.*
+You can effortlessly deploy Amazon Elastic Compute Cloud Service (EC2) by utilizing a **CloudFormation template**. This template will deploy all the services required to run ToolJet on AWS EC2 instances.
+
+To deploy all the services at once, simply employ the following template:
+```
+curl -LO https://tooljet-deployments.s3.us-west-1.amazonaws.com/cloudformation/EC2-cloudfomration.yml
+```
+
Follow the steps below to deploy ToolJet on AWS EC2 instances.
1. Setup a PostgreSQL database and make sure that the database is accessible from the EC2 instance.
@@ -77,4 +84,26 @@ Follow the steps below to deploy ToolJet on AWS EC2 instances.
ToolJet AMI comes inbuilt with PostgREST. If you intend to use this feature, you'd only have to setup the environment variables in `~/app/.env` file and run `./setup_app` script.
-You can learn more about this feature [here](/docs/tooljet-database).
\ No newline at end of file
+You can learn more about this feature [here](/docs/tooljet-database).
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
+
+
+
+
+
+
diff --git a/docs/versioned_docs/version-2.17.0/setup/ecs.md b/docs/versioned_docs/version-2.17.0/setup/ecs.md
index c3eb758aa0..b4f3073222 100644
--- a/docs/versioned_docs/version-2.17.0/setup/ecs.md
+++ b/docs/versioned_docs/version-2.17.0/setup/ecs.md
@@ -228,3 +228,18 @@ Follow the steps below to deploy PostgREST on a ECS cluster.
Update ToolJet deployment with the appropriate env variables [here](https://docs.tooljet.com/docs/setup/env-vars/#enable-tooljet-database--optional-) and apply the changes.
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.17.0/setup/google-cloud-run.md b/docs/versioned_docs/version-2.17.0/setup/google-cloud-run.md
index fc7dd35617..3d5e7e0344 100644
--- a/docs/versioned_docs/version-2.17.0/setup/google-cloud-run.md
+++ b/docs/versioned_docs/version-2.17.0/setup/google-cloud-run.md
@@ -151,3 +151,20 @@ Once the Service is created and live, to make the Cloud Service URL public. Ple
+
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.17.0/setup/helm.md b/docs/versioned_docs/version-2.17.0/setup/helm.md
index cca63346c1..ce2632a837 100644
--- a/docs/versioned_docs/version-2.17.0/setup/helm.md
+++ b/docs/versioned_docs/version-2.17.0/setup/helm.md
@@ -33,4 +33,20 @@ For more information about the ToolJet database, you can visit [here](/docs/tool
If you plan to use this feature, you need to set up and deploy the PostgREST server, which facilitates querying the ToolJet Database.
-To enable the ToolJet database, please set the environment variable `ENABLE_TOOLJET_DB` to true in the `values.yaml` file.
\ No newline at end of file
+To enable the ToolJet database, please set the environment variable `ENABLE_TOOLJET_DB` to true in the `values.yaml` file.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.17.0/setup/kubernetes-aks.md b/docs/versioned_docs/version-2.17.0/setup/kubernetes-aks.md
index 09160b07e7..0ca42d0872 100644
--- a/docs/versioned_docs/version-2.17.0/setup/kubernetes-aks.md
+++ b/docs/versioned_docs/version-2.17.0/setup/kubernetes-aks.md
@@ -53,3 +53,19 @@ If you intend to use this feature, you'd have to set up and deploy PostgREST ser
```
2. Update ToolJet deployment with the appropriate env variables [here](https://tooljet-deployments.s3.us-west-1.amazonaws.com/kubernetes/AKS/deployment.yaml) and apply the changes.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.17.0/setup/kubernetes-gke.md b/docs/versioned_docs/version-2.17.0/setup/kubernetes-gke.md
index 8071da0ae7..614ac6a485 100644
--- a/docs/versioned_docs/version-2.17.0/setup/kubernetes-gke.md
+++ b/docs/versioned_docs/version-2.17.0/setup/kubernetes-gke.md
@@ -79,3 +79,19 @@ If you intend to use this feature, you'd have to set up and deploy PostgREST ser
```
2. Update ToolJet deployment with the appropriate env variables [here](https://tooljet-deployments.s3.us-west-1.amazonaws.com/kubernetes/GKE/deployment.yaml) and apply the changes.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.17.0/setup/kubernetes.md b/docs/versioned_docs/version-2.17.0/setup/kubernetes.md
index b54428f606..a329ddb9e1 100644
--- a/docs/versioned_docs/version-2.17.0/setup/kubernetes.md
+++ b/docs/versioned_docs/version-2.17.0/setup/kubernetes.md
@@ -62,3 +62,19 @@ If you intend to use this feature, you'd have to set up and deploy PostgREST ser
```
2. Update ToolJet deployment with the appropriate env variables [here](https://tooljet-deployments.s3.us-west-1.amazonaws.com/kubernetes/deployment.yaml) and apply the changes.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.17.0/setup/openshift.md b/docs/versioned_docs/version-2.17.0/setup/openshift.md
index 73f6a7e531..10cebdf7db 100644
--- a/docs/versioned_docs/version-2.17.0/setup/openshift.md
+++ b/docs/versioned_docs/version-2.17.0/setup/openshift.md
@@ -68,3 +68,19 @@ If you intend to use this feature, you'd have to set up and deploy PostgREST ser
```
https://tooljet-deployments.s3.us-west-1.amazonaws.com/openshift/postgrest.yaml
```
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.17.0/setup/tooljet-subpath.md b/docs/versioned_docs/version-2.17.0/setup/tooljet-subpath.md
index e05625d5d6..51c8a438ad 100644
--- a/docs/versioned_docs/version-2.17.0/setup/tooljet-subpath.md
+++ b/docs/versioned_docs/version-2.17.0/setup/tooljet-subpath.md
@@ -20,4 +20,20 @@ You'll need to setup the following environment variables if ToolJet installation
See all **[Environment Variables](/docs/setup/env-vars)** here.
:::
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
+
diff --git a/docs/versioned_docs/version-2.17.0/setup/try-tooljet.md b/docs/versioned_docs/version-2.17.0/setup/try-tooljet.md
index eb60b5323a..59c9108cf2 100644
--- a/docs/versioned_docs/version-2.17.0/setup/try-tooljet.md
+++ b/docs/versioned_docs/version-2.17.0/setup/try-tooljet.md
@@ -10,16 +10,16 @@ title: Try ToolJet
You can run the command below to have ToolJet up and running right away.
```bash
-docker run \
+docker run -d \
--name tooljet \
--restart unless-stopped \
-p 80:80 \
+ --platform linux/amd64 \
-v tooljet_data:/var/lib/postgresql/13/main \
tooljet/try:latest
```
*If you have any questions feel free to join our [Slack Community](https://tooljet.com/slack) or send us an email at hello@tooljet.com.*
-
#### Setup information
- Runs the ToolJet server on the port 80 on your machine.
diff --git a/docs/versioned_docs/version-2.18.0/contributing-guide/setup/codespaces.md b/docs/versioned_docs/version-2.18.0/contributing-guide/setup/codespaces.md
new file mode 100644
index 0000000000..1204d71f63
--- /dev/null
+++ b/docs/versioned_docs/version-2.18.0/contributing-guide/setup/codespaces.md
@@ -0,0 +1,117 @@
+---
+id: codespaces
+title: GitHub Codespaces
+---
+
+Follow the steps below to set up ToolJet on GitHub Codespaces. We recommend reading our guide on [architecture](https://docs.tooljet.com/docs/contributing-guide/setup/architecture) of ToolJet before proceeding.
+
+Open the terminal and run the commands below.
+
+## Setting up
+
+### 1. Set up the environment
+
+1. Install Node.js ( version: v18.3.0 ) and npm (version: v8.11.0)
+
+```
+nvm install 18.3.0
+nvm use 18.3.0
+npm install -g npm@8.11.0
+```
+
+2. Install Postgres
+
+```
+sudo sh -c 'echo "deb [http://apt.postgresql.org/pub/repos/apt](http://apt.postgresql.org/pub/repos/apt) $(lsb_release -cs)-pgdg main" > /etc/apt/sources.list.d/pgdg.list'
+
+wget --quiet -O - [https://www.postgresql.org/media/keys/ACCC4CF8.asc](https://www.postgresql.org/media/keys/ACCC4CF8.asc) | sudo apt-key add -
+
+sudo apt-get update
+
+sudo apt-get install postgresql-13 postgresql-contrib-13
+```
+
+To start the postgresql service run the below command:
+
+```
+sudo service postgresql start
+```
+
+If you wish to change the password of the installed postresql service run the below commands:
+
+```
+sudo su
+
+sudo -u postgres psql
+
+\password postgres
+
+\q
+```
+
+### 2. Set up environment variables
+
+Create a `.env` file by running the command `touch .env`. More information on the variables that can be set is given in the [environment variables reference](https://docs.tooljet.com/docs/setup/env-vars)
+
+**For basic set-up you add the below env variables:**
+
+```
+TOOLJET_HOST=http://localhost:3000
+
+LOCKBOX_MASTER_KEY=
+
+SECRET_KEY_BASE=
+
+PG_USER=postgres
+
+PG_HOST=localhost
+
+PG_PASS=postgres
+
+PG_DB=tooljet_prod
+
+SUB_PATH=/apps/tooljet/
+
+NODE_ENV=production
+
+SERVE_CLIENT=true
+```
+
+> `SECRET_KEY_BASE` requires a 64 byte key. (If you have `openssl` installed, run `openssl rand -hex 64` to create a 64 byte secure random key)
+>
+> `LOCKBOX_MASTER_KEY` requires a 32 byte key. (Run `openssl rand -hex 32` to create a 32 byte secure random key)
+
+### 3. Install and build dependencies
+
+Make sure node version is set to 18.3.0 before running the below command:
+
+```
+npm install
+npm install --prefix server
+npm install --prefix frontend
+npm run build:plugins
+```
+
+
+### 4. Set up database
+
+```
+npm run --prefix server db:create
+npm run --prefix server db:mirgate
+```
+
+If at any point you need to reset the database, use this command `npm run --prefix server db:reset`
+
+### 5. Build client
+
+```
+cd ./frontend && NODE=production npm run build
+```
+
+### 6. Run server
+
+```
+cd ./server && npm run start:prod
+```
+
+The client will start on the **port 3000**, you can access the client by visiting the url created by codespace - `https:///apps/tooljet`
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.18.0/data-sources/clickhouse.md b/docs/versioned_docs/version-2.18.0/data-sources/clickhouse.md
index bb55b4a069..a9d60b9cd4 100644
--- a/docs/versioned_docs/version-2.18.0/data-sources/clickhouse.md
+++ b/docs/versioned_docs/version-2.18.0/data-sources/clickhouse.md
@@ -13,7 +13,7 @@ ToolJet uses this [NodeJS](https://github.com/TimonKK/clickhouse) client for Cli
## Connection
-To add a new ClickHouse datasource, Go to the **Datasource Manager** on the left sidebar of the app editor and click on `Add datasource` button. Select **ClickHouse** from the modal that pops up.
+To establish a connection with the Clickhouse data source, you can either click on the `+Add new data source` button located on the query panel or navigate to the **[Data Sources](/docs/data-sources/overview)** page through the ToolJet dashboard.
ToolJet requires the following to connect to your ClickHouse Database:
@@ -33,7 +33,7 @@ ToolJet requires the following to connect to your ClickHouse Database:
## Querying ClickHouse
-After setting up the ClickHouse datasource, you can click on the `+` button of the query manager and select the ClickHouse datasource that you added in the previous step to create a new query.
+After setting up the ClickHouse data source, you can click on the `+` button of the query manager and select the ClickHouse data source that you added in the previous step to create a new query.
:::info
For more details on clickhouse visit [Clickhouse docs](https://clickhouse.com/docs/en/quick-start).
diff --git a/docs/versioned_docs/version-2.18.0/how-to/bulk-update-multiple-rows-in-table.md b/docs/versioned_docs/version-2.18.0/how-to/bulk-update-multiple-rows-in-table.md
index b29e582b46..f518b117ac 100644
--- a/docs/versioned_docs/version-2.18.0/how-to/bulk-update-multiple-rows-in-table.md
+++ b/docs/versioned_docs/version-2.18.0/how-to/bulk-update-multiple-rows-in-table.md
@@ -5,56 +5,62 @@ title: Bulk update multiple rows in table
# Bulk update multiple rows in table
-Currently, the datasources in ToolJet have operation for **bulk update(GUI mode)** but that only works for changes made in the single row. We will soon be adding a new operation for bulk updating the multiple rows but for now we can bulk update multiple rows by creating a Custom JS query.
+Currently, the data sources in ToolJet have operation for **bulk update(GUI mode)** but that only works for changes made in the single row. We will soon be adding a new operation for bulk updating the multiple rows but for now we can bulk update multiple rows by creating a Custom JS query.
-In this guide, We have assumed that you have successfully connected the data source. For this guide, we will be using the PostgreSQL data source as an example database, currently, this workaround can be used only for PostgreSQL and MySQL.
+In this guide, We have assumed that you have successfully connected the data source. For this guide, we will be using the PostgreSQL data source as an example database. Currently, this workaround can be used only for PostgreSQL and MySQL.
## 1. Create a query to get the data from the database
-Let's create the query that will be getting the data from the database:
+- Create a postgresql query in **SQL mode** and enter
+
+```sql
+SELECT * FROM tooljet // replace tooljet with your table name
+```
+
+- Hit **Run** to fetch the data from the database
-
+
## 2. Display the data on the table
-- Drag a **Table** widget on the canvas and click on its handle to open the properties on the left sidebar
-- Edit the **Table data** field value and enter **`{{queries.postgresql1.data}}`**
+- Go to the **Components** library on the right and drag a **Table** component onto the canvas
+- Click on the handle of the **Table** component to open its properties on the right sidebar
+- Populate the table with the data from the query by entering **`{{queries..data}}`** in the **Data** field
-
+
## 3. Make the columns editable
-- Go to the **Columns**, Add or edit columns section and enter the **Column Name** that you want to display on the table and the **Key** name. Key is the name of the column in your database.
-- Enable the toggle for **Make editable** for the columns that you want to be editable.
+- Under the **Columns** accordion, click on the column name that you want to make editable
+- On clicking the column name, a new section will open. Enable the toggle for **Make editable** to make the column editable
-
+
-## 4. Enable bulk update options for table widget
+## 4. Enable Multiple Row Selection
-- Go to the **Options** section and enable the **Show update buttons**. Enabling this will add two buttons - **Save Changes** and **Discard Changes** at the bottom of the table, only when any cell in the table is edited.
-- You can also enable highlight selected row.(**Optional**)
+- Under the **Row Selection** accordion, enable the **Allow Selection**, **Highlight Selected Row**, and **Bulk Selection** option
-
+
## 5. Create a Custom JS query
-We will create a new Custom JS query(**runjs1**) that will generate SQL query for updating multiple rows.
+- Create a new Run Javascript query and use the code below to generate the SQL query for updating multiple rows.
```js
const uniqueIdentifier = "id"
@@ -81,36 +87,47 @@ Update **table1** with the name of the table you are using.
:::
-
+
## 6. Create an Update query
-Let's create a new PostgreSQL query and name it `update`. In **SQL mode**, enter `{{queries.runjs1.data.join(' ')}}` and **Save** it.
+- Create a postgresql query in **SQL mode** and rename it as **update**:
+
+```sql
+{{queries.runjs1.data.join(' ')}}
+```
+
+- This query will run the SQL query generated by the runjs1 query.
-
+
-## 7. Creating a flow for queries
+## 7. Adding event handlers to execute queries in sequence
-- Click on the handle of the **Table** widget to open its properties
-- Go to the **Events**, and add a handler
-- Select **Bulk Update** in Events, **Run Query** in Actions, and then select the **runjs1** query in Query. Now whenever a user will edit the table and hit the **Save Changes** button runjs1 will run.
+- Edit the **Table** component and add the event handler for **Save Changes** event so that whenever a user will edit the table and hit the **Save Changes** button the runjs1 query will run.
+- Add **loading state** to table so that whenever the **users** or **update** query is running the table will show a loading state.
+
+```js
+{{queries.users.isLoading || queries.update.isLoading}} // add this in the loading state field of the table
+```
-
+
-- Now, go to the **Advanced** tab of **runjs1** and add a handler to run update query for **Query Success** Event. Now whenever the runjs1 query will be run - the update operation will be performed on the database.
+- Now, go to the **runjs1** query and add a **Event** to run update query for **Query Success** Event. This will run the update query whenever the runjs1 query will be run.
-
+
-
\ No newline at end of file
+
+
+- Finally, go to the **update** query and add a **Event** to run the users query for **Query Success** Event. This will refresh the table whenever the update query will be run.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.18.0/setup/azure-container.md b/docs/versioned_docs/version-2.18.0/setup/azure-container.md
index 60bdc0aaa5..fe19e718dc 100644
--- a/docs/versioned_docs/version-2.18.0/setup/azure-container.md
+++ b/docs/versioned_docs/version-2.18.0/setup/azure-container.md
@@ -68,3 +68,19 @@ Please note that you need to set up a PostgreSQL database manually to be used by
You can access ToolJet via the application URL provided in the overview tab.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
diff --git a/docs/versioned_docs/version-2.18.0/setup/client.md b/docs/versioned_docs/version-2.18.0/setup/client.md
index ebea627ad9..a29cfb1b60 100644
--- a/docs/versioned_docs/version-2.18.0/setup/client.md
+++ b/docs/versioned_docs/version-2.18.0/setup/client.md
@@ -96,3 +96,19 @@ Summarising the steps below:
```bash
cd tooljet-assets && gcloud app deploy
```
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
diff --git a/docs/versioned_docs/version-2.18.0/setup/digitalocean.md b/docs/versioned_docs/version-2.18.0/setup/digitalocean.md
index 0030942f83..03c485dcf5 100644
--- a/docs/versioned_docs/version-2.18.0/setup/digitalocean.md
+++ b/docs/versioned_docs/version-2.18.0/setup/digitalocean.md
@@ -107,3 +107,19 @@ Follow the steps below to deploy ToolJet Database on DigitalOcean:
4. Add your newly created PostgREST app to the trusted sources of your managed or separate database.
5. Update your existing ToolJet application deployment with [environment variables](/docs/setup/env-vars#enable-tooljet-database--optional-) required for PostgREST.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.18.0/setup/docker.md b/docs/versioned_docs/version-2.18.0/setup/docker.md
index ea1671ef1f..8a80874ba0 100644
--- a/docs/versioned_docs/version-2.18.0/setup/docker.md
+++ b/docs/versioned_docs/version-2.18.0/setup/docker.md
@@ -128,11 +128,29 @@ Confused about which setup to select? Feel free to ask the community via Slack:
`sudo docker-compose up -d`
iv. Setup docker to run without root privileges by following the instructions written here https://docs.docker.com/engine/install/linux-postinstall/
- :::
+:::
-
-
-
-
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
+
+
+
+
+
+
diff --git a/docs/versioned_docs/version-2.18.0/setup/ec2.md b/docs/versioned_docs/version-2.18.0/setup/ec2.md
index 662b4f2d56..1c10b0e918 100644
--- a/docs/versioned_docs/version-2.18.0/setup/ec2.md
+++ b/docs/versioned_docs/version-2.18.0/setup/ec2.md
@@ -11,6 +11,13 @@ You should setup a PostgreSQL database manually to be used by the ToolJet server
*If you have any questions feel free to join our [Slack Community](https://tooljet.com/slack) or send us an email at hello@tooljet.com.*
+You can effortlessly deploy Amazon Elastic Compute Cloud Service (EC2) by utilizing a **CloudFormation template**. This template will deploy all the services required to run ToolJet on AWS EC2 instances.
+
+To deploy all the services at once, simply employ the following template:
+```
+curl -LO https://tooljet-deployments.s3.us-west-1.amazonaws.com/cloudformation/EC2-cloudfomration.yml
+```
+
Follow the steps below to deploy ToolJet on AWS EC2 instances.
1. Setup a PostgreSQL database and make sure that the database is accessible from the EC2 instance.
@@ -77,4 +84,26 @@ Follow the steps below to deploy ToolJet on AWS EC2 instances.
ToolJet AMI comes inbuilt with PostgREST. If you intend to use this feature, you'd only have to setup the environment variables in `~/app/.env` file and run `./setup_app` script.
-You can learn more about this feature [here](/docs/tooljet-database).
\ No newline at end of file
+You can learn more about this feature [here](/docs/tooljet-database).
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
+
+
+
+
+
+
diff --git a/docs/versioned_docs/version-2.18.0/setup/ecs.md b/docs/versioned_docs/version-2.18.0/setup/ecs.md
index c3eb758aa0..b4f3073222 100644
--- a/docs/versioned_docs/version-2.18.0/setup/ecs.md
+++ b/docs/versioned_docs/version-2.18.0/setup/ecs.md
@@ -228,3 +228,18 @@ Follow the steps below to deploy PostgREST on a ECS cluster.
Update ToolJet deployment with the appropriate env variables [here](https://docs.tooljet.com/docs/setup/env-vars/#enable-tooljet-database--optional-) and apply the changes.
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.18.0/setup/google-cloud-run.md b/docs/versioned_docs/version-2.18.0/setup/google-cloud-run.md
index 0431078dcc..3034395e2f 100644
--- a/docs/versioned_docs/version-2.18.0/setup/google-cloud-run.md
+++ b/docs/versioned_docs/version-2.18.0/setup/google-cloud-run.md
@@ -151,3 +151,20 @@ Once the Service is created and live, to make the Cloud Service URL public. Ple
+
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.18.0/setup/helm.md b/docs/versioned_docs/version-2.18.0/setup/helm.md
index cca63346c1..ce2632a837 100644
--- a/docs/versioned_docs/version-2.18.0/setup/helm.md
+++ b/docs/versioned_docs/version-2.18.0/setup/helm.md
@@ -33,4 +33,20 @@ For more information about the ToolJet database, you can visit [here](/docs/tool
If you plan to use this feature, you need to set up and deploy the PostgREST server, which facilitates querying the ToolJet Database.
-To enable the ToolJet database, please set the environment variable `ENABLE_TOOLJET_DB` to true in the `values.yaml` file.
\ No newline at end of file
+To enable the ToolJet database, please set the environment variable `ENABLE_TOOLJET_DB` to true in the `values.yaml` file.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.18.0/setup/kubernetes-aks.md b/docs/versioned_docs/version-2.18.0/setup/kubernetes-aks.md
index 04cc1515d2..35027ad21f 100644
--- a/docs/versioned_docs/version-2.18.0/setup/kubernetes-aks.md
+++ b/docs/versioned_docs/version-2.18.0/setup/kubernetes-aks.md
@@ -53,3 +53,19 @@ If you intend to use this feature, you'd have to set up and deploy PostgREST ser
```
2. Update ToolJet deployment with the appropriate env variables [here](https://tooljet-deployments.s3.us-west-1.amazonaws.com/kubernetes/AKS/deployment.yaml) and apply the changes.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.18.0/setup/kubernetes-gke.md b/docs/versioned_docs/version-2.18.0/setup/kubernetes-gke.md
index c87a6c36bd..27447189f0 100644
--- a/docs/versioned_docs/version-2.18.0/setup/kubernetes-gke.md
+++ b/docs/versioned_docs/version-2.18.0/setup/kubernetes-gke.md
@@ -79,3 +79,19 @@ If you intend to use this feature, you'd have to set up and deploy PostgREST ser
```
2. Update ToolJet deployment with the appropriate env variables [here](https://tooljet-deployments.s3.us-west-1.amazonaws.com/kubernetes/GKE/deployment.yaml) and apply the changes.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.18.0/setup/kubernetes.md b/docs/versioned_docs/version-2.18.0/setup/kubernetes.md
index 10441ef99d..4155bcae09 100644
--- a/docs/versioned_docs/version-2.18.0/setup/kubernetes.md
+++ b/docs/versioned_docs/version-2.18.0/setup/kubernetes.md
@@ -62,3 +62,19 @@ If you intend to use this feature, you'd have to set up and deploy PostgREST ser
```
2. Update ToolJet deployment with the appropriate env variables [here](https://tooljet-deployments.s3.us-west-1.amazonaws.com/kubernetes/deployment.yaml) and apply the changes.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.18.0/setup/openshift.md b/docs/versioned_docs/version-2.18.0/setup/openshift.md
index 73f6a7e531..10cebdf7db 100644
--- a/docs/versioned_docs/version-2.18.0/setup/openshift.md
+++ b/docs/versioned_docs/version-2.18.0/setup/openshift.md
@@ -68,3 +68,19 @@ If you intend to use this feature, you'd have to set up and deploy PostgREST ser
```
https://tooljet-deployments.s3.us-west-1.amazonaws.com/openshift/postgrest.yaml
```
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.18.0/setup/tooljet-subpath.md b/docs/versioned_docs/version-2.18.0/setup/tooljet-subpath.md
index e05625d5d6..51c8a438ad 100644
--- a/docs/versioned_docs/version-2.18.0/setup/tooljet-subpath.md
+++ b/docs/versioned_docs/version-2.18.0/setup/tooljet-subpath.md
@@ -20,4 +20,20 @@ You'll need to setup the following environment variables if ToolJet installation
See all **[Environment Variables](/docs/setup/env-vars)** here.
:::
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
+
diff --git a/docs/versioned_docs/version-2.18.0/setup/try-tooljet.md b/docs/versioned_docs/version-2.18.0/setup/try-tooljet.md
index eb60b5323a..59c9108cf2 100644
--- a/docs/versioned_docs/version-2.18.0/setup/try-tooljet.md
+++ b/docs/versioned_docs/version-2.18.0/setup/try-tooljet.md
@@ -10,16 +10,16 @@ title: Try ToolJet
You can run the command below to have ToolJet up and running right away.
```bash
-docker run \
+docker run -d \
--name tooljet \
--restart unless-stopped \
-p 80:80 \
+ --platform linux/amd64 \
-v tooljet_data:/var/lib/postgresql/13/main \
tooljet/try:latest
```
*If you have any questions feel free to join our [Slack Community](https://tooljet.com/slack) or send us an email at hello@tooljet.com.*
-
#### Setup information
- Runs the ToolJet server on the port 80 on your machine.
diff --git a/docs/versioned_docs/version-2.19.0/contributing-guide/setup/codespaces.md b/docs/versioned_docs/version-2.19.0/contributing-guide/setup/codespaces.md
new file mode 100644
index 0000000000..1204d71f63
--- /dev/null
+++ b/docs/versioned_docs/version-2.19.0/contributing-guide/setup/codespaces.md
@@ -0,0 +1,117 @@
+---
+id: codespaces
+title: GitHub Codespaces
+---
+
+Follow the steps below to set up ToolJet on GitHub Codespaces. We recommend reading our guide on [architecture](https://docs.tooljet.com/docs/contributing-guide/setup/architecture) of ToolJet before proceeding.
+
+Open the terminal and run the commands below.
+
+## Setting up
+
+### 1. Set up the environment
+
+1. Install Node.js ( version: v18.3.0 ) and npm (version: v8.11.0)
+
+```
+nvm install 18.3.0
+nvm use 18.3.0
+npm install -g npm@8.11.0
+```
+
+2. Install Postgres
+
+```
+sudo sh -c 'echo "deb [http://apt.postgresql.org/pub/repos/apt](http://apt.postgresql.org/pub/repos/apt) $(lsb_release -cs)-pgdg main" > /etc/apt/sources.list.d/pgdg.list'
+
+wget --quiet -O - [https://www.postgresql.org/media/keys/ACCC4CF8.asc](https://www.postgresql.org/media/keys/ACCC4CF8.asc) | sudo apt-key add -
+
+sudo apt-get update
+
+sudo apt-get install postgresql-13 postgresql-contrib-13
+```
+
+To start the postgresql service run the below command:
+
+```
+sudo service postgresql start
+```
+
+If you wish to change the password of the installed postresql service run the below commands:
+
+```
+sudo su
+
+sudo -u postgres psql
+
+\password postgres
+
+\q
+```
+
+### 2. Set up environment variables
+
+Create a `.env` file by running the command `touch .env`. More information on the variables that can be set is given in the [environment variables reference](https://docs.tooljet.com/docs/setup/env-vars)
+
+**For basic set-up you add the below env variables:**
+
+```
+TOOLJET_HOST=http://localhost:3000
+
+LOCKBOX_MASTER_KEY=
+
+SECRET_KEY_BASE=
+
+PG_USER=postgres
+
+PG_HOST=localhost
+
+PG_PASS=postgres
+
+PG_DB=tooljet_prod
+
+SUB_PATH=/apps/tooljet/
+
+NODE_ENV=production
+
+SERVE_CLIENT=true
+```
+
+> `SECRET_KEY_BASE` requires a 64 byte key. (If you have `openssl` installed, run `openssl rand -hex 64` to create a 64 byte secure random key)
+>
+> `LOCKBOX_MASTER_KEY` requires a 32 byte key. (Run `openssl rand -hex 32` to create a 32 byte secure random key)
+
+### 3. Install and build dependencies
+
+Make sure node version is set to 18.3.0 before running the below command:
+
+```
+npm install
+npm install --prefix server
+npm install --prefix frontend
+npm run build:plugins
+```
+
+
+### 4. Set up database
+
+```
+npm run --prefix server db:create
+npm run --prefix server db:mirgate
+```
+
+If at any point you need to reset the database, use this command `npm run --prefix server db:reset`
+
+### 5. Build client
+
+```
+cd ./frontend && NODE=production npm run build
+```
+
+### 6. Run server
+
+```
+cd ./server && npm run start:prod
+```
+
+The client will start on the **port 3000**, you can access the client by visiting the url created by codespace - `https:///apps/tooljet`
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.19.0/data-sources/clickhouse.md b/docs/versioned_docs/version-2.19.0/data-sources/clickhouse.md
index bb55b4a069..a9d60b9cd4 100644
--- a/docs/versioned_docs/version-2.19.0/data-sources/clickhouse.md
+++ b/docs/versioned_docs/version-2.19.0/data-sources/clickhouse.md
@@ -13,7 +13,7 @@ ToolJet uses this [NodeJS](https://github.com/TimonKK/clickhouse) client for Cli
## Connection
-To add a new ClickHouse datasource, Go to the **Datasource Manager** on the left sidebar of the app editor and click on `Add datasource` button. Select **ClickHouse** from the modal that pops up.
+To establish a connection with the Clickhouse data source, you can either click on the `+Add new data source` button located on the query panel or navigate to the **[Data Sources](/docs/data-sources/overview)** page through the ToolJet dashboard.
ToolJet requires the following to connect to your ClickHouse Database:
@@ -33,7 +33,7 @@ ToolJet requires the following to connect to your ClickHouse Database:
## Querying ClickHouse
-After setting up the ClickHouse datasource, you can click on the `+` button of the query manager and select the ClickHouse datasource that you added in the previous step to create a new query.
+After setting up the ClickHouse data source, you can click on the `+` button of the query manager and select the ClickHouse data source that you added in the previous step to create a new query.
:::info
For more details on clickhouse visit [Clickhouse docs](https://clickhouse.com/docs/en/quick-start).
diff --git a/docs/versioned_docs/version-2.19.0/how-to/bulk-update-multiple-rows-in-table.md b/docs/versioned_docs/version-2.19.0/how-to/bulk-update-multiple-rows-in-table.md
index b29e582b46..f518b117ac 100644
--- a/docs/versioned_docs/version-2.19.0/how-to/bulk-update-multiple-rows-in-table.md
+++ b/docs/versioned_docs/version-2.19.0/how-to/bulk-update-multiple-rows-in-table.md
@@ -5,56 +5,62 @@ title: Bulk update multiple rows in table
# Bulk update multiple rows in table
-Currently, the datasources in ToolJet have operation for **bulk update(GUI mode)** but that only works for changes made in the single row. We will soon be adding a new operation for bulk updating the multiple rows but for now we can bulk update multiple rows by creating a Custom JS query.
+Currently, the data sources in ToolJet have operation for **bulk update(GUI mode)** but that only works for changes made in the single row. We will soon be adding a new operation for bulk updating the multiple rows but for now we can bulk update multiple rows by creating a Custom JS query.
-In this guide, We have assumed that you have successfully connected the data source. For this guide, we will be using the PostgreSQL data source as an example database, currently, this workaround can be used only for PostgreSQL and MySQL.
+In this guide, We have assumed that you have successfully connected the data source. For this guide, we will be using the PostgreSQL data source as an example database. Currently, this workaround can be used only for PostgreSQL and MySQL.
## 1. Create a query to get the data from the database
-Let's create the query that will be getting the data from the database:
+- Create a postgresql query in **SQL mode** and enter
+
+```sql
+SELECT * FROM tooljet // replace tooljet with your table name
+```
+
+- Hit **Run** to fetch the data from the database
-
+
## 2. Display the data on the table
-- Drag a **Table** widget on the canvas and click on its handle to open the properties on the left sidebar
-- Edit the **Table data** field value and enter **`{{queries.postgresql1.data}}`**
+- Go to the **Components** library on the right and drag a **Table** component onto the canvas
+- Click on the handle of the **Table** component to open its properties on the right sidebar
+- Populate the table with the data from the query by entering **`{{queries..data}}`** in the **Data** field
-
+
## 3. Make the columns editable
-- Go to the **Columns**, Add or edit columns section and enter the **Column Name** that you want to display on the table and the **Key** name. Key is the name of the column in your database.
-- Enable the toggle for **Make editable** for the columns that you want to be editable.
+- Under the **Columns** accordion, click on the column name that you want to make editable
+- On clicking the column name, a new section will open. Enable the toggle for **Make editable** to make the column editable
-
+
-## 4. Enable bulk update options for table widget
+## 4. Enable Multiple Row Selection
-- Go to the **Options** section and enable the **Show update buttons**. Enabling this will add two buttons - **Save Changes** and **Discard Changes** at the bottom of the table, only when any cell in the table is edited.
-- You can also enable highlight selected row.(**Optional**)
+- Under the **Row Selection** accordion, enable the **Allow Selection**, **Highlight Selected Row**, and **Bulk Selection** option
-
+
## 5. Create a Custom JS query
-We will create a new Custom JS query(**runjs1**) that will generate SQL query for updating multiple rows.
+- Create a new Run Javascript query and use the code below to generate the SQL query for updating multiple rows.
```js
const uniqueIdentifier = "id"
@@ -81,36 +87,47 @@ Update **table1** with the name of the table you are using.
:::
-
+
## 6. Create an Update query
-Let's create a new PostgreSQL query and name it `update`. In **SQL mode**, enter `{{queries.runjs1.data.join(' ')}}` and **Save** it.
+- Create a postgresql query in **SQL mode** and rename it as **update**:
+
+```sql
+{{queries.runjs1.data.join(' ')}}
+```
+
+- This query will run the SQL query generated by the runjs1 query.
-
+
-## 7. Creating a flow for queries
+## 7. Adding event handlers to execute queries in sequence
-- Click on the handle of the **Table** widget to open its properties
-- Go to the **Events**, and add a handler
-- Select **Bulk Update** in Events, **Run Query** in Actions, and then select the **runjs1** query in Query. Now whenever a user will edit the table and hit the **Save Changes** button runjs1 will run.
+- Edit the **Table** component and add the event handler for **Save Changes** event so that whenever a user will edit the table and hit the **Save Changes** button the runjs1 query will run.
+- Add **loading state** to table so that whenever the **users** or **update** query is running the table will show a loading state.
+
+```js
+{{queries.users.isLoading || queries.update.isLoading}} // add this in the loading state field of the table
+```
-
+
-- Now, go to the **Advanced** tab of **runjs1** and add a handler to run update query for **Query Success** Event. Now whenever the runjs1 query will be run - the update operation will be performed on the database.
+- Now, go to the **runjs1** query and add a **Event** to run update query for **Query Success** Event. This will run the update query whenever the runjs1 query will be run.
-
+
-
\ No newline at end of file
+
+
+- Finally, go to the **update** query and add a **Event** to run the users query for **Query Success** Event. This will refresh the table whenever the update query will be run.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.19.0/setup/azure-container.md b/docs/versioned_docs/version-2.19.0/setup/azure-container.md
index 60bdc0aaa5..fe19e718dc 100644
--- a/docs/versioned_docs/version-2.19.0/setup/azure-container.md
+++ b/docs/versioned_docs/version-2.19.0/setup/azure-container.md
@@ -68,3 +68,19 @@ Please note that you need to set up a PostgreSQL database manually to be used by
You can access ToolJet via the application URL provided in the overview tab.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
diff --git a/docs/versioned_docs/version-2.19.0/setup/client.md b/docs/versioned_docs/version-2.19.0/setup/client.md
index ebea627ad9..a29cfb1b60 100644
--- a/docs/versioned_docs/version-2.19.0/setup/client.md
+++ b/docs/versioned_docs/version-2.19.0/setup/client.md
@@ -96,3 +96,19 @@ Summarising the steps below:
```bash
cd tooljet-assets && gcloud app deploy
```
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
diff --git a/docs/versioned_docs/version-2.19.0/setup/digitalocean.md b/docs/versioned_docs/version-2.19.0/setup/digitalocean.md
index 0030942f83..03c485dcf5 100644
--- a/docs/versioned_docs/version-2.19.0/setup/digitalocean.md
+++ b/docs/versioned_docs/version-2.19.0/setup/digitalocean.md
@@ -107,3 +107,19 @@ Follow the steps below to deploy ToolJet Database on DigitalOcean:
4. Add your newly created PostgREST app to the trusted sources of your managed or separate database.
5. Update your existing ToolJet application deployment with [environment variables](/docs/setup/env-vars#enable-tooljet-database--optional-) required for PostgREST.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.19.0/setup/docker.md b/docs/versioned_docs/version-2.19.0/setup/docker.md
index ea1671ef1f..8a80874ba0 100644
--- a/docs/versioned_docs/version-2.19.0/setup/docker.md
+++ b/docs/versioned_docs/version-2.19.0/setup/docker.md
@@ -128,11 +128,29 @@ Confused about which setup to select? Feel free to ask the community via Slack:
`sudo docker-compose up -d`
iv. Setup docker to run without root privileges by following the instructions written here https://docs.docker.com/engine/install/linux-postinstall/
- :::
+:::
-
-
-
-
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
+
+
+
+
+
+
diff --git a/docs/versioned_docs/version-2.19.0/setup/ec2.md b/docs/versioned_docs/version-2.19.0/setup/ec2.md
index 662b4f2d56..1c10b0e918 100644
--- a/docs/versioned_docs/version-2.19.0/setup/ec2.md
+++ b/docs/versioned_docs/version-2.19.0/setup/ec2.md
@@ -11,6 +11,13 @@ You should setup a PostgreSQL database manually to be used by the ToolJet server
*If you have any questions feel free to join our [Slack Community](https://tooljet.com/slack) or send us an email at hello@tooljet.com.*
+You can effortlessly deploy Amazon Elastic Compute Cloud Service (EC2) by utilizing a **CloudFormation template**. This template will deploy all the services required to run ToolJet on AWS EC2 instances.
+
+To deploy all the services at once, simply employ the following template:
+```
+curl -LO https://tooljet-deployments.s3.us-west-1.amazonaws.com/cloudformation/EC2-cloudfomration.yml
+```
+
Follow the steps below to deploy ToolJet on AWS EC2 instances.
1. Setup a PostgreSQL database and make sure that the database is accessible from the EC2 instance.
@@ -77,4 +84,26 @@ Follow the steps below to deploy ToolJet on AWS EC2 instances.
ToolJet AMI comes inbuilt with PostgREST. If you intend to use this feature, you'd only have to setup the environment variables in `~/app/.env` file and run `./setup_app` script.
-You can learn more about this feature [here](/docs/tooljet-database).
\ No newline at end of file
+You can learn more about this feature [here](/docs/tooljet-database).
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
+
+
+
+
+
+
diff --git a/docs/versioned_docs/version-2.19.0/setup/ecs.md b/docs/versioned_docs/version-2.19.0/setup/ecs.md
index c3eb758aa0..b4f3073222 100644
--- a/docs/versioned_docs/version-2.19.0/setup/ecs.md
+++ b/docs/versioned_docs/version-2.19.0/setup/ecs.md
@@ -228,3 +228,18 @@ Follow the steps below to deploy PostgREST on a ECS cluster.
Update ToolJet deployment with the appropriate env variables [here](https://docs.tooljet.com/docs/setup/env-vars/#enable-tooljet-database--optional-) and apply the changes.
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.19.0/setup/google-cloud-run.md b/docs/versioned_docs/version-2.19.0/setup/google-cloud-run.md
index 0431078dcc..3034395e2f 100644
--- a/docs/versioned_docs/version-2.19.0/setup/google-cloud-run.md
+++ b/docs/versioned_docs/version-2.19.0/setup/google-cloud-run.md
@@ -151,3 +151,20 @@ Once the Service is created and live, to make the Cloud Service URL public. Ple
+
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.19.0/setup/helm.md b/docs/versioned_docs/version-2.19.0/setup/helm.md
index cca63346c1..9062825d83 100644
--- a/docs/versioned_docs/version-2.19.0/setup/helm.md
+++ b/docs/versioned_docs/version-2.19.0/setup/helm.md
@@ -13,7 +13,7 @@ This repository contains Helm charts for deploying [ToolJet](https://github.com/
### From Helm repo
```bash
-helm repo add tooljet https://github.com/ToolJet/helm-charts.git
+helm repo add tooljet https://tooljet.github.io/helm-charts
helm install tooljet tooljet/tooljet
```
@@ -33,4 +33,20 @@ For more information about the ToolJet database, you can visit [here](/docs/tool
If you plan to use this feature, you need to set up and deploy the PostgREST server, which facilitates querying the ToolJet Database.
-To enable the ToolJet database, please set the environment variable `ENABLE_TOOLJET_DB` to true in the `values.yaml` file.
\ No newline at end of file
+To enable the ToolJet database, please set the environment variable `ENABLE_TOOLJET_DB` to true in the `values.yaml` file.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
diff --git a/docs/versioned_docs/version-2.19.0/setup/kubernetes-aks.md b/docs/versioned_docs/version-2.19.0/setup/kubernetes-aks.md
index 04cc1515d2..35027ad21f 100644
--- a/docs/versioned_docs/version-2.19.0/setup/kubernetes-aks.md
+++ b/docs/versioned_docs/version-2.19.0/setup/kubernetes-aks.md
@@ -53,3 +53,19 @@ If you intend to use this feature, you'd have to set up and deploy PostgREST ser
```
2. Update ToolJet deployment with the appropriate env variables [here](https://tooljet-deployments.s3.us-west-1.amazonaws.com/kubernetes/AKS/deployment.yaml) and apply the changes.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.19.0/setup/kubernetes-gke.md b/docs/versioned_docs/version-2.19.0/setup/kubernetes-gke.md
index c87a6c36bd..27447189f0 100644
--- a/docs/versioned_docs/version-2.19.0/setup/kubernetes-gke.md
+++ b/docs/versioned_docs/version-2.19.0/setup/kubernetes-gke.md
@@ -79,3 +79,19 @@ If you intend to use this feature, you'd have to set up and deploy PostgREST ser
```
2. Update ToolJet deployment with the appropriate env variables [here](https://tooljet-deployments.s3.us-west-1.amazonaws.com/kubernetes/GKE/deployment.yaml) and apply the changes.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.19.0/setup/kubernetes.md b/docs/versioned_docs/version-2.19.0/setup/kubernetes.md
index 10441ef99d..4155bcae09 100644
--- a/docs/versioned_docs/version-2.19.0/setup/kubernetes.md
+++ b/docs/versioned_docs/version-2.19.0/setup/kubernetes.md
@@ -62,3 +62,19 @@ If you intend to use this feature, you'd have to set up and deploy PostgREST ser
```
2. Update ToolJet deployment with the appropriate env variables [here](https://tooljet-deployments.s3.us-west-1.amazonaws.com/kubernetes/deployment.yaml) and apply the changes.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.19.0/setup/openshift.md b/docs/versioned_docs/version-2.19.0/setup/openshift.md
index 73f6a7e531..10cebdf7db 100644
--- a/docs/versioned_docs/version-2.19.0/setup/openshift.md
+++ b/docs/versioned_docs/version-2.19.0/setup/openshift.md
@@ -68,3 +68,19 @@ If you intend to use this feature, you'd have to set up and deploy PostgREST ser
```
https://tooljet-deployments.s3.us-west-1.amazonaws.com/openshift/postgrest.yaml
```
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.19.0/setup/tooljet-subpath.md b/docs/versioned_docs/version-2.19.0/setup/tooljet-subpath.md
index e05625d5d6..51c8a438ad 100644
--- a/docs/versioned_docs/version-2.19.0/setup/tooljet-subpath.md
+++ b/docs/versioned_docs/version-2.19.0/setup/tooljet-subpath.md
@@ -20,4 +20,20 @@ You'll need to setup the following environment variables if ToolJet installation
See all **[Environment Variables](/docs/setup/env-vars)** here.
:::
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
+
diff --git a/docs/versioned_docs/version-2.19.0/setup/try-tooljet.md b/docs/versioned_docs/version-2.19.0/setup/try-tooljet.md
index eb60b5323a..59c9108cf2 100644
--- a/docs/versioned_docs/version-2.19.0/setup/try-tooljet.md
+++ b/docs/versioned_docs/version-2.19.0/setup/try-tooljet.md
@@ -10,16 +10,16 @@ title: Try ToolJet
You can run the command below to have ToolJet up and running right away.
```bash
-docker run \
+docker run -d \
--name tooljet \
--restart unless-stopped \
-p 80:80 \
+ --platform linux/amd64 \
-v tooljet_data:/var/lib/postgresql/13/main \
tooljet/try:latest
```
*If you have any questions feel free to join our [Slack Community](https://tooljet.com/slack) or send us an email at hello@tooljet.com.*
-
#### Setup information
- Runs the ToolJet server on the port 80 on your machine.
diff --git a/docs/versioned_docs/version-2.2.0/setup/azure-container.md b/docs/versioned_docs/version-2.2.0/setup/azure-container.md
index b9e9f9947f..c0d9138d6e 100644
--- a/docs/versioned_docs/version-2.2.0/setup/azure-container.md
+++ b/docs/versioned_docs/version-2.2.0/setup/azure-container.md
@@ -65,3 +65,19 @@ Please note that you need to set up a PostgreSQL database manually to be used by
You can access ToolJet via the application URL provided in the overview tab.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
diff --git a/docs/versioned_docs/version-2.2.0/setup/client.md b/docs/versioned_docs/version-2.2.0/setup/client.md
index ebea627ad9..a29cfb1b60 100644
--- a/docs/versioned_docs/version-2.2.0/setup/client.md
+++ b/docs/versioned_docs/version-2.2.0/setup/client.md
@@ -96,3 +96,19 @@ Summarising the steps below:
```bash
cd tooljet-assets && gcloud app deploy
```
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
diff --git a/docs/versioned_docs/version-2.2.0/setup/digitalocean.md b/docs/versioned_docs/version-2.2.0/setup/digitalocean.md
index a4143f9e4f..ab64f0b3bd 100644
--- a/docs/versioned_docs/version-2.2.0/setup/digitalocean.md
+++ b/docs/versioned_docs/version-2.2.0/setup/digitalocean.md
@@ -64,3 +64,19 @@ Follow the steps below to deploy ToolJet Database on DigitalOcean:
4. Add your newly created PostgREST app to the trusted sources of your managed or separate database.
5. Update your existing ToolJet application deployment with [environment variables](/docs/setup/env-vars#tooljet-database-feature-enable--optional-) required for PostgREST.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.2.0/setup/docker.md b/docs/versioned_docs/version-2.2.0/setup/docker.md
index 7215a1bb59..a5abea0646 100644
--- a/docs/versioned_docs/version-2.2.0/setup/docker.md
+++ b/docs/versioned_docs/version-2.2.0/setup/docker.md
@@ -126,11 +126,29 @@ Confused about which setup to select? Feel free to ask the community via Slack:
`sudo docker-compose up -d`
iv. Setup docker to run without root privileges by following the instructions written here https://docs.docker.com/engine/install/linux-postinstall/
- :::
+:::
-
-
-
-
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
+
+
+
+
+
+
diff --git a/docs/versioned_docs/version-2.2.0/setup/ec2.md b/docs/versioned_docs/version-2.2.0/setup/ec2.md
index 540b16c50d..55b0cdb563 100644
--- a/docs/versioned_docs/version-2.2.0/setup/ec2.md
+++ b/docs/versioned_docs/version-2.2.0/setup/ec2.md
@@ -77,4 +77,26 @@ Follow the steps below to deploy ToolJet on AWS EC2 instances.
ToolJet AMI comes inbuilt with PostgREST. If you intend to use this feature, you'd only have to setup the environment variables in `~/app/.env` file and run `./setup_app` script.
-You can learn more about this feature [here](/docs/tooljet-database).
\ No newline at end of file
+You can learn more about this feature [here](/docs/tooljet-database).
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
+
+
+
+
+
+
diff --git a/docs/versioned_docs/version-2.2.0/setup/ecs.md b/docs/versioned_docs/version-2.2.0/setup/ecs.md
index b16770014a..a21236d5e0 100644
--- a/docs/versioned_docs/version-2.2.0/setup/ecs.md
+++ b/docs/versioned_docs/version-2.2.0/setup/ecs.md
@@ -77,3 +77,18 @@ Follow the steps below to deploy ToolJet on a ECS cluster.
The setup above is just a template. Feel free to update the task definition and configure parameters for resources and environment variables according to your needs.
:::
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.2.0/setup/google-cloud-run.md b/docs/versioned_docs/version-2.2.0/setup/google-cloud-run.md
index 0aba9f1854..8fae7cf56e 100644
--- a/docs/versioned_docs/version-2.2.0/setup/google-cloud-run.md
+++ b/docs/versioned_docs/version-2.2.0/setup/google-cloud-run.md
@@ -151,3 +151,20 @@ Once the Service is created and live, to make the Cloud Service URL public. Ple
+
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.2.0/setup/helm.md b/docs/versioned_docs/version-2.2.0/setup/helm.md
index cca63346c1..ce2632a837 100644
--- a/docs/versioned_docs/version-2.2.0/setup/helm.md
+++ b/docs/versioned_docs/version-2.2.0/setup/helm.md
@@ -33,4 +33,20 @@ For more information about the ToolJet database, you can visit [here](/docs/tool
If you plan to use this feature, you need to set up and deploy the PostgREST server, which facilitates querying the ToolJet Database.
-To enable the ToolJet database, please set the environment variable `ENABLE_TOOLJET_DB` to true in the `values.yaml` file.
\ No newline at end of file
+To enable the ToolJet database, please set the environment variable `ENABLE_TOOLJET_DB` to true in the `values.yaml` file.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.2.0/setup/heroku.md b/docs/versioned_docs/version-2.2.0/setup/heroku.md
index 80e14d2c06..eeafb5aa46 100644
--- a/docs/versioned_docs/version-2.2.0/setup/heroku.md
+++ b/docs/versioned_docs/version-2.2.0/setup/heroku.md
@@ -143,3 +143,19 @@ Please install Heroku CLI on your local machine. Please refer Heroku CLI install
Please enter the below env variables in the Tooljet application, under the setting tab. You can also refer environment variable [**here**](/docs/setup/env-vars#tooljet-database).
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.2.0/setup/kubernetes-aks.md b/docs/versioned_docs/version-2.2.0/setup/kubernetes-aks.md
index db2ffea0cb..d5c263bae3 100644
--- a/docs/versioned_docs/version-2.2.0/setup/kubernetes-aks.md
+++ b/docs/versioned_docs/version-2.2.0/setup/kubernetes-aks.md
@@ -53,3 +53,19 @@ If you intend to use this feature, you'd have to set up and deploy PostgREST ser
```
2. Update ToolJet deployment with the appropriate env variables [here](https://github.com/ToolJet/ToolJet/blob/chore/main/kubernetes/GKE/deployment.yaml#L62) and apply the changes.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.2.0/setup/kubernetes-gke.md b/docs/versioned_docs/version-2.2.0/setup/kubernetes-gke.md
index af86339fec..2fd124631d 100644
--- a/docs/versioned_docs/version-2.2.0/setup/kubernetes-gke.md
+++ b/docs/versioned_docs/version-2.2.0/setup/kubernetes-gke.md
@@ -79,3 +79,19 @@ If you intend to use this feature, you'd have to set up and deploy PostgREST ser
```
2. Update ToolJet deployment with the appropriate env variables [here](https://raw.githubusercontent.com/ToolJet/ToolJet/main/deploy/kubernetes/GKE/deployment.yaml) and apply the changes.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.2.0/setup/kubernetes.md b/docs/versioned_docs/version-2.2.0/setup/kubernetes.md
index f3caf2b871..b3bd0050f2 100644
--- a/docs/versioned_docs/version-2.2.0/setup/kubernetes.md
+++ b/docs/versioned_docs/version-2.2.0/setup/kubernetes.md
@@ -61,3 +61,19 @@ If you intend to use this feature, you'd have to set up and deploy PostgREST ser
```
2. Update ToolJet deployment with the appropriate env variables [here](https://raw.githubusercontent.com/ToolJet/ToolJet/main/deploy/kubernetes/deployment.yaml) and apply the changes.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.2.0/setup/openshift.md b/docs/versioned_docs/version-2.2.0/setup/openshift.md
index 1cdb3dd674..28a318e14f 100644
--- a/docs/versioned_docs/version-2.2.0/setup/openshift.md
+++ b/docs/versioned_docs/version-2.2.0/setup/openshift.md
@@ -67,4 +67,20 @@ If you intend to use this feature, you'd have to set up and deploy PostgREST ser
```
https://raw.githubusercontent.com/ToolJet/ToolJet/main/deploy/openshift/postgrest.yaml
-```
\ No newline at end of file
+```
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.2.0/setup/tooljet-subpath.md b/docs/versioned_docs/version-2.2.0/setup/tooljet-subpath.md
index e05625d5d6..51c8a438ad 100644
--- a/docs/versioned_docs/version-2.2.0/setup/tooljet-subpath.md
+++ b/docs/versioned_docs/version-2.2.0/setup/tooljet-subpath.md
@@ -20,4 +20,20 @@ You'll need to setup the following environment variables if ToolJet installation
See all **[Environment Variables](/docs/setup/env-vars)** here.
:::
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
+
diff --git a/docs/versioned_docs/version-2.2.0/setup/try-tooljet.md b/docs/versioned_docs/version-2.2.0/setup/try-tooljet.md
index 7ba26756aa..59c9108cf2 100644
--- a/docs/versioned_docs/version-2.2.0/setup/try-tooljet.md
+++ b/docs/versioned_docs/version-2.2.0/setup/try-tooljet.md
@@ -4,15 +4,17 @@ title: Try ToolJet
---
# Try ToolJet
+
## On local with Docker
You can run the command below to have ToolJet up and running right away.
```bash
-docker run \
+docker run -d \
--name tooljet \
--restart unless-stopped \
-p 80:80 \
+ --platform linux/amd64 \
-v tooljet_data:/var/lib/postgresql/13/main \
tooljet/try:latest
```
diff --git a/docs/versioned_docs/version-2.22.0/contributing-guide/setup/codespaces.md b/docs/versioned_docs/version-2.22.0/contributing-guide/setup/codespaces.md
new file mode 100644
index 0000000000..1204d71f63
--- /dev/null
+++ b/docs/versioned_docs/version-2.22.0/contributing-guide/setup/codespaces.md
@@ -0,0 +1,117 @@
+---
+id: codespaces
+title: GitHub Codespaces
+---
+
+Follow the steps below to set up ToolJet on GitHub Codespaces. We recommend reading our guide on [architecture](https://docs.tooljet.com/docs/contributing-guide/setup/architecture) of ToolJet before proceeding.
+
+Open the terminal and run the commands below.
+
+## Setting up
+
+### 1. Set up the environment
+
+1. Install Node.js ( version: v18.3.0 ) and npm (version: v8.11.0)
+
+```
+nvm install 18.3.0
+nvm use 18.3.0
+npm install -g npm@8.11.0
+```
+
+2. Install Postgres
+
+```
+sudo sh -c 'echo "deb [http://apt.postgresql.org/pub/repos/apt](http://apt.postgresql.org/pub/repos/apt) $(lsb_release -cs)-pgdg main" > /etc/apt/sources.list.d/pgdg.list'
+
+wget --quiet -O - [https://www.postgresql.org/media/keys/ACCC4CF8.asc](https://www.postgresql.org/media/keys/ACCC4CF8.asc) | sudo apt-key add -
+
+sudo apt-get update
+
+sudo apt-get install postgresql-13 postgresql-contrib-13
+```
+
+To start the postgresql service run the below command:
+
+```
+sudo service postgresql start
+```
+
+If you wish to change the password of the installed postresql service run the below commands:
+
+```
+sudo su
+
+sudo -u postgres psql
+
+\password postgres
+
+\q
+```
+
+### 2. Set up environment variables
+
+Create a `.env` file by running the command `touch .env`. More information on the variables that can be set is given in the [environment variables reference](https://docs.tooljet.com/docs/setup/env-vars)
+
+**For basic set-up you add the below env variables:**
+
+```
+TOOLJET_HOST=http://localhost:3000
+
+LOCKBOX_MASTER_KEY=
+
+SECRET_KEY_BASE=
+
+PG_USER=postgres
+
+PG_HOST=localhost
+
+PG_PASS=postgres
+
+PG_DB=tooljet_prod
+
+SUB_PATH=/apps/tooljet/
+
+NODE_ENV=production
+
+SERVE_CLIENT=true
+```
+
+> `SECRET_KEY_BASE` requires a 64 byte key. (If you have `openssl` installed, run `openssl rand -hex 64` to create a 64 byte secure random key)
+>
+> `LOCKBOX_MASTER_KEY` requires a 32 byte key. (Run `openssl rand -hex 32` to create a 32 byte secure random key)
+
+### 3. Install and build dependencies
+
+Make sure node version is set to 18.3.0 before running the below command:
+
+```
+npm install
+npm install --prefix server
+npm install --prefix frontend
+npm run build:plugins
+```
+
+
+### 4. Set up database
+
+```
+npm run --prefix server db:create
+npm run --prefix server db:mirgate
+```
+
+If at any point you need to reset the database, use this command `npm run --prefix server db:reset`
+
+### 5. Build client
+
+```
+cd ./frontend && NODE=production npm run build
+```
+
+### 6. Run server
+
+```
+cd ./server && npm run start:prod
+```
+
+The client will start on the **port 3000**, you can access the client by visiting the url created by codespace - `https:///apps/tooljet`
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.22.0/how-to/bulk-update-multiple-rows-in-table.md b/docs/versioned_docs/version-2.22.0/how-to/bulk-update-multiple-rows-in-table.md
index b29e582b46..f518b117ac 100644
--- a/docs/versioned_docs/version-2.22.0/how-to/bulk-update-multiple-rows-in-table.md
+++ b/docs/versioned_docs/version-2.22.0/how-to/bulk-update-multiple-rows-in-table.md
@@ -5,56 +5,62 @@ title: Bulk update multiple rows in table
# Bulk update multiple rows in table
-Currently, the datasources in ToolJet have operation for **bulk update(GUI mode)** but that only works for changes made in the single row. We will soon be adding a new operation for bulk updating the multiple rows but for now we can bulk update multiple rows by creating a Custom JS query.
+Currently, the data sources in ToolJet have operation for **bulk update(GUI mode)** but that only works for changes made in the single row. We will soon be adding a new operation for bulk updating the multiple rows but for now we can bulk update multiple rows by creating a Custom JS query.
-In this guide, We have assumed that you have successfully connected the data source. For this guide, we will be using the PostgreSQL data source as an example database, currently, this workaround can be used only for PostgreSQL and MySQL.
+In this guide, We have assumed that you have successfully connected the data source. For this guide, we will be using the PostgreSQL data source as an example database. Currently, this workaround can be used only for PostgreSQL and MySQL.
## 1. Create a query to get the data from the database
-Let's create the query that will be getting the data from the database:
+- Create a postgresql query in **SQL mode** and enter
+
+```sql
+SELECT * FROM tooljet // replace tooljet with your table name
+```
+
+- Hit **Run** to fetch the data from the database
-
+
## 2. Display the data on the table
-- Drag a **Table** widget on the canvas and click on its handle to open the properties on the left sidebar
-- Edit the **Table data** field value and enter **`{{queries.postgresql1.data}}`**
+- Go to the **Components** library on the right and drag a **Table** component onto the canvas
+- Click on the handle of the **Table** component to open its properties on the right sidebar
+- Populate the table with the data from the query by entering **`{{queries..data}}`** in the **Data** field
-
+
## 3. Make the columns editable
-- Go to the **Columns**, Add or edit columns section and enter the **Column Name** that you want to display on the table and the **Key** name. Key is the name of the column in your database.
-- Enable the toggle for **Make editable** for the columns that you want to be editable.
+- Under the **Columns** accordion, click on the column name that you want to make editable
+- On clicking the column name, a new section will open. Enable the toggle for **Make editable** to make the column editable
-
+
-## 4. Enable bulk update options for table widget
+## 4. Enable Multiple Row Selection
-- Go to the **Options** section and enable the **Show update buttons**. Enabling this will add two buttons - **Save Changes** and **Discard Changes** at the bottom of the table, only when any cell in the table is edited.
-- You can also enable highlight selected row.(**Optional**)
+- Under the **Row Selection** accordion, enable the **Allow Selection**, **Highlight Selected Row**, and **Bulk Selection** option
-
+
## 5. Create a Custom JS query
-We will create a new Custom JS query(**runjs1**) that will generate SQL query for updating multiple rows.
+- Create a new Run Javascript query and use the code below to generate the SQL query for updating multiple rows.
```js
const uniqueIdentifier = "id"
@@ -81,36 +87,47 @@ Update **table1** with the name of the table you are using.
:::
-
+
## 6. Create an Update query
-Let's create a new PostgreSQL query and name it `update`. In **SQL mode**, enter `{{queries.runjs1.data.join(' ')}}` and **Save** it.
+- Create a postgresql query in **SQL mode** and rename it as **update**:
+
+```sql
+{{queries.runjs1.data.join(' ')}}
+```
+
+- This query will run the SQL query generated by the runjs1 query.
-
+
-## 7. Creating a flow for queries
+## 7. Adding event handlers to execute queries in sequence
-- Click on the handle of the **Table** widget to open its properties
-- Go to the **Events**, and add a handler
-- Select **Bulk Update** in Events, **Run Query** in Actions, and then select the **runjs1** query in Query. Now whenever a user will edit the table and hit the **Save Changes** button runjs1 will run.
+- Edit the **Table** component and add the event handler for **Save Changes** event so that whenever a user will edit the table and hit the **Save Changes** button the runjs1 query will run.
+- Add **loading state** to table so that whenever the **users** or **update** query is running the table will show a loading state.
+
+```js
+{{queries.users.isLoading || queries.update.isLoading}} // add this in the loading state field of the table
+```
-
+
-- Now, go to the **Advanced** tab of **runjs1** and add a handler to run update query for **Query Success** Event. Now whenever the runjs1 query will be run - the update operation will be performed on the database.
+- Now, go to the **runjs1** query and add a **Event** to run update query for **Query Success** Event. This will run the update query whenever the runjs1 query will be run.
-
+
-
\ No newline at end of file
+
+
+- Finally, go to the **update** query and add a **Event** to run the users query for **Query Success** Event. This will refresh the table whenever the update query will be run.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.22.0/setup/azure-container.md b/docs/versioned_docs/version-2.22.0/setup/azure-container.md
index 60bdc0aaa5..fe19e718dc 100644
--- a/docs/versioned_docs/version-2.22.0/setup/azure-container.md
+++ b/docs/versioned_docs/version-2.22.0/setup/azure-container.md
@@ -68,3 +68,19 @@ Please note that you need to set up a PostgreSQL database manually to be used by
You can access ToolJet via the application URL provided in the overview tab.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
diff --git a/docs/versioned_docs/version-2.22.0/setup/client.md b/docs/versioned_docs/version-2.22.0/setup/client.md
index ebea627ad9..a29cfb1b60 100644
--- a/docs/versioned_docs/version-2.22.0/setup/client.md
+++ b/docs/versioned_docs/version-2.22.0/setup/client.md
@@ -96,3 +96,19 @@ Summarising the steps below:
```bash
cd tooljet-assets && gcloud app deploy
```
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
diff --git a/docs/versioned_docs/version-2.22.0/setup/digitalocean.md b/docs/versioned_docs/version-2.22.0/setup/digitalocean.md
index 0030942f83..03c485dcf5 100644
--- a/docs/versioned_docs/version-2.22.0/setup/digitalocean.md
+++ b/docs/versioned_docs/version-2.22.0/setup/digitalocean.md
@@ -107,3 +107,19 @@ Follow the steps below to deploy ToolJet Database on DigitalOcean:
4. Add your newly created PostgREST app to the trusted sources of your managed or separate database.
5. Update your existing ToolJet application deployment with [environment variables](/docs/setup/env-vars#enable-tooljet-database--optional-) required for PostgREST.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.22.0/setup/docker.md b/docs/versioned_docs/version-2.22.0/setup/docker.md
index ea1671ef1f..8a80874ba0 100644
--- a/docs/versioned_docs/version-2.22.0/setup/docker.md
+++ b/docs/versioned_docs/version-2.22.0/setup/docker.md
@@ -128,11 +128,29 @@ Confused about which setup to select? Feel free to ask the community via Slack:
`sudo docker-compose up -d`
iv. Setup docker to run without root privileges by following the instructions written here https://docs.docker.com/engine/install/linux-postinstall/
- :::
+:::
-
-
-
-
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
+
+
+
+
+
+
diff --git a/docs/versioned_docs/version-2.22.0/setup/ec2.md b/docs/versioned_docs/version-2.22.0/setup/ec2.md
index 662b4f2d56..1c10b0e918 100644
--- a/docs/versioned_docs/version-2.22.0/setup/ec2.md
+++ b/docs/versioned_docs/version-2.22.0/setup/ec2.md
@@ -11,6 +11,13 @@ You should setup a PostgreSQL database manually to be used by the ToolJet server
*If you have any questions feel free to join our [Slack Community](https://tooljet.com/slack) or send us an email at hello@tooljet.com.*
+You can effortlessly deploy Amazon Elastic Compute Cloud Service (EC2) by utilizing a **CloudFormation template**. This template will deploy all the services required to run ToolJet on AWS EC2 instances.
+
+To deploy all the services at once, simply employ the following template:
+```
+curl -LO https://tooljet-deployments.s3.us-west-1.amazonaws.com/cloudformation/EC2-cloudfomration.yml
+```
+
Follow the steps below to deploy ToolJet on AWS EC2 instances.
1. Setup a PostgreSQL database and make sure that the database is accessible from the EC2 instance.
@@ -77,4 +84,26 @@ Follow the steps below to deploy ToolJet on AWS EC2 instances.
ToolJet AMI comes inbuilt with PostgREST. If you intend to use this feature, you'd only have to setup the environment variables in `~/app/.env` file and run `./setup_app` script.
-You can learn more about this feature [here](/docs/tooljet-database).
\ No newline at end of file
+You can learn more about this feature [here](/docs/tooljet-database).
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
+
+
+
+
+
+
diff --git a/docs/versioned_docs/version-2.22.0/setup/ecs.md b/docs/versioned_docs/version-2.22.0/setup/ecs.md
index c3eb758aa0..b4f3073222 100644
--- a/docs/versioned_docs/version-2.22.0/setup/ecs.md
+++ b/docs/versioned_docs/version-2.22.0/setup/ecs.md
@@ -228,3 +228,18 @@ Follow the steps below to deploy PostgREST on a ECS cluster.
Update ToolJet deployment with the appropriate env variables [here](https://docs.tooljet.com/docs/setup/env-vars/#enable-tooljet-database--optional-) and apply the changes.
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.22.0/setup/google-cloud-run.md b/docs/versioned_docs/version-2.22.0/setup/google-cloud-run.md
index 0431078dcc..3034395e2f 100644
--- a/docs/versioned_docs/version-2.22.0/setup/google-cloud-run.md
+++ b/docs/versioned_docs/version-2.22.0/setup/google-cloud-run.md
@@ -151,3 +151,20 @@ Once the Service is created and live, to make the Cloud Service URL public. Ple
+
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.22.0/setup/helm.md b/docs/versioned_docs/version-2.22.0/setup/helm.md
index cca63346c1..ce2632a837 100644
--- a/docs/versioned_docs/version-2.22.0/setup/helm.md
+++ b/docs/versioned_docs/version-2.22.0/setup/helm.md
@@ -33,4 +33,20 @@ For more information about the ToolJet database, you can visit [here](/docs/tool
If you plan to use this feature, you need to set up and deploy the PostgREST server, which facilitates querying the ToolJet Database.
-To enable the ToolJet database, please set the environment variable `ENABLE_TOOLJET_DB` to true in the `values.yaml` file.
\ No newline at end of file
+To enable the ToolJet database, please set the environment variable `ENABLE_TOOLJET_DB` to true in the `values.yaml` file.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.22.0/setup/kubernetes-aks.md b/docs/versioned_docs/version-2.22.0/setup/kubernetes-aks.md
index 04cc1515d2..35027ad21f 100644
--- a/docs/versioned_docs/version-2.22.0/setup/kubernetes-aks.md
+++ b/docs/versioned_docs/version-2.22.0/setup/kubernetes-aks.md
@@ -53,3 +53,19 @@ If you intend to use this feature, you'd have to set up and deploy PostgREST ser
```
2. Update ToolJet deployment with the appropriate env variables [here](https://tooljet-deployments.s3.us-west-1.amazonaws.com/kubernetes/AKS/deployment.yaml) and apply the changes.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.22.0/setup/kubernetes-gke.md b/docs/versioned_docs/version-2.22.0/setup/kubernetes-gke.md
index c87a6c36bd..27447189f0 100644
--- a/docs/versioned_docs/version-2.22.0/setup/kubernetes-gke.md
+++ b/docs/versioned_docs/version-2.22.0/setup/kubernetes-gke.md
@@ -79,3 +79,19 @@ If you intend to use this feature, you'd have to set up and deploy PostgREST ser
```
2. Update ToolJet deployment with the appropriate env variables [here](https://tooljet-deployments.s3.us-west-1.amazonaws.com/kubernetes/GKE/deployment.yaml) and apply the changes.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.22.0/setup/kubernetes.md b/docs/versioned_docs/version-2.22.0/setup/kubernetes.md
index 10441ef99d..4155bcae09 100644
--- a/docs/versioned_docs/version-2.22.0/setup/kubernetes.md
+++ b/docs/versioned_docs/version-2.22.0/setup/kubernetes.md
@@ -62,3 +62,19 @@ If you intend to use this feature, you'd have to set up and deploy PostgREST ser
```
2. Update ToolJet deployment with the appropriate env variables [here](https://tooljet-deployments.s3.us-west-1.amazonaws.com/kubernetes/deployment.yaml) and apply the changes.
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.22.0/setup/openshift.md b/docs/versioned_docs/version-2.22.0/setup/openshift.md
index 73f6a7e531..10cebdf7db 100644
--- a/docs/versioned_docs/version-2.22.0/setup/openshift.md
+++ b/docs/versioned_docs/version-2.22.0/setup/openshift.md
@@ -68,3 +68,19 @@ If you intend to use this feature, you'd have to set up and deploy PostgREST ser
```
https://tooljet-deployments.s3.us-west-1.amazonaws.com/openshift/postgrest.yaml
```
+
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.22.0/setup/tooljet-subpath.md b/docs/versioned_docs/version-2.22.0/setup/tooljet-subpath.md
index e05625d5d6..51c8a438ad 100644
--- a/docs/versioned_docs/version-2.22.0/setup/tooljet-subpath.md
+++ b/docs/versioned_docs/version-2.22.0/setup/tooljet-subpath.md
@@ -20,4 +20,20 @@ You'll need to setup the following environment variables if ToolJet installation
See all **[Environment Variables](/docs/setup/env-vars)** here.
:::
+## Upgrading to v2.24.3-ee2.10.2
+
+Version v2.24.3-ee2.10.2 includes architectural changes and, hence, comes with new migrations.
+
+If this is a new installation of the application, you may start directly with version v2.24.3-ee2.10.2. This guide is not required for new installations.
+
+#### Prerequisites for Upgrading to the Latest Version:
+
+- It is **crucial to perform a comprehensive backup of your database** before starting the upgrade process to prevent data loss.
+
+- Ensure that your current version is v2.23.3-ee2.10.2 before upgrading.
+
+- Users on versions earlier than v2.23.3-ee2.10.2 must first upgrade to this version before proceeding to v2.24.3-ee2.10.2.
+
+For specific issues or questions, refer to our **[Slack](https://tooljet.slack.com/join/shared_invite/zt-25438diev-mJ6LIZpJevG0LXCEcL0NhQ#)**.
+
diff --git a/docs/versioned_docs/version-2.22.0/setup/try-tooljet.md b/docs/versioned_docs/version-2.22.0/setup/try-tooljet.md
index eb60b5323a..59c9108cf2 100644
--- a/docs/versioned_docs/version-2.22.0/setup/try-tooljet.md
+++ b/docs/versioned_docs/version-2.22.0/setup/try-tooljet.md
@@ -10,16 +10,16 @@ title: Try ToolJet
You can run the command below to have ToolJet up and running right away.
```bash
-docker run \
+docker run -d \
--name tooljet \
--restart unless-stopped \
-p 80:80 \
+ --platform linux/amd64 \
-v tooljet_data:/var/lib/postgresql/13/main \
tooljet/try:latest
```
*If you have any questions feel free to join our [Slack Community](https://tooljet.com/slack) or send us an email at hello@tooljet.com.*
-
#### Setup information
- Runs the ToolJet server on the port 80 on your machine.
diff --git a/docs/versioned_docs/version-2.23.0/Enterprise/_category_.json b/docs/versioned_docs/version-2.23.0/Enterprise/_category_.json
new file mode 100644
index 0000000000..b9b132f890
--- /dev/null
+++ b/docs/versioned_docs/version-2.23.0/Enterprise/_category_.json
@@ -0,0 +1,5 @@
+{
+ "label": "Enterprise",
+ "position": 9,
+ "collapsed": true
+}
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.23.0/Enterprise/audit_logs.md b/docs/versioned_docs/version-2.23.0/Enterprise/audit_logs.md
new file mode 100644
index 0000000000..5681e15ae9
--- /dev/null
+++ b/docs/versioned_docs/version-2.23.0/Enterprise/audit_logs.md
@@ -0,0 +1,141 @@
+---
+id: audit_logs
+title: Audit logs
+---
+
+
Available on: Paid plans
+
+
+The audit log is the report of all the activities done in your ToolJet account. It will capture and display events automatically by recording who performed an activity, what when, and where the activity was performed, along with other information such as IP address.
+
+
+
+
+
+
+
+### Date Range
+
+Retrieve the log of events that occurred within the specified date and time range using the range picker. By default, the system loads 24-hour logs for the initial view. The maximum duration that can be specified for the "from" and "to" dates is 30 days.
+
+:::info
+Pagination at the bottom allows navigation through the pages, with each page displaying a maximum of 7 logs.
+:::
+
+
+
+
+
+
+
+### Filter Audit Logs
+
+You can apply filters to the audited events based on the following criteria.
+
+#### Select Users
+
+Choose a specific user from the dropdown list to view all their activities.
+
+#### Select Apps
+
+The dropdown will display all the apps associated with your account. Select an app to filter the logs related to that particular app.
+
+#### Select Resources
+
+| Resources | description |
+| ----------- | ----------- |
+| User | Filter all the User events like `USER_LOGIN`, `USER_SIGNUP`, `USER_INVITE`, AND `USER_INVITE_REDEEM`. |
+| App | Filter all the App events like `APP_CREATE`, `APP_UPDATE`,`APP_VIEW`,`APP_DELETE`,`APP_IMPORT`,`APP_EXPORT`,`APP_CLONE`. |
+| Data Query | Filters the events associated with Data Query like `DATA_QUERY_RUN`. |
+| Group Permission | All the events associated with Group Permissions will be filtered. Group Permissions include `GROUP_CREATE`, `GROUP_UPDATE`, `GROUP_DELETE`. |
+| App Group Permission | Within each group, you can set apps for read or edit privileges. These events get recorded as App Group Permissions. |
+
+#### Select Actions
+
+| Actions | description |
+| ----------- | ----------- |
+| USER_LOGIN | This event is recorded everytime a user logins. |
+| USER_SIGNUP | This event is recorded everytime a new signup is made. |
+| USER_INVITE | You can invite users to your account from `Manage Users` section and an event is audited everytime an invite is sent. |
+| USER_INVITE_REDEEM | This event is recorded whenever an invite is redeemed. |
+| APP_CREATE | This event is recorded when a user creates a new app. |
+| APP_UPDATE | This event is recorded whenever actions like renaming the app, making the app public, editing shareable link, or deploying the app are made. |
+| APP_VIEW | This event is logged when someone views the launched app. (public apps aren't accounted for) |
+| APP_DELETE | This event is recorded whenever a user deletes an app from the dashboard. |
+| APP_IMPORT | This event is recorded whenever a user imports an app. |
+| APP_EXPORT | This event is recorded whenever an app is exported. |
+| APP_CLONE | This event is recorded whenever a clone of the existing app is created. |
+| DATA_QUERY_RUN | This event is logged whenever a data source is added, a query is created, or whenever a query is run either from the query editor or from the launched app. |
+| GROUP_PERMISSION_CREATE | This event is recorded whenever a group is created. |
+| GROUP_PERMISSION_UPDATE | This event is recorded whenever an app or user is added to or removed from a group, or the permissions for a group are updated. |
+| GROUP_PERMISSION_DELETE | This event is recorded whenever a user group is deleted from an account. |
+| APP_GROUP_PERMISSION_UPDATE | For every app added in to user group, you can set privileges like `View` or `Edit` and whenever these privileges are updated this event is recorded. By default, the permission of an app for a user group is set to `View`. |
+
+### Understanding Log Information
+
+
+
+
+
+
+
+| Property | Description |
+| ----------- | ----------- |
+| action_type | This indicates the type of action that was logged in the event. Refer to [this](#select-actions) for more information on actions. |
+| created_at | Shows the date and time when the event was logged. |
+| id | Each logged event is assigned a unique event ID. |
+| ip_address | Displays the IP address from which the event was logged. |
+| metadata | The metadata includes two sub-properties: `tooljet_version` and `user_agent`. `tooljet_version` shows the version of ToolJet used for the event, while `user_agent` contains information about the device and browser used. |
+| organization_id | Every organization in ToolJet has a unique ID associated with it, which is recorded when an event occurs. |
+| resource_id | Different [resources](#select-resources) have their respective IDs associated with them. These IDs are assigned when the resources are created. |
+| resource_name | Shows the name of the [resources](#select-resources) that were involved in the logged event. For example, if an app was created or deleted, it will display the name of that app. |
+| resource_type | Indicates the type of the [resources](#select-resources) involved in the logged event. |
+| user_id | Each user account in ToolJet has a unique ID associated with it, which is recorded when an event occurs. |
+
+### Log file
+
+The file will contain all the data from audit logs. The log file can be created by specifying the path in the [environment variables](/docs/setup/env-vars). The log file is rotated on a daily basis and is updated dynamically every time a new audit log is generated.
+
+#### Log Rotation
+
+The log file is configured to rotate on a daily basis. This means that a new log file will be created every day, ensuring efficient management and organization of audit data.
+
+#### Log File Path
+
+The path for the log file is defined using the `LOG_FILE_PATH` variable in the environment. It's important to understand that this path is relative to the home directory of the machine. For instance, if `LOG_FILE_PATH` is set to `hsbc/dashboard/log`, the resulting log file path will be structured as follows:
+```
+homepath/hsbc/dashboard/log/tooljet_log/{process_id}-{date}/audit.log
+```
+Here, `{process_id}` is a placeholder for the unique process identifier, and `{date}` represents the current date. This structured path ensures that audit logs are organized by both process and date, facilitating easy traceability and analysis.
+
+| Variable | Description |
+| -------- | --------------------------------------------------------------------------- |
+| LOG_FILE_PATH | the path where the log file will be created ( eg: tooljet/log/tooljet-audit.log) |
+
+
+Example Log file data
+
+```bash
+{
+ level: 'info',
+ message: 'PERFORM APP_CREATE OF awdasdawdwd APP',
+ timestamp: '2023-11-02 17:12:40',
+ auditLog: {
+ userId: '0ad48e21-e7a2-4597-9568-c4535aedf687',
+ organizationId: 'cf8e132f-a68a-4c81-a0d4-3617b79e7b17',
+ resourceId: 'eac02f79-b8e2-495a-bffe-82633416c829',
+ resourceType: 'APP',
+ actionType: 'APP_CREATE',
+ resourceName: 'awdasdawdwd',
+ ipAddress: '::1',
+ metadata: {
+ userAgent: 'Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/118.0.0.0 Safari/537.36',
+ tooljetVersion: '2.22.2-ee2.8.3'
+ }
+ },
+ label: 'APP'
+}
+```
+
+
+
diff --git a/docs/versioned_docs/version-2.23.0/Enterprise/superadmin.md b/docs/versioned_docs/version-2.23.0/Enterprise/superadmin.md
new file mode 100644
index 0000000000..b8fe31f689
--- /dev/null
+++ b/docs/versioned_docs/version-2.23.0/Enterprise/superadmin.md
@@ -0,0 +1,158 @@
+---
+id: superadmin
+title: Super Admin
+---
+
+
Available on: Paid plans
+
+A Super Admin is the user who has full access to all the Workspaces, Users, and Groups of an instance. An instance can have more than one Super Admin. A Super Admin has full control over other users' workspaces and can create users, groups, and other super admins.
+
+The user details entered while setting up ToolJet will have Super Admin privileges.
+
+## How is Super Admin different from Admin
+
+| Privilege | Admin | Super Admin |
+| --------- | ----- | ----------- |
+| Manage Users in their workspace (Invite/Archive/Unarchive) | ✅ | ✅ |
+| Manage Groups in their workspace (Create Group/Add or Delete Users from groups/ Modify Group Permissions) | ✅ | ✅ |
+| Manage SSO in their workspace | ✅ | ✅ |
+| Manage Workspace Variables in their workspace | ✅ | ✅ |
+| Manage Workspace Constants in their workspace | ✅ | ✅ |
+| [Manage data sources for the user group in their workspace](/docs/data-sources/overview#permissions) | ✅ | ✅ |
+| [Access any user's personal workspace (create, edit or delete apps)](#access-any-workspace) | ❌ | ✅ |
+| [Archive Admin or any user of any workspace](#archiveunarchive-users) | ❌ | ✅ |
+| [Access any user's ToolJet database (create, edit or delete database)](#access-tooljet-db-in-any-workspace) | ❌ | ✅ |
+| [Manage any workspace's setting (Groups/SSO/Workspace constants)](#manage-workspace-setting-groupsssoworkspace-constants) | ❌ | ✅ |
+| [Manage all users from all the workspaces in the instance](#manage-all-users-in-the-instance) | ❌ | ✅ |
+| [Make any user Super Admin](#make-the-user-super-admin) | ❌ | ✅ |
+| [Restrict creation of personal workspace of users](#restrict-creation-of-personal-workspace-of-users) | ❌ | ✅ |
+| [Enable Multiplayer editing](#enable-multiplayer-editing) | ❌ | ✅ |
+| [Implement White Labelling](#white-labelling) | ❌ | ✅ |
+
+
+
+
+
+
+
+## Super Admin features
+
+### Access any workspace
+
+If a user has Super Admin privileges, they can switch to any workspace created by any user within the instance using the Workspace Switcher located in the bottom left corner of the screen.
+
+The dropdown will display all workspaces, including those created by both Super Admins and any other users.
+
+
+
+
+
+
+
+### Create, Edit or Delete apps from any user's personal workspace
+
+Once the Super Admin accesses the workspace of any other user, they can create, edit or delete app on the workspace.
+
+This also includes - modifying folders and importing, exporting, or cloning apps to any user's workspace.
+
+### Archive/Unarchive Users
+
+Super Admin can not only archive/unarchive users/admins on their workspace but also from the workspaces of any other user.
+
+If a user is Super Admin, they just need to open the workspace in which they want to archive or unarchive a user. Then go to the **Workspace Settings** from the sidebar -> **Manage Users** -> **Archive/Unarchive** any user/admin
+
+
+
+
+
+
+
+### Access ToolJet DB in any workspace
+
+Super Admins have access to the database of any user's workspace - just like Super Admins can access any application in any workspace. They have full access to modify or create any table in the ToolJet DB of any workspace.
+
+### Manage Workspace Settings (Groups/SSO/Workspace constants)
+
+Super Admins have all the privileges that an Admin of a workspace have, Super Admins can:
+- **✅ Manage Groups**: Creating/Deleting/Updating a Group in any workspace
+- **✅ Manage SSO**: Full control over General Settings, Password login and other SSO options
+- **✅ Workspace Variables**: Adding, updating or deleting workspace variables
+- **✅ Workspace Constants**: Adding, updating or deleting workspace constants
+- **✅ Copilot**: Enabling or disabling Copilot
+- **✅ Custom Styles**: Adding or modifying custom styles
+
+## Instance Settings
+
+Only Super Admins can access the Instance Settings:
+
+- **All Users**
+- **Manage Instance Settings**
+- **License**
+- **White labelling**
+
+## All Users
+
+### Manage all users in the instance
+
+**All Users** page can be used to check the list of all the users in the instance. Super Admins can also promote/demote any user to/from Super Admin from this page. They can also archive/unarchive any user from this page.
+
+
+
+
+
+
+
+### Archiving a user from workspace
+
+Super Admins have the privilege to remove any user from any workspace to which they belong.
+
+Super Admins can go to **All Users** page, Under the **Workspaces** column they'll see the number of workspaces a user belongs to. Click on the **`View(n)`**, a modal will pop up that will have the list of **`n`** number the workspaces, click on the **Archive/Unarchive** button next to the workspace name to remove the user from the workspace.
+
+
+
+
+
+
+
+### Make the user super admin
+
+Super Admins can make any user as Super Admin or remove any Super Admin from the **Manage All Users** in the Instance Settings page.
+
+Click on the **Edit** button next to any user, **Enable** the **Make the user Super Admin** option, and then **Save** it.
+
+The user will become Super Admin and the Type column will update from **`workspace`** to **`instance`**.
+
+
+
+
+
+
+
+## Manage Instance Settings
+
+
+
+
+
+
+
+### Restrict creation of personal workspace of users
+
+When a user joins a workspace, they are provided with their own personal workspace and option to create new workspaces.
+
+Super Admins can **control** this behavior from the Manage Instance Settings page, they can **toggle off** the option to **Allow personal workspace**. Now whenever a user joins a workspace they won't be provided a personal workspace nor they will be able to create a new workspace in the instance.
+
+### Enable multiplayer editing
+
+Super Admins can enable multiplayer editing from the Manage Instance Settings page. Once enabled, users will be able to edit the same app simultaneously resulting in real-time collaboration.
+
+## License
+
+Manage the instance license via the **Instance Settings** page. Super Admins have the capability to update the instance's license key from this page.
+
+Check out the [License](/docs/licensing) page for more details.
+
+## White labelling
+This feature allows you to customize the ToolJet instance with your own branding. You can change the logo, favicon, and the name of the instance.
+
+Check out the [White labelling](/docs/enterprise/white-label/) page for more details.
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.23.0/Enterprise/white-label.md b/docs/versioned_docs/version-2.23.0/Enterprise/white-label.md
new file mode 100644
index 0000000000..2f91cf349a
--- /dev/null
+++ b/docs/versioned_docs/version-2.23.0/Enterprise/white-label.md
@@ -0,0 +1,48 @@
+---
+id: white-label
+title: White Label
+---
+
+
Available on: Paid plans
+
+The White Label feature allows you to completely remove ToolJet's branding from the ToolJet platform, allowing you to replace it with your own customized logo, favicon and page title. This feature grants you full control over the visual identity of your ToolJet-powered application, ensuring a seamless and personalized user experience.
+
+With this feature, you gain the ability to rebrand the following key elements:
+
+- **Application Logo**: This includes the logo displayed on the login screen, dashboard, and app-editor.
+
+
+
+
+
+
+
+- **Favicon**: The small icon associated with your application.
+
+
+
+
+
+
+
+- **Page Title**: This is the text displayed next to the Favicon.
+
+
+
+
+
+
+
+## Configuration
+
+To enable white labelling, you'll need to go to the **Instance Settings** from the Dashboard and click on the `White labelling` tab. On the White labelling page, you'll be able to configure the following:
+
+- **Application Logo**: Add the URL of the image you want to use as your application logo. Preferred dimensions of the logo are: width `130px` and height `26px`.
+- **Favicon**: Enter the URL of the image you want to use as your application's favicon. Preferred dimensions of the favicon are: width `32px` and height `32px` or `16px` and height `16px`.
+- **Page Title**: Enter the text you want to display as your application's title. Preferred title length are 50-60 characters.
+
+
+
+
+
+
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.23.0/actions/_category_.json b/docs/versioned_docs/version-2.23.0/actions/_category_.json
new file mode 100644
index 0000000000..f5b2dfe045
--- /dev/null
+++ b/docs/versioned_docs/version-2.23.0/actions/_category_.json
@@ -0,0 +1,5 @@
+{
+ "label": "Actions Reference",
+ "position": 7,
+ "collapsed": true
+}
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.23.0/actions/close-modal.md b/docs/versioned_docs/version-2.23.0/actions/close-modal.md
new file mode 100644
index 0000000000..bb772142f9
--- /dev/null
+++ b/docs/versioned_docs/version-2.23.0/actions/close-modal.md
@@ -0,0 +1,19 @@
+---
+id: close-modal
+title: Close modal
+---
+
+Use this action to close the modal that is already shown.
+
+Debounce field is empty by default, you can enter a numerical value to specify the time in milliseconds after which the action will be performed. ex: `300`
+
+:::info
+You can also trigger actions from the **JavaScript code**. Check it out [here](/docs/how-to/run-actions-from-runjs).
+:::
+
+
+
+
+
+
+
diff --git a/docs/versioned_docs/version-2.23.0/actions/control-component.md b/docs/versioned_docs/version-2.23.0/actions/control-component.md
new file mode 100644
index 0000000000..61f653d21e
--- /dev/null
+++ b/docs/versioned_docs/version-2.23.0/actions/control-component.md
@@ -0,0 +1,102 @@
+---
+id: control-component
+title: Control component (Component Specific Actions)
+---
+
+Control component action invokes the component specific actions. Component specific actions are the actions that are exclusive actions for a particular component. Component specific actions can be triggered either through the event handlers or from the Run JavaScript code query.
+
+You can find the component specific actions for the specific component in their respective documentation. For example, you can find the component specific actions for the **Bounded Box** component in the [Bounded Box](/docs/widgets/bounded-box) documentation.
+
+
+ Currently, Component specific actions are supported only by the below listed components.
+
+
+
+:::info
+Check out the **[demo](https://youtu.be/JIhSH3YeM3E)** of Component specific actions demonstrated in one of our community call.
+:::
+
+## Using Component Specific Actions
+
+### Set a value for text input component using button's event handler
+
+- Drag a **Text Input** and a **Button** component onto the canvas.
+
+- Go to the **Inspector** on the left sidebar to check the exposed variables available for the `textinput1` component under the `components`. You'll see that the variable `value` is an empty string because the field value of the text input component is empty right now.
+
+
+
+
+
+
+
+- Now enter some value in the text input component and you'll see that the `value` in inspector has been updated.
+
+
+
+
+
+
+
+- Now, click on the button's component handler to open up its properties in the right sidebar and then add a event handler for **On Click** event to trigger **Control Component** action. Select `textinput1` in component dropdown, `Set text` as Action, and in `Text` field enter the text that you want to update in the field value.
+
+
+
+
+
+
+
+- Now when you'll click on the button you'll see that the field value of the text input component has been updated with value that you set.
+
+
+
+
+
+
+
+
+### Clear value of text input component using JavaScript query
+
+- Let's clear the value that we set in the previous section, using Run JavaScript code. Create a new Run JavaScript Code query and call the component and the CSA that component provides.
+
+**Syntax:**
+```js
+await components.textinput1.clear()
+```
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+- Finally, hit the **save and run** query button to fire up the query, and you'll see that the field value of the text input component has been cleared.
+
diff --git a/docs/versioned_docs/version-2.23.0/actions/copy-to-clipboard.md b/docs/versioned_docs/version-2.23.0/actions/copy-to-clipboard.md
new file mode 100644
index 0000000000..81f97c360e
--- /dev/null
+++ b/docs/versioned_docs/version-2.23.0/actions/copy-to-clipboard.md
@@ -0,0 +1,18 @@
+---
+id: copy-to-clipboard
+title: Copy to clipboard
+---
+
+Use this action to copy the text to the clipboard.
+
+Debounce field is empty by default, you can enter a numerical value to specify the time in milliseconds after which the action will be performed. ex: `300`
+
+:::info
+You can also trigger actions from the **JavaScript code**. Check it out [here](/docs/how-to/run-actions-from-runjs).
+:::
+
+
+
+
+
+
diff --git a/docs/versioned_docs/version-2.23.0/actions/generate-file.md b/docs/versioned_docs/version-2.23.0/actions/generate-file.md
new file mode 100644
index 0000000000..5e969b87a8
--- /dev/null
+++ b/docs/versioned_docs/version-2.23.0/actions/generate-file.md
@@ -0,0 +1,56 @@
+---
+id: generate-file
+title: Generate file
+---
+
+# Generate file
+
+This action allows you to construct files on the fly and let users download it.
+
+## Options
+
+| Option | Description |
+|--------|-------------|
+| Type | Type of file to be generated. Types: `CSV`, `Text` and `PDF` |
+| File name | Name of the file to be generated |
+| Data | Data that will be used to construct the file. Its format will depend on the file type, as specified in the following section |
+| Debounce | Debounce field is empty by default, you can enter a numerical value to specify the time in milliseconds after which the action will be performed. ex: `300` |
+
+:::tip
+Check how to run **[generate file action using RunJS](/docs/how-to/run-actions-from-runjs/#generate-file)**.
+:::
+
+### CSV Data Format
+
+To use the `CSV` file format, the data field should contain an array of objects. ToolJet assumes that the keys in each object are the same and represent the column headers of the CSV file.
+
+Example:
+
+```javascript
+{{
+ [
+ { name: 'John', email: 'john@tooljet.com' },
+ { name: 'Sarah', email: 'sarah@tooljet.com' },
+ ]
+}}
+```
+
+Using the above code snippet will generate a CSV file with the following content:
+
+```csv
+name,email
+John,john@tooljet.com
+Sarah,sarah@tooljet.com
+```
+
+### Text Data Format
+
+To use the `Text` file format, the data field should contain a string.
+
+If you want to generate a text file based on an array of objects, you need to stringify the data before providing it.
+
+For example, if you are using the table component to provide the data, you can enter **`{{JSON.stringify(components.table1.currentPageData)}}`** in the Data field.
+
+### PDF data format
+
+The PDF data format supports two types of input: either a `string` or an `array of objects`. When using an array of objects, the resulting PDF will display the data in a tabular format with columns and rows. On the other hand, if a string is provided, the generated PDF will consist of plain text.
diff --git a/docs/versioned_docs/version-2.23.0/actions/go-to-app.md b/docs/versioned_docs/version-2.23.0/actions/go-to-app.md
new file mode 100644
index 0000000000..02d15e6aef
--- /dev/null
+++ b/docs/versioned_docs/version-2.23.0/actions/go-to-app.md
@@ -0,0 +1,20 @@
+---
+id: go-to-app
+title: Go to app
+---
+
+This action allows you to open any ToolJet application when an event occurs.
+
+Debounce field is empty by default, you can enter a numerical value to specify the time in milliseconds after which the action will be performed. ex: `300`
+
+:::info
+You can also trigger actions from the **JavaScript code**. Check it out [here](/docs/how-to/run-actions-from-runjs).
+:::
+
+
+
+
+
+
+
+
diff --git a/docs/versioned_docs/version-2.23.0/actions/logout.md b/docs/versioned_docs/version-2.23.0/actions/logout.md
new file mode 100644
index 0000000000..0e3187471c
--- /dev/null
+++ b/docs/versioned_docs/version-2.23.0/actions/logout.md
@@ -0,0 +1,18 @@
+---
+id: logout
+title: Logout
+---
+
+This action allows you to log out of the application (ToolJet).
+
+Debounce field is empty by default, you can enter a numerical value to specify the time in milliseconds after which the action will be performed. ex: `300`
+
+:::info
+You can also trigger actions from the **JavaScript code**. Check it out [here](/docs/how-to/run-actions-from-runjs).
+:::
+
+
+
+
+
+
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.23.0/actions/open-webpage.md b/docs/versioned_docs/version-2.23.0/actions/open-webpage.md
new file mode 100644
index 0000000000..749b205eb9
--- /dev/null
+++ b/docs/versioned_docs/version-2.23.0/actions/open-webpage.md
@@ -0,0 +1,18 @@
+---
+id: open-webpage
+title: Open webpage
+---
+
+You can use this action to open a webpage(on a new tab) for any event.
+
+Debounce field is empty by default, you can enter a numerical value to specify the time in milliseconds after which the action will be performed. ex: `300`
+
+:::info
+You can also trigger actions from the **JavaScript code**. Check it out [here](/docs/how-to/run-actions-from-runjs).
+:::
+
+
+
+
+
+
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.23.0/actions/run-query.md b/docs/versioned_docs/version-2.23.0/actions/run-query.md
new file mode 100644
index 0000000000..55eb1f16aa
--- /dev/null
+++ b/docs/versioned_docs/version-2.23.0/actions/run-query.md
@@ -0,0 +1,18 @@
+---
+id: run-query
+title: Run Query
+---
+
+This action allows you to fire queries when an event occurs.
+
+Debounce field is empty by default, you can enter a numerical value to specify the time in milliseconds after which the action will be performed. ex: `300`
+
+:::info
+You can also trigger actions from the **JavaScript code**. Check it out [here](/docs/how-to/run-actions-from-runjs).
+:::
+
+
+
+
+
+
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.23.0/actions/set-localstorage.md b/docs/versioned_docs/version-2.23.0/actions/set-localstorage.md
new file mode 100644
index 0000000000..3dead574aa
--- /dev/null
+++ b/docs/versioned_docs/version-2.23.0/actions/set-localstorage.md
@@ -0,0 +1,59 @@
+---
+id: set-localstorage
+title: Set localStorage
+---
+
+# Set localStorage
+
+This action allows you to specify a `key` and its corresponding `value` to be stored in localStorage.
+
+## Example: App that stores a name in localStorage and displays it on reload
+
+1. Add an input field, button and a text as shown
+
+
+
+3. Select the text label we've added and set its value to the name item from localStorage.
+
+:::info
+Debounce field is empty by default, you can enter a numerical value to specify the time in milliseconds after which the action will be performed. ex: `300`
+:::
+
+
+
+
+4. Now save the application, this is important as we're about to reload the page.
+
+5. Type in anything you wish on the input box and click on the button
+
+
+
diff --git a/docs/versioned_docs/version-2.23.0/actions/set-page-var.md b/docs/versioned_docs/version-2.23.0/actions/set-page-var.md
new file mode 100644
index 0000000000..5c50bab3ee
--- /dev/null
+++ b/docs/versioned_docs/version-2.23.0/actions/set-page-var.md
@@ -0,0 +1,36 @@
+---
+id: set-page-variable
+title: Set page variable
+---
+
+Page variables are restricted to the page where they are created and cannot be accessed throughout the entire application like regular variables.
+
+Use this action to establish a variable and assign a value to it within the [Multipage Apps](/docs/tutorial/pages).
+
+By default, the debounce field is left empty. However, you can input a numeric value to indicate the time in milliseconds before the action is executed. For example, `300`.
+
+
+
+
+
+
+
+## Using RunJS query to set page variable
+
+Alternatively, the set page variable action can be triggered via a RunJS query using the following syntax:
+```js
+await actions.setPageVariable('',)
+```
+
+`variablekey` must be provided as a string (enclosed in quotes), while the `variablevalue` does not require quotation marks if it is a numerical value.
+
+
+
+
+
+
+
+:::info
+For instructions on how to run actions from a RunJS query, refer to the how-to guide [Running Actions from RunJS Query](/docs/how-to/run-actions-from-runjs).
+:::
+
diff --git a/docs/versioned_docs/version-2.23.0/actions/set-table-page.md b/docs/versioned_docs/version-2.23.0/actions/set-table-page.md
new file mode 100644
index 0000000000..6c6414650c
--- /dev/null
+++ b/docs/versioned_docs/version-2.23.0/actions/set-table-page.md
@@ -0,0 +1,24 @@
+---
+id: set-table-page
+title: Set Table Page
+---
+
+Use this action to change the page index in the table widget.
+
+## Options
+
+| Option | Description |
+|--------|-------------|
+| Table | Select table from the dropdown |
+| Page Index | Numerical value for the page index. ex: `{{2}}` |
+| Debounce | Debounce field is empty by default, you can enter a numerical value to specify the time in milliseconds after which the action will be performed. ex: `300` |
+
+:::info
+You can also trigger actions from the **JavaScript code**. Check it out [here](/docs/how-to/run-actions-from-runjs).
+:::
+
+
+
+
+
+
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.23.0/actions/set-variable.md b/docs/versioned_docs/version-2.23.0/actions/set-variable.md
new file mode 100644
index 0000000000..ef611d43ba
--- /dev/null
+++ b/docs/versioned_docs/version-2.23.0/actions/set-variable.md
@@ -0,0 +1,24 @@
+---
+id: set-variable
+title: Set variable
+---
+
+This action allows you to create a variable and assign a `value` to it.
+
+## Options
+
+| Option | Description |
+|--------|-------------|
+| Key | Name(String) of the variable through which you can access the value |
+| Value | A value can be a string, number, boolean expression, array, or object |
+| Debounce | Debounce field is empty by default, you can enter a numerical value to specify the time in milliseconds after which the action will be performed. ex: `300` |
+
+:::info
+You can also trigger actions from the **JavaScript code**. Check it out [here](/docs/how-to/run-actions-from-runjs).
+:::
+
+
+
+
+
+
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.23.0/actions/show-alert.md b/docs/versioned_docs/version-2.23.0/actions/show-alert.md
new file mode 100644
index 0000000000..f92ec12cd7
--- /dev/null
+++ b/docs/versioned_docs/version-2.23.0/actions/show-alert.md
@@ -0,0 +1,23 @@
+---
+id: show-alert
+title: Show alert
+---
+
+This action allows you to display an alert message.
+
+You can set a custom **message** for the alert and choose a particular alert type.
+
+There are 4 types of alert messages - **Info**, **Success**, **Warning**, and **Error**.
+
+Debounce field is empty by default, you can enter a numerical value to specify the time in milliseconds after which the action will be performed. ex: `300`
+
+:::info
+You can also trigger actions from the **JavaScript code**. Check it out [here](/docs/how-to/run-actions-from-runjs).
+:::
+
+
+
+
+
+
+
diff --git a/docs/versioned_docs/version-2.23.0/actions/show-modal.md b/docs/versioned_docs/version-2.23.0/actions/show-modal.md
new file mode 100644
index 0000000000..10f5d9ab17
--- /dev/null
+++ b/docs/versioned_docs/version-2.23.0/actions/show-modal.md
@@ -0,0 +1,18 @@
+---
+id: show-modal
+title: Show modal
+---
+
+Use this action to show the modal for an event.
+
+Debounce field is empty by default, you can enter a numerical value to specify the time in milliseconds after which the action will be performed. ex: `300`
+
+:::info
+You can also trigger actions from the **JavaScript code**. Check it out [here](/docs/how-to/run-actions-from-runjs).
+:::
+
+
+
+
+
+
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.23.0/actions/switch-page.md b/docs/versioned_docs/version-2.23.0/actions/switch-page.md
new file mode 100644
index 0000000000..2438fb45e7
--- /dev/null
+++ b/docs/versioned_docs/version-2.23.0/actions/switch-page.md
@@ -0,0 +1,55 @@
+---
+id: switch-page
+title: Switch Page
+---
+
+Utilize this action with various event handler to transition to a different page within the [Multipage App](/docs/tutorial/pages).
+
+By default, the debounce field is left empty. However, you can input a numeric value to indicate the time in milliseconds before the action is executed. For example, `300`.
+
+
+
+
+
+
+
+## Query Params
+
+Query parameters can be passed through action such as `Switch Page`. The parameters are appended to the end of the application URL and are preceded by a question mark (`?`).
+
+Query parameters are composed of key-value pairs, where the `key` and `value` are separated by an equals sign (`=`). Multiple query parameters can be included by clicking on the `+` button.
+
+
+
+
+
+
+
+In the above screenshot, we have provided the `username` as the key and the value is `{{globals.currentUser.email}}` which gets the email of the signed in user dynamically. When the button is clicked to trigger the `Switch Page` event handler attached to it then the URL on the switched page will have the parameters.
+
+They are commonly used to provide additional information to the server or to modify the behavior of a web page. They can be used for filtering search results, pagination, sorting, and various other purposes.
+
+
+
+
+
+
+
+## Using RunJS query to switch page
+
+Alternatively, the switch page action can be activated via a RunJS query using the following syntax:
+```js
+await actions.switchPage('')
+```
+
+:::info
+For instructions on how to run actions from a RunJS query, refer to the how-to guide [Running Actions from RunJS Query](/docs/how-to/run-actions-from-runjs).
+:::
+
+### Switch page with query params
+
+The switch page action can also be triggered along with query parameters using the following syntax:
+
+```js
+actions.switchPage('', [['param1', 'value1'], ['param2', 'value2']])
+```
diff --git a/docs/versioned_docs/version-2.23.0/actions/unset-page-var.md b/docs/versioned_docs/version-2.23.0/actions/unset-page-var.md
new file mode 100644
index 0000000000..933721c12d
--- /dev/null
+++ b/docs/versioned_docs/version-2.23.0/actions/unset-page-var.md
@@ -0,0 +1,27 @@
+---
+id: unset-page-variable
+title: Unset page variable
+---
+
+Utilize this action to clear a variable that was established using the [set page variable action](/docs/actions/set-page-variable).
+
+By default, the debounce field is left empty. However, you can input a numeric value to indicate the time in milliseconds before the action is executed. For example, `300`.
+
+
+
+
+
+
+
+## Using RunJS query to unset variable
+
+Alternatively, the unset page variable action can be triggered via a RunJS query using the following syntax:
+```js
+await actions.unsetPageVariable('')
+```
+
+`variablename` is the key of the variable that was provided while creating the variable.
+
+:::info
+For instructions on how to run actions from a RunJS query, refer to the how-to guide [Running Actions from RunJS Query](/docs/how-to/run-actions-from-runjs).
+:::
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.23.0/actions/unset-variable.md b/docs/versioned_docs/version-2.23.0/actions/unset-variable.md
new file mode 100644
index 0000000000..1e6b35f99f
--- /dev/null
+++ b/docs/versioned_docs/version-2.23.0/actions/unset-variable.md
@@ -0,0 +1,23 @@
+---
+id: unset-variable
+title: Unset variable
+---
+
+This action allows you to remove the variable variable that was created using the set variable action.
+
+## Options
+
+| Option | Description |
+|--------|-------------|
+| Key | Name(String) of the variable through which you can access the value |
+| Debounce | Debounce field is empty by default, you can enter a numerical value to specify the time in milliseconds after which the action will be performed. ex: `300` |
+
+:::info
+You can also trigger actions from the **JavaScript code**. Check it out [here](/docs/how-to/run-actions-from-runjs).
+:::
+
+
+
+
+
+
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.23.0/app-builder/canvas.md b/docs/versioned_docs/version-2.23.0/app-builder/canvas.md
new file mode 100644
index 0000000000..99d2a75318
--- /dev/null
+++ b/docs/versioned_docs/version-2.23.0/app-builder/canvas.md
@@ -0,0 +1,67 @@
+---
+id: canvas
+title: Canvas
+---
+
+Canvas is the center area of the ToolJet app builder where the application is built. You arrange the **components** by dragging them from the Components library(right-sidebar).
+
+
+
+
+
+
+
+
+:::info
+- The Canvas height and width can be adjusted from the [Global Settings](/docs/app-builder/left-sidebar#global-settings).
+- When the [Pages drawer](/docs/tutorial/pages) on the left is opened or pinned, the canvas becomes horizontally scrollable.
+
+
+
+
+
+
+:::
+
+### Arrange Components
+
+All the components are fully interactive in editor mode - to prevent interaction you can **click and hold** the **Component Handle** to change component's position.
+
+
+
+
+
+
+
+### Resize Components
+
+Components on the canvas can be resized from the edges.
+
+You can precisely set the position of selected components using keyboard arrow keys after clicking the component handle.
+
+
+
+
+
+
+
+### Group Components
+
+ToolJet comes with flexible components to group other components together, such as **[Container](/docs/widgets/container/)** and **[Form](/docs/widgets/form/)**. When you drag and drop components in containers/forms they create a group of nested components. All components can be nested in this way.
+
+### Hide or Disable Components
+
+Hide or Disable a component by setting its **Visibility** or **Disabled** property to `true`. Click on the component handle to open **config inspector** on right side. These values can also evaluate to true based on a truthy value. For example, you can use the property of one component to toggle the Visibility property of another component dynamically, you just need to write a conditional statement.
+
+For example: We want to disable a button when a checkbox is checked so we can simple use `{{components.checkbox1.value}}` in **Disable** property of the button. `{{components.checkbox1.value}}` evaluates to `true` when the checkbox is checked, and false when unchecked.
+
+
+
+
+
+
+
+### Clone Components
+
+You can clone existing components on the canvas by **cmd/ctrl + d**. Check other **[Keyboard Shortcuts](/docs/tutorial/keyboard-shortcuts)**.
+
diff --git a/docs/versioned_docs/version-2.23.0/app-builder/customcss.md b/docs/versioned_docs/version-2.23.0/app-builder/customcss.md
new file mode 100644
index 0000000000..870292c51e
--- /dev/null
+++ b/docs/versioned_docs/version-2.23.0/app-builder/customcss.md
@@ -0,0 +1,56 @@
+---
+id: customstyles
+title: Custom Styles
+---
+
+
Available on: Paid plans
+
+Custom Styles feature enables the implementation of theming on ToolJet apps, allowing users to inject their own CSS styling to override the default app styling. This feature fulfills the requirement of allowing users to easily customize the appearance of their apps.
+
+Custom Styles helps in maintaining consistent themes across the ToolJet apps, alleviating the repetitive burden of styling components whenever a new app is created. By enabling users to apply standardized styles, this feature ensures that each app adheres to a unified theme without the need to manually restyle the components from scratch. As a result, the ToolJet app development process becomes more efficient, and the visual coherence of the apps is preserved, providing users with a seamless experience across all applications.
+
+
+
+
+
+
+
+## Applying Custom Styles
+
+To add Custom Styles to ToolJet apps, users should follow these steps:
+
+1. Go to the **Custom Styles** Page, accessible under **Workspace Settings** from the ToolJet dashboard.
+
+
+
+
+
+
+2. When creating a new app on ToolJet, the default button color is **blue**. If you wish to change the default button color to **red**, you must identify the class of the button component, which follows the format `_tooljet-`.
+ - The browser's inspector can also help you find the class of the component. Classes are added for both **pages** and **components**, and there are two types of selectors for classes: **Common** (`_tooljet-`) and **Individual** (`_tooljet-`).
+
+
+
+
+
+
+3. Once the class (**`_tooljet-Button`**) is identified, navigate to the Custom Styles page and apply the desired CSS changes for that class, as shown in the following CSS code:
+ ```css
+ ._tooljet-Button button {
+ background: red !important;
+ }
+ ._tooljet-Button button:hover {
+ background: green !important;
+ }
+ ```
+
+4. By applying this custom styles, all future instances of the app will have buttons with a red default color, and they will turn green on hover. This eliminates the need for users to individually edit button properties, streamlining the customization process.
+ :::info
+ Custom Styles are injected at the workspace level, ensuring consistent theming across all apps within the workspace.
+ :::
+
+
+
+
+
+
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.23.0/app-builder/left-sidebar.md b/docs/versioned_docs/version-2.23.0/app-builder/left-sidebar.md
new file mode 100644
index 0000000000..54a2f0a8ad
--- /dev/null
+++ b/docs/versioned_docs/version-2.23.0/app-builder/left-sidebar.md
@@ -0,0 +1,101 @@
+---
+id: left-sidebar
+title: Left-sidebar
+---
+
+Left-sidebar has the following options:
+
+- **[Pages](#pages)**
+- **[Inspector](#inspector)**
+- **[Debugger](#debugger)**
+- **[Global Settings](#global-settings)**
+- **[Comments](#comments)**
+- **[Theme switch](#theme-switch)**
+
+
+
+
+
+
+
+## Pages
+
+Pages allows you to have multiple pages in a single application, making your ToolJet applications more robust and user-friendly.
+
+Check the detailed documentation for **[Pages](/docs/tutorial/pages)**.
+
+
+
+
+
+
+
+## Inspector
+
+The Inspector can be used to inspect the data of the **queries**, properties and values of the **components** that are there on the canvas, ToolJet's global variables and the variables that have been set by the user.
+
+Check the detailed guide on **[using Inspector](/docs/how-to/use-inspector)**.
+
+
+
+
+
+
+
+## Debugger
+
+Debugger records any errors that occur during the execution of queries. For instance, if a database query fails because the database is unavailable or if a REST API query fails due to an incorrect URL, the errors will be captured and shown in the debugger. Additionally, the debugger provides pertinent information associated with the error alongside the error message.
+
+If you wish to prevent the debugger from closing, you can simply click on the pin icon located in the top-right corner. By doing so, the debugger will stay open until you decide to unpin it.
+
+Debugger consists of two main sections:
+
+1. **All Log:** In this section, you can view a comprehensive list of all the logs generated during the execution of the application. These logs may include various types of messages, such as success messages, warning, and error messages.
+
+2. **Errors:** This section specifically focuses on displaying the error messages that occurred during the program's execution. These error messages indicate issues or problems that need attention, as they may lead to unexpected behaviors of the application.
+
+
+
+
+
+
+
+## Global Settings
+
+To configure the app's global settings, click on the kebab menu(three vertical dots) on the left of the app name. Global settings include:
+
+- **Unique app slug**: The unique slug of the application. This slug is used in the URL of the application. By default, the slug is the `app id` of the application. You can change the slug to a custom value. For example, if the slug is `7b56293b-be5a-401f-8806-b71625f8ee0d` you can change it to `` then the new URL of the application will be `https://app.tooljet.com//apps//`
+- **App link**: The link to the application. This link can be used to share the application with other users of the workspace. If you want to share the application with users outside the workspace, you can make the application public from the **[Share](/docs/app-builder/share)** modal.
+- **Hide header for launched apps**: Toggle this on to the hide the tooljet's header when the applications are launched
+- **Maintenance mode**: Toggle this on to put the application in maintenance mode. When in **maintenance mode**, on launching the app, the user will get an error message that **the app is under maintenance**.
+- **Max width of canvas**: Modify the width of the canvas in **px** or **%**. The default width is `1292` px.
+- **Background color of canvas**: Enter the hex color code or choose a color from the picker to change the background color of the canvas. You can also click on the **Fx** to programmatically set the value.
+- **Export app**: Click on the [Export app](/docs/dashboard/#export-app) button to export the application as a JSON file. You can import this JSON file in any other workspace to use the application.
+
+
+
+
+
+
+
+## Comments
+
+Comment anywhere on the canvas and collaborate with other users in the workspace. Click on the comments button to enable it and then drop comment anywhere on the canvas.
+
+
+
+
+
+
+
+## Theme Switch
+
+Use the theme switch button to toggle ToolJet between light and dark modes.
+
+While developers can access the current theme's value through global variables using `{{globals.theme.name}}`, it is not currently feasible to change the theme programmatically.
+
+
+
+
+
+
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.23.0/app-builder/overview.md b/docs/versioned_docs/version-2.23.0/app-builder/overview.md
new file mode 100644
index 0000000000..2fb73cfed2
--- /dev/null
+++ b/docs/versioned_docs/version-2.23.0/app-builder/overview.md
@@ -0,0 +1,20 @@
+---
+id: overview
+title: Overview
+---
+
+# App-Builder: Overview
+
+ToolJet's App Builder allows you to build applications. ToolJet's app builder has the following major components:
+
+- **[Topbar](/docs/app-builder/topbar)**: configure app settings
+- **[Canvas](/docs/app-builder/canvas)**: Arrange the components to build the interface of app
+- **[Left-sidebar](/docs/app-builder/left-sidebar)**: Add **[pages](/docs/tutorial/pages)**, **[inspect](/docs/how-to/use-inspector)** the components, queries or variables, and **[debug](#debugger)** the errors.
+- **[Components library](/docs/app-builder/components-library)**(right sidebar): Drag any component or modify the property or styling
+- **[Query Panel](/docs/app-builder/query-panel)**: Create, edit or manage the queries from the **[datasources](/docs/data-sources/overview)**
+
+
+
+
+
+
diff --git a/docs/versioned_docs/version-2.23.0/app-builder/query-panel.md b/docs/versioned_docs/version-2.23.0/app-builder/query-panel.md
new file mode 100644
index 0000000000..d21714e855
--- /dev/null
+++ b/docs/versioned_docs/version-2.23.0/app-builder/query-panel.md
@@ -0,0 +1,218 @@
+---
+id: query-panel
+title: Query Panel
+---
+
+The Query Panel, located at the bottom of the app-builder, allows you to create and manage queries for interacting with connected **Default** and **Global** datasources. It provides the capability to perform API requests, query **[databases](/docs/data-sources/overview)**, and apply **[transformations](/docs/tutorial/transformations)** or data manipulation using **[JavaScript](/docs/data-sources/run-js)** and **[Python](/docs/data-sources/run-py)**.
+
+The Query Panel consists of two sections:
+- The **[Query Manager](#query-manager)** on the right side, which displays a list of all the created queries.
+- The **[Query Editor](#query-editor)**, used to configure the selected query.
+
+
+
+
+
+
+
+## Query Manager
+
+Query Manager will list all the queries that has been created in the application. Query Manager helps in managing the queries that have been created, you can **add**, **edit**, **delete**, **duplicate**, **search**, **sort** and **filter** through them.
+
+
+
+
+
+
+
+### Add
+
+Add button is used to add new query in the application. When Add button is clicked, a menu will open with a list of options for creating a query from **Default** datasources such as **Rest API**, **ToolJet Database**, **JavaScript Code**, **Python Code** or from connected **Global Datasources**.
+
+
+
+
+
+
+
+### Sort/Filter
+
+On the top of Query Manager, there is button to Sort or Filter queries. The following options are there:
+
+**Filter:**
+- By Datasource
+
+**Sort:**
+- Name: A-Z
+- Name: Z-A
+- Type: A-Z
+- Type: Z-A
+- Last modified: oldest first
+- Last modified: newest First
+
+
+
+
+
+
+
+### Search
+
+On the top of the query manager is search box that can be used to search for a specific query.
+
+
+
+
+
+
+
+### Delete
+
+Delete button will delete the selected query, the button will only show up when you hover over the query name. When you click on the delete button, a confirmation dialog will open to confirm the deletion of the query.
+
+
+
+
+
+
+
+### Duplicate
+
+Duplicate button will duplicate the selected query, the button will only show up when you hover over the query name. The duplicate query will be named as `_copy`.
+
+
+
+
+
+
+
+### Rename
+
+Rename button is used to rename the selected query, the button will only show up when you hover over the query name. When you click on the rename button, the query name becomes editable and you can change the name of the query.
+
+
+
+
+
+
+
+## Query Editor
+
+Query editor used to configure the query parameters, preview or transform the data return by the query.
+
+:::info
+The changes made in the query panel will be saved automatically.
+:::
+
+
+
+
+
+
+
+### Topbar
+
+On the top of the query panel there are a few options:
+
+#### Query Name
+
+The name of query is displayed on the top of the query panel. You can click on it to make it editable and change the name of the query.
+
+
+
+
+
+
+
+#### Preview
+
+Preview button is used to preview the data returned by the query. The data will be displayed on the preview section present at the bottom of the query panel. This helps in debugging the query and see the data returned by the query without triggering the query in the app.
+
+The Preview of data is returned in two different formats: **Raw** & **JSON**. You can click on the clear button to clear the preview data.
+
+
+
+
+
+
+
+#### Run
+
+Run is used to trigger the query, running the query will interact with the application unlike `Preview`.
+
+
+
+
+
+
+
+### Query Parameters
+
+Query Parameters are essential values that must be provided in a query for the server to generate a response. These parameters encompass **endpoints**, **methods**, or **operations**. It's important to note that the specific set of Query Parameters varies for each datasource.
+
+
+
+
+
+
+
+#### Datasource
+
+The primary and default parameter found in all queries is **Datasource**. This option allows you to choose the appropriate datasource for your query.
+
+In cases where multiple datasources of the same type are connected, you can easily switch the query's datasource using the dropdown menu.
+
+
+
+
+
+
+
+### Transformation
+
+Transformations can be enabled on queries to transform the query results. ToolJet allows you to transform the query results using two programming languages JavaScript & Python. Check the detailed documentation on **[Transformations](/docs/tutorial/transformations)**.
+
+
+
+
+
+
+
+### Settings
+
+
+
+
+
+
+
+#### Run this query on application load?
+
+Enabling this option will execute the query every time the app is loaded.
+
+#### Request confirmation before running the query?
+
+Enabling this option show a confirmation modal to confirm `Yes` or `No` if you want to fire that query.
+
+#### Show notification on success?
+
+Enabling this option show a success toast notification when the query is successfully triggered.
+
+You can provide a custom **success message** and **notification duration** in milliseconds.
+
+### Events
+
+Event handlers can be added to queries for the following events:
+
+- **Query Success**
+- **Query Failure**
+
+:::info
+Learn more about [Event Handlers and Actions](/docs/widgets/overview#component-event-handlers).
+:::
+
+
+
+
+
+
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.23.0/app-builder/right-sidebar.md b/docs/versioned_docs/version-2.23.0/app-builder/right-sidebar.md
new file mode 100644
index 0000000000..88faa89314
--- /dev/null
+++ b/docs/versioned_docs/version-2.23.0/app-builder/right-sidebar.md
@@ -0,0 +1,29 @@
+---
+id: components-library
+title: Components Library
+---
+
+The **Components Library** on the right sidebar contains all of the available components. Use this to drag-and-drop a component from the library to the canvas. It organizes components into sections and you can enter a search term to quickly find a component you need.
+
+
+
+
+
+
+
+:::tip
+Check the **[Components Catalog](/docs/widgets/overview)** to know more about specific component.
+:::
+
+## Component Config Inspector
+
+The Component Config Inspector is also called as component inspector. It contains all the available settings for the selected component and is where you **set values**, **update component names**, and **create event handlers**. The Component Inspector organizes settings into different sections, such as **Property** and **Styles**.
+
+To open the Component Config Inspector, click on the **[component handle](/docs/app-builder/canvas#arrange-components)** that is present on the top of the component including **⚙️ + Component Name** and the component inspector will open up on the right side:
+
+
+
+
+
+
+
diff --git a/docs/versioned_docs/version-2.23.0/app-builder/share.md b/docs/versioned_docs/version-2.23.0/app-builder/share.md
new file mode 100644
index 0000000000..0c9dbddd09
--- /dev/null
+++ b/docs/versioned_docs/version-2.23.0/app-builder/share.md
@@ -0,0 +1,52 @@
+---
+id: share
+title: Share
+---
+
+ToolJet apps offer two sharing options: they can either be shared privately with workspace users or publicly by generating a shareable link. To obtain the shareable URL, you can easily do so by clicking on the Share button located on the top bar of the App builder.
+
+
+
+
+
+
+
+### Making the app public
+
+To share the app with external end users and make it accessible to anyone on the internet without requiring a ToolJet login, you can toggle on the Switch for "Make the application public?" in the Share modal.
+
+
+
+
+
+
+
+### Customizing the app URL
+
+By default, ToolJet will generate a unique URL for your application. However, you also have the option to edit the slug of the URL to make it more customized and user-friendly.
+
+
+
+
+
+
+
+### Embedding ToolJet Apps
+
+ToolJet apps can be directly shared with end users and embedded into web apps using `iframes`. If you want to make your application public, you can use the Share modal to obtain the embeddable link.
+
+:::info
+For embedding private ToolJet apps, you'll need to set an environment variable in the `.env` file.
+
+| Variable | Description |
+|:-------------- |:------------------------------------ |
+| ENABLE_PRIVATE_APP_EMBED | `true` or `false` |
+
+You can learn more [here](/docs/setup/env-vars#enabling-embedding-of-private-apps).
+:::
+
+
+
+
+
+
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.23.0/app-builder/toolbar.md b/docs/versioned_docs/version-2.23.0/app-builder/toolbar.md
new file mode 100644
index 0000000000..c5e3b41372
--- /dev/null
+++ b/docs/versioned_docs/version-2.23.0/app-builder/toolbar.md
@@ -0,0 +1,135 @@
+---
+id: topbar
+title: Topbar
+---
+
+Topbar is present at the top of the app-builder, and is used to configure the app settings.
+
+
+
+
+
+
+
+### App name
+
+The App name can be modified by selecting the application name located on the left side of the topbar.
+
+Upon the creation of a new app, it is automatically assigned a unique app name.
+
+
+
+
+
+
+
+### Desktop or Mobile layout
+
+Switch the canvas mode in Mobile or Desktop layout from the topbar.
+
+#### Showing component on mobile layout
+
+Click on the component handle to open [component config inspector](/docs/app-builder/components-library#component-config-inspector) on the right sidebar. Scroll down to the **Layout** section and toggle on the Mobile Layout option. The width of the components will be adjusted to fit the Mobile Layout.
+
+#### Adding a new component to mobile layout
+
+Switch the canvas to mobile layout by clicking the mobile icon on the topbar. Drag and drop a new component to the canvas. This component will not be visible on the desktop layout unless **Show on desktop** is enabled from the component config inspector.
+
+:::info
+Width of the component will be automatically adjusted to fit the screen while viewing the application in app viewer.
+:::
+
+
+
+
+
+
+
+### Changes saved indicator
+
+Whenever a change is made on the component or the query panel/queries, the changes are saved automatically. The changes saved indicator will be displayed on the topbar. This helps the developer to know if the changes are saved or not.
+
+
+
+
+
+
+
+### Developer Details
+
+This will show a profile picture of the developer who is currently working on the application. Hovering over the profile picture will show the name of the developer. If there is no profile picture, then the first letter of the first name and last name will be displayed.
+
+
+
+
+
+
+
+### Version Manager
+
+**Add** or **remove** versions of an application from the Version Manager. Click on the `edit` icon next to version name to rename the version.
+
+When many developers are working on an app, **Versioning** allows them to save their own version of the app. This also prevents developers from overwriting the other developer's work.
+
+:::tip
+Versioning is also helpful when working with **[multiple environments](/docs/release-management/multi-environment/)** like development, staging and production.
+:::
+
+
+
+
+
+
+
+### Undo or Redo
+
+Undo or Redo any action performed on the canvas.
+
+You can also use **[Keyboard Shortcuts](/docs/tutorial/keyboard-shortcuts)** to perform such actions.
+
+
+
+
+
+
+
+### Share
+
+Share your applications with a unique URL generated automatically or edit the URL slug to personalize it.
+
+- When **Make the application public** is off and URL is shared then the users will have to login to ToolJet to use the application. Toggle on the option then anyone on the internet will be able to access the application without logging in to ToolJet.
+- ToolJet generates the **Embedded link** which can be used to embed application on the webpages.
+
+:::tip
+Learn more about **[Sharing](/docs/app-builder/share)** your tooljet applications.
+:::
+
+
+
+
+
+
+
+### Preview
+
+Clicking on **Preview** button will open up the currently opened version of the app in the new tab. This is really handy when the app developer wants to immediately check the app preview in production.
+
+
+
+
+
+
+
+### Release
+
+Release the app to publish the current version of the app and push the changes into the production.
+
+:::caution
+ToolJet will block editing of the Released version of an app and will display a prompt to create a new version to make the changes. This is to prevent accidentally pushing an unfinished app to the live version.
+:::
+
+
+
+
+
+
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.23.0/contributing-guide/_category_.json b/docs/versioned_docs/version-2.23.0/contributing-guide/_category_.json
new file mode 100644
index 0000000000..317067020d
--- /dev/null
+++ b/docs/versioned_docs/version-2.23.0/contributing-guide/_category_.json
@@ -0,0 +1,5 @@
+{
+ "label": "Contributing Guide",
+ "position": 11,
+ "collapsed": true
+}
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.23.0/contributing-guide/code-of-conduct.md b/docs/versioned_docs/version-2.23.0/contributing-guide/code-of-conduct.md
new file mode 100644
index 0000000000..03f7184d51
--- /dev/null
+++ b/docs/versioned_docs/version-2.23.0/contributing-guide/code-of-conduct.md
@@ -0,0 +1,81 @@
+---
+id: code-of-conduct
+title: Contributor Code of Conduct
+---
+
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to make participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, sex characteristics, gender identity and expression,
+level of experience, education, socio-economic status, nationality, personal
+appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+ advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+ address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+ professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies within all project spaces, and it also applies when
+an individual is representing the project or its community in public spaces.
+Examples of representing a project or community include using an official
+project e-mail address, posting via an official social media account, or acting
+as an appointed representative at an online or offline event. Representation of
+a project may be further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at hello@tooljet.com . All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see
+https://www.contributor-covenant.org/faq
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.23.0/contributing-guide/l10n.md b/docs/versioned_docs/version-2.23.0/contributing-guide/l10n.md
new file mode 100644
index 0000000000..196a10aba2
--- /dev/null
+++ b/docs/versioned_docs/version-2.23.0/contributing-guide/l10n.md
@@ -0,0 +1,69 @@
+---
+id: l10n
+title: Localization
+---
+
+Welcome to ToolJet Localization Guide. The goal of the Localization is to make ToolJet easy to use and close to all countries, languages, and general cultural groups. On this page, you will find instructions on how to contribute to ToolJet through Localization and make a more friendly ToolJet for all regions.
+
+## Adding Translations
+
+- For adding the translations of your language in ToolJet, you'll need to create a new **languagecode.json** file which will include all the translations for the keywords in your language, and then list the language in the **languages.json** file for the language to be listed in the dashboard of the ToolJet.
+
+- Go to the **frontend** directory which is at the root of ToolJet, then go to the **assets** and inside assets, you'll find the **translations** directory. You have created a new json file with the **language code** as the file name. The language code should follow [ISO 639-1 Code](https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes).
+
+ ```
+ \frontend
+ |--\assets
+ |--\--\translations
+ |--\--\--\languages.json
+ |--\--\--\en.json
+ ```
+
+
+
+
+
+
+
+- Let's localize ToolJet in the **French** language. Create a new json file inside the translations directory and name it **fr.json**. `fr` is the language code for French.
+
+- After creating the new file, open the **en.json** file and copy all the contents of the file to the newly created **fr.json**.
+
+
+
+
+
+
+
+- Once copied, you can now start adding the translations for the keywords in the french language.
+
+- After completing the translation, all you need to do is list the language in **languages.json** file. You'll need to add an object with three key-value pairs. **lang** - the name of the language that you added, **code** - the language code, and the **nativeLang** - name of language in the native.
+
+ ```js
+ {
+ "languageList":
+ [
+ { "lang": "English", "code": "en", "nativeLang": "English" },
+ { "lang": "French", "code": "fr", "nativeLang": "Français" }
+ ]
+ }
+ ```
+
+
+
+:::note
+Feel free to reach us on [Slack](https://tooljet.com/slack) for any help related to Localization.
+:::
\ No newline at end of file
diff --git a/docs/versioned_docs/version-2.23.0/contributing-guide/marketplace/creating-a-plugin.md b/docs/versioned_docs/version-2.23.0/contributing-guide/marketplace/creating-a-plugin.md
new file mode 100644
index 0000000000..6cadb88d7e
--- /dev/null
+++ b/docs/versioned_docs/version-2.23.0/contributing-guide/marketplace/creating-a-plugin.md
@@ -0,0 +1,390 @@
+---
+id: creating-a-plugin
+title: 'Marketplace: Creating plugins'
+---
+
+# Marketplace: Creating plugins
+
+## What are plugins
+
+ToolJet’s development has centered on extensibility, allowing developers to utilize plugins that expand their capabilities. Currently, these plugins are limited to connectors, including data source connectors like PostgreSQL, MySQL, Twilio, Stripe, and more. Using JavaScript/TypeScript, developers can develop plugins to enhance ToolJet's functionality and publish these plugins on the ToolJet Marketplace.
+
+This guide will provide step-by-step instructions for creating ToolJet plugins using the `tooljet` CLI.
+
+The `tooljet` CLI is a user-friendly command-line tool designed to simplify the plugin building process. As part of this guide, we will create a basic plugin for GitHub.
+
+## Step 1: Creating a New Plugin - GitHub Plugin
+
+The first step is to bootstrap a new plugin for the ToolJet marketplace. The plugin will authenticate users with a GitHub Personal Access Token and include fundamental operations such as fetching user details, repositories, issues, and pull requests.
+
+If you have completed the **[Setup](/docs/contributing-guide/marketplace/marketplace-setup)** guide, you can begin developing the plugin using the `tooljet` CLI. To initiate plugin development, enter the following command in the terminal:
+```bash
+# create a new plugin
+tooljet plugin create github
+```
+
+When prompted, enter the **plugin name** and select the **plugin type**, which is api in this case. Additionally, select **yes** when prompted to create a new plugin for the marketplace.
+
+If your plugin is hosted on GitHub, please provide the **repository URL** when prompted. Otherwise, leave it blank.
+
+When a plugin is created using the `ToolJet` CLI, an object is added to the **plugins.json** file in the **`ToolJet/server/src/assets/marketplace/`** directory. This object includes metadata about the plugin, such as its name, description, version, author, and other relevant details.
+
+The plugins.json file serves as a registry of all available plugins for use in ToolJet. When the ToolJet server starts up, it reads the plugins.json file and loads all plugins that are listed in it.
+
+:::info
+It is important to note that the plugins.json file should not be manually edited, as it is automatically generated by the `ToolJet CLI`. Making changes to this file can result in issues with the proper functioning of the plugins in the system.
+:::
+
+All marketplace plugins are stored in the **`/marketplace`** directory of the ToolJet repository. You can find the GitHub plugin **[here](https://github.com/ToolJet/ToolJet/tree/develop/marketplace/plugins/github)**.
+
+The structure of a typical ToolJet plugin directory appears as follows:
+```bash
+github/
+ package.json
+ lib/
+ icon.svg
+ index.ts
+ operations.json
+ manifest.json
+```
+
+In this structure, the file **manifest.json** contains information about the plugin's name, description, and other details. The file **operations.json** contains metadata about all the operations that the plugin supports. The main file, **index.ts**, creates a QueryService for the plugin, which handles queries, connection testing, caching, and more. The **icon.svg** file serves as the plugin's icon, while **package.json** is automatically generated by the CLI.
+
+:::info
+**Why do we need a manifest.json file or a operations.json file?**
+
+The manifest.json file is used by a React component to create a dynamic UI for connection forms. It defines the schema of an API or data source, including its name, type, and any exposed variables, as well as options for authentication and other customizable properties. The properties section specifies the required fields and their types for connecting to the API or data source. By reading the manifest.json file, the React component generates the necessary UI components based on the schema, such as text inputs, dropdowns, checkboxes, and other elements.
+
+On the other hand, the operations.json file contains a schema definition for a specific data source, like Github. It describes the available operations and their parameters that can be used to query the data source. A React component uses this schema to create queries in ToolJet applications, generating a UI that allows users to select the desired operation and provide the required parameters. The component uses the properties defined in the operations.json file to create various UI elements, such as dropdowns and input fields, and handle user interactions to create the final query. Once the user fills in the required parameters, the component uses them to generate a query that can be executed against the data source and return the results to the user.
+
+Overall, *manifest.json* and *operations.json* files are essential for creating dynamic UI components in ToolJet applications. They define the schema for data sources and available operations, which React components then use to generate user-friendly UI elements. By utilizing these files, ToolJet enables users to easily connect to various APIs and data sources, perform queries, and retrieve data in an intuitive and efficient manner.
+:::
+
+## Step 2: Defining the manifest.json file
+
+To construct the connection form, it's important to include the necessary options in the manifest.json file. Here's an example of how to do it:
+```json
+ "properties": {
+ "credentials": {
+ "label": "Authentication",
+ "key": "auth_type",
+ "type": "dropdown-component-flip",
+ "description": "A single select dropdown to choose credentials",
+ "list": [
+ {
+ "value": "personal_access_token",
+ "name": "Use Personal Access Token"
+ }
+ ]
+ },
+ "personal_access_token": {
+ "token": {
+ "label": "Token",
+ "key": "personal_token",
+ "type": "password",
+ "description": "Enter your personal access token",
+ "hint": "You can generate a personal access token from your Github account settings."
+ }
+ }
+ }
+```
+This manifest.json file includes information about authentication options, specifically a dropdown to choose a type of credentials and a field to enter a personal access token. The label, key, type, description, and hint properties are used to define the specific fields and their types required for connecting to the API or data source.
+
+In this particular code, there are two main properties defined: **`credentials`** and **`personal_access_token`**.
+
+The **`credentials`** property specifies the authentication method to be used. It contains several keys:
+- **`label`**: a user-friendly label for the authentication method, set to "Authentication"
+- **`key`**: a unique identifier for the authentication method, set to "auth_type"
+- **`type`**: the type of the authentication method, set to "dropdown-component-flip"
+- **`description`**: a description of the authentication method, set to "A single select dropdown to choose credentials"
+- **`list`**: an array of objects representing the different authentication methods available. In this case, there is only one method available: a personal access token. The `value` key in the object is set to "personal_access_token" and the `name` key is set to "Use Personal Access Token".
+
+The **`personal_access_token`** property specifies the details of the personal access token authentication method. It contains a `token` key, which specifies the actual personal access token to be used. The `token` key contains several keys:
+- **`label`**: a user-friendly label for the personal access token, set to "Token"
+- **`key`**: a unique identifier for the personal access token, set to "personal_token"
+- **`type`**: the type of the personal access token, set to "password"
+- **`description`**: a description of the personal access token, set to "Enter your personal access token"
+- **`hint`**: a hint for the personal access token, set to "You can generate a personal access token from your Github account settings."
+
+The available `type` options are:
+
+However, based on the code you provided, the available **`type`** options are:
+- **`password`**: used to input a secret value, such as a password or an access token.
+- **`dropdown-component-flip`**: used to create a dropdown menu that flips its position relative to the component that triggers it.
+- **`text`**: used to input a single line of text.
+- **`textarea`**: used to input multiple lines of text.
+- **`toggle`**: used to create a simple on/off switch.
+- **`react-component-headers`**: used to display headers for React components.
+- **`codehinter`**: is a specialized input field used for entering code and has additional functionality, such as resolving JavaScript code within double curly braces`{{}}`.
+
+:::tip
+The **manifest.json** file is utilized by the connection modal component, which appears to prompt users to enter their datasource credentials. Meanwhile, the **operations.json** file is used by the query manager when users generate a specific query for a connected datasource. **Both files utilize a similar schema**.
+:::
+
+## Step 3: Defining the operations.json file
+```json
+ "properties": {
+ "operation": {
+ "label": "Operation",
+ "key": "operation",
+ "type": "dropdown-component-flip",
+ "description": "Single select dropdown for operation",
+ "list": [
+ {
+ "value": "get_user_info",
+ "name": "Get user info"
+ },
+ {
+ "value": "get_repo",
+ "name": "Get repository"
+ },
+ {
+ "value": "get_repo_issues",
+ "name": "Get repository issues"
+ },
+ {
+ "value": "get_repo_pull_requests",
+ "name": "Get repository pull requests"
+ }
+ ]
+ },
+ "get_user_info": {
+ "username": {
+ "label": "Username",
+ "key": "username",
+ "type": "codehinter",
+ "lineNumbers": false,
+ "description": "Enter username",
+ "width": "320px",
+ "height": "36px",
+ "className": "codehinter-plugins",
+ "placeholder": "Enter username"
+ }
+ },
+ "get_repo": {
+ "owner": {
+ "label": "Owner",
+ "key": "owner",
+ "type": "codehinter",
+ "lineNumbers": false,
+ "description": "Enter owner name",
+ "width": "320px",
+ "height": "36px",
+ "className": "codehinter-plugins",
+ "placeholder": "developer"
+ },
+ "repo": {
+ "label": "Repository",
+ "key": "repo",
+ "type": "codehinter",
+ "lineNumbers": false,
+ "description": "Enter repository name",
+ "width": "320px",
+ "height": "36px",
+ "className": "codehinter-plugins",
+ "placeholder": "tooljet"
+ }
+ },
+ "get_repo_issues": {
+ "owner": {
+ "label": "Owner",
+ "key": "owner",
+ "type": "codehinter",
+ "lineNumbers": false,
+ "description": "Enter owner name",
+ "width": "320px",
+ "height": "36px",
+ "className": "codehinter-plugins",
+ "placeholder": "developer"
+ },
+ "repo": {
+ "label": "Repository",
+ "key": "repo",
+ "type": "codehinter",
+ "lineNumbers": false,
+ "description": "Enter repository name",
+ "width": "320px",
+ "height": "36px",
+ "className": "codehinter-plugins",
+ "placeholder": "tooljet"
+ },
+ "state": {
+ "label": "State",
+ "key": "state",
+ "className": "codehinter-plugins col-4",
+ "type": "dropdown",
+ "description": "Single select dropdown for choosing state",
+ "list": [
+ {
+ "value": "open",
+ "name": "Open"
+ },
+ {
+ "value": "closed",
+ "name": "Closed"
+ },
+ {
+ "value": "all",
+ "name": "All"
+ }
+ ]
+ }
+ },
+ "get_repo_pull_requests": {
+ "owner": {
+ "label": "Owner",
+ "key": "owner",
+ "type": "codehinter",
+ "lineNumbers": false,
+ "description": "Enter owner name",
+ "width": "320px",
+ "height": "36px",
+ "className": "codehinter-plugins",
+ "placeholder": "developer"
+ },
+ "repo": {
+ "label": "Repository",
+ "key": "repo",
+ "type": "codehinter",
+ "lineNumbers": false,
+ "description": "Enter repository name",
+ "width": "320px",
+ "height": "36px",
+ "className": "codehinter-plugins",
+ "placeholder": "tooljet"
+ },
+ "state": {
+ "label": "State",
+ "key": "state",
+ "type": "dropdown",
+ "className": "codehinter-plugins col-4",
+ "description": "Single select dropdown for choosing state",
+ "list": [
+ {
+ "value": "open",
+ "name": "Open"
+ },
+ {
+ "value": "closed",
+ "name": "Closed"
+ },
+ {
+ "value": "all",
+ "name": "All"
+ }
+ ]
+ }
+ }
+ }
+```
+The operations.json file specifies the available operations that can be executed on the data source. It provides details about the operation type, required fields to execute the operation, and the data type of each field. The label, key, type, description, and hint properties are used to define the specific fields and their types required to establish a connection with the API or data source.
+
+## Step 4: Add the npm package of Gitub to the plugin dependencies
+
+- Change directory to the plugin directory where the npm package needs to be installed and then install the package
+ ```bash
+ # change directory to the plugin directory and install the npm package
+ npm i octokit --workspace=@tooljet-marketplace/github
+ ```
+
+ :::info
+ Steps to install npm package to a plugin
+
+ ```bash
+ npm i --workspace=
+ ```
+
+ The command `npm i --workspace=` is used to install a specific npm package into a particular workspace of a multi-package repository.
+
+ The *--workspace* flag is used to specify the workspace where the package should be installed. In this case, we are installing the package in the *@tooljet-marketplace/github* workspace.
+ :::
+
+## Step 5: Implement the query execution logic in index.ts
+
+In index.ts, the query execution logic needs to be implemented for the Github plugin's QueryService. The QueryService is responsible for handling the process of running queries and receives information about the data source, including credentials, configurations, and query parameters.
+
+For the Github data source, the sourceOptions will contain the necessary authentication credentials, like the personal access token, while the queryOptions will include the configurations and parameters specific to the query, like obtaining a list of repositories for a particular user.
+
+Using this information, the QueryService will create and execute API requests against the Github API. The resulting data will be returned to the caller for further processing as needed.
+
+Create a new file **query_operations.ts** in the **plugins/github/src** directory and add the following code to it.
+```typescript
+import { Octokit } from 'octokit'
+import { QueryOptions } from './types'
+
+
+export async function getUserInfo(octokit: Octokit, options: QueryOptions): Promise
+ 
-
-
-
-
-
-
-
-
-
-
+
+Make sure to replace username, password, cluster, and database with your actual MongoDB details. If your MongoDB instance requires additional connection options, you can usually append these options to the connection string.
+
+
## Querying MongoDB
Click on `+` button of the query manager at the bottom panel of the editor and select the database added in the previous step as the data source. Select the operation that you want to perform and click 'Save' to save the query.
diff --git a/docs/docs/data-sources/restapi.md b/docs/docs/data-sources/restapi.md
index ab4cbc3194..179dfbd11b 100644
--- a/docs/docs/data-sources/restapi.md
+++ b/docs/docs/data-sources/restapi.md
@@ -1,6 +1,6 @@
---
id: restapi
-title: REST API
+title: REST API
---
ToolJet can establish a connection with any available REST API endpoint and create queries to interact with it.
@@ -61,11 +61,32 @@ ToolJet supports the REST HTTP methods **GET**, **POST**, **PUT**, **PATCH**, an
+
+
+
+
+
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ 
+
+ 
+
+ 
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ 
+
+