Appreciate if anyone can give a clue why child nodes do not expand automatically when navigating to a Aurena tree page from another Aurena screen.
Select one or more records in Aurena page A and call action ‘Show Details’.
Then Aurena tree page B load but the child nodes do not automatically expand.
Thanks!
best regards,
Lakmalee.
Best answer by Mikko K.
Hi,
my guess is that @Lakmalee refers to a scenario where, for example
a number of records in a list are chosen (Picture 1) and navigation to another page is initiated
then after navigation to the page, which utilizes the tree control, the records are visualized in the record selector on the header level only (Picture 2) Picture 1Picture 2
Then to view the actual tree control nodes per record, one must expand them individually.
I would assume one reason to not visualize the tree control nodes as already expanded is that the record selector would likely look unusable if there are records with a large number of nodes in their trees.
Imagine you have only 2 records but both have trees with large numbers of nodes and sub nodes: would it be feasible to automatically expand all nodes visible to the user for both records?
The user would have a lot of information exposed to them, most of which they would likely not need at that time, so the more feasible way is to first show the number of records in total and then it’s up to the user to choose which tree, and which nodes, to expand.
In Picture 3 I have 1 Assortment record as fully expanded, but there’s so many layers of nodes that they do not even all fit into the screen at once.
my guess is that @Lakmalee refers to a scenario where, for example
a number of records in a list are chosen (Picture 1) and navigation to another page is initiated
then after navigation to the page, which utilizes the tree control, the records are visualized in the record selector on the header level only (Picture 2) Picture 1Picture 2
Then to view the actual tree control nodes per record, one must expand them individually.
I would assume one reason to not visualize the tree control nodes as already expanded is that the record selector would likely look unusable if there are records with a large number of nodes in their trees.
Imagine you have only 2 records but both have trees with large numbers of nodes and sub nodes: would it be feasible to automatically expand all nodes visible to the user for both records?
The user would have a lot of information exposed to them, most of which they would likely not need at that time, so the more feasible way is to first show the number of records in total and then it’s up to the user to choose which tree, and which nodes, to expand.
In Picture 3 I have 1 Assortment record as fully expanded, but there’s so many layers of nodes that they do not even all fit into the screen at once.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.