Feature/agentflow v2

[HenryHengZJ]

https://flowiseai.notion.site/Agentflow-V2-1606dbc4d9ec804e91abf94c0b948371

[AsharibAli]

amazing work @HenryHengZJ 🫡❤️

[chungyau97]

Description

Test the behavior of the executionId column in chatMessage during export and import across different test scenarios.

Test Environment

• [x] SQLite
• [x] PostgreSQL
• [x] MySQL
• [x] MariaDB

Test Data

all.json only Executions.json only Agentflows V2.json only Agentflows V2 chat data.json

Test Scenarios

Note: The database should be deleted before running each test scenario.

1. Duplicate Import Test

   Expectation: Each executionId should have a different ID (no duplication)

   Import all.json twice to verify that the system correctly handles duplicate IDs during the import process.

2. Only Agentflows V2

   Expectation: executionId should not be null

   Import the following files in order:

   • only Executions.json
   • only Agentflows V2.json
   • only Agentflows V2 chat data.json
   • only Agentflows V2 chat data.json

3. No Executions Data in JSON and Database

   Expectation: executionId should be null

   Import the following files in order:

   • only Agentflows V2.json
   • only Agentflows V2 chat data.json

[chungyau97]

Description

Test that export import of execution data works cross-platform across different database systems.

Test Environment

• [x] SQLite
• [x] PostgreSQL
• [x] MySQL
• [x] MariaDB

Test Data

mariadb execution null true false.json mysql execution null true false.json postgres execution null true false.json sqlite execution null true false.json

Test steps

1. Import all test data into Flowise runing SQLite

2. Import all test data into Flowise runing PostgreSQL

3. Import all test data into Flowise runing MySQL

4. Import all test data into Flowise runing MariaDB