I just updated client application so that nodes without parent objects in infrastructure tree are not shown as root level objects. This change will be part of release 5.0.3.
Best regards,
Victor

Thanks Victor, look forward to it.

@filipp-sudanov said in new desktop client - unbound nodes in infrastructure outside the folder tree:

Not sure why this is happening. Can you run the script I've shared manually (via Execute Script from context menu) on a couple of nodes which we bound to that container, but should not and share the output.

Hi Filip, attached is a screenshot of executing the script on a node that had an existing parent.  It always seems to return true whether on a node that has no other parent or an existing node.

Best regards,
Victor

Currently you can have "Unbound stuff" container somewhere with this auto-bind script, it will pick objects that are not present in any other containers:

for(p : $object.parents) {
  println(classof(p));
  if ((classof(p) == "Container") and p.id != $container.id) return false;
}
return true;

Thanks Filipp.  

I tried this script however it seems to pickup and autobind all nodes over time, not just those nodes outside the infrastructure services tree with no parent container.  

eg: attached an example of it filtered down to some APs that are already in parent containers and still trigger the autobind event.

Currently you can have "Unbound stuff" container somewhere with this auto-bind script, it will pick objects that are not present in any other containers:

for(p : $object.parents) {
  println(classof(p));
  if ((classof(p) == "Container") and p.id != $container.id) return false;
}
return true;