Skip to Content
0
Oct 11, 2019 at 11:29 AM

Hybris Backoffice editor-tree visibility

205 Views

I've been trying to migrate old hmc configs on to backoffice and ran into an issue with visibility of nodes on the explorer tree. Essentially, I was finding that some navigation-node elements were not being rendered in the left-hand nav, even though the user (admin) should be able to see them and they were merged to the correct nodes. After some trial and error I found a config that we are loading;

<context component="explorer-tree" principal="admin,globallinkrole" merge-by="module">
  <n:explorer-tree xmlns:n="http://www.hybris.com/cockpitng/config/explorertree" >
    <n:dynamic-node id="cng_globallink" populator-bean-id="globalLinkMenuPopulator" />
  </n:explorer-tree>
</context>

Removing the principal attribute allows the other nodes to be viewed, but I'm not sure why I need to do this. Shouldn't this be applying the admin/globallink access to this node only? If I add another config subsequently, like so

<context merge-by="module" parent="auto" component="explorer-tree">
    <explorer-tree xmlns="http://www.hybris.com/cockpitng/config/explorertree">
        <navigation-node id="hmc.payment">
            <type-node code="SomeType" id="SomeType"/>
        </navigation-node>
    </explorer-tree>
</context>

I believe I should be able to view this in the explorer tree section without having to have the globallinkrole, but that doesn't seem to be the case. Is there some guidance on the proper usage for the principal attribute?