Security

Navigation Menu Default.xml Default View Cascading for Permission Restricted View

Explorer

What is the expected behavior for setting multiple default views in the default.xml navigation menu?

<nav search_view="search">
    <collection label="DefaultViews">
        <view name="permission_restricted_d1" default='true' />
        <view name="unrestricted_d2" default='true' />
 </collection>

The documentation has a case where multiple defaults are set in the same app and collection implying some sort of expected behavior.

In practice, restricting a users access to permisson_restricted_d1 causes a 404 error and does not cascade to unrestricted_d2.

Is this a known issue and/or is there a workaround available that would not involve creating a new app with alternate navigation to the same resources?

0 Karma