Hello,
Idea for the following Tabs (Only An Example)
- Relationship
- Managed Items
- Where Used
It might be worth incorporating pagination here and only load [25, 50, 100] items at time I have been just running some tests as I am curious to understand maximum capacity off how long tab's take to load...and obviously once you start loading a lot of relationships it takes way too long to load.
But also it's worth noting that when too many relationships are created finding them becomes that much harder, so my suggestion is the following:
- Pagination To Show Only [25, 50, 100] Records At a Time, (Default to 25 For Maximum Performance).
- Filter Button Either On Each Column or a Button At The Top Where You Can Specify Search Criteria For Example, Item Descriptor ,Workspace or even Current State.
This would allow the solution to be much more scale-able, and also you would be adding additional filters to the V3 API to be able to extract relationships based on filtered criteria, therefore causing less of a resource burden on your servers pulling everything down when it's not required.
Happy To Discuss Further
Thanks,
Ashley
@lee.dodds1
