Details
-
Type:
Problem report
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 4.2.1
-
Fix Version/s: 4.0.11rc1, 4.2.5rc1, 4.4.0alpha1, 4.4 (plan)
-
Component/s: Frontend (F)
-
Labels:
-
Team:Team B
-
Sprint:Sprint 52 (May 2019), Sprint 53 (Jun 2019), Sprint 54 (Jul 2019)
-
Story Points:1
Description
Here is the illustration of map navigation tree in three levels:
1ST_LEVEL_MAP
trigger_count | map | group name | groupid
---------------+-------------------------+-------------+---------
21 | 1ST_LEVEL_MAP | TEST/10_AAA | 43
3994 | 1ST_LEVEL_MAP | TEST/02_BBB | 37
1 | 1ST_LEVEL_MAP | TEST/03_CCC | 41
2ND_LEVEL_MAP
trigger_count | map | group name | groupid
---------------+---------------+---------------------+---------
3843 | 2ND_LEVEL_MAP | TEST/02_BBB/GR1 | 39
15 | 2ND_LEVEL_MAP | TEST/02_BBB/SDC | 40
3RD_LEVEL_MAP
trigger_count | map | group name | groupid
---------------+--------------------------+-----------------------------+---------
35879 | 3RD_LEVEL_MAP | ANOTHER GROUP | 47
3843 | 3RD_LEVEL_MAP | TEST/02_BBB/GR1 | 39
Here is a sample configuration how the element type gets represented in the map:
The problem is that for such trigger count
21 + 3994 + 1 + 3843 + 15 + 35879 + 3843
The widget is not able to load.
