Open sfmskywalker opened 3 months ago
To implement the solution described in the problem statement, you would need to follow these steps:
Create a New API Endpoint:
parentId
as an input parameter.Modify the Backend Logic:
parentId
.Update the UI for Lazy Loading:
Optimize Data Handling:
Test the Solution:
By following these steps, you can achieve the benefits of reduced initial load time, improved performance, and scalable data handling for complex workflow graphs in the UI.
This comment was generated by Glime.
The Problem
The current UI retrieves and loads the entire workflow graph from the server, which leads to:
The Solution
New API Endpoint
parentId
: Identifies the parent node for which child nodes are to be fetched.parentId
.UI Modifications
Benefits
Notes
The solution addresses performance issues related to sub-workflows (workflows as activities) and other complex activities like "ForEach" and "Container". It ensures efficient and scalable graph handling, regardless of the specific workflow structure or component type.