Any smart way to hide or remove the navigation menu from Sites (top right corner, next to user profile pic)
This menu is hidden when the user has access to only one site.
It is only shown when user has access to more than one site, thereby allowing to view all accessible sites.
Our requirement is to hide/remove the menu ALWAYS for all users with access to one or more Sites.
Verified https://community.appian.com/discussions/f/user-interface/10178/removing-the-menu-and-drop-list-of-forms-from-the-top-right-hand-side-of-the-header-bar but no resolution provided.
Thanks & Regards,
This can't be done since it is the only way to route the user from multiple sites or the tempo from the sites. You can submit a request to Appian so that they might be marked this as enhancement for the feature releases.
If you don't like the icon, you could show the Site Name instead. Just choose the option for "Show site name on navigation bar" in the site designer. Then, it will show the site name in place of the icon.
That being said, the Site Name still has a dropdown menu you can use to navigate to other sites. It isn't removable because otherwise there would be no way to discover any other sites you had access to!
How did the people drafting that requirement expect users to be able to get to the other sites without it?
Just for devil's advocate, I've seen some projects where all users land on a universalized landing page (at one particular site) which then has links to the other applications they have access to, each one being a safelink to a different site.
Thanks David for the question. As mentioned by Mike, we are using a universalized landing page (at one particular site) which then has links to the other applications they have access to, each one being a safelink to a different site.
Thank you Shanmukha, planning to raise it as an enhancement request.
Absolutely right Mike, and that is how our project is designed as well. We have a landing page which has safelinks to other sites.
OK, crazy thought here, but one possibility to achieve the intended functionality is to not implement any of the other "sites" as sites themselves, but as other processes not attached to a site that the user can begin with a!startProcessLink.
The user won't be directed to a different site, they'll be directed to a process that executes completely, including all forms underneath, as part of the first site they are on. If you need users to start at that process within a different site, you can duplicate the PM and make a site-based version and non-site version of the same PM.
Otherwise, it's actually less work to do it this way. You configure the startprocess links instead of site links, and then just don't go through the effort of connecting your PMs to a site.
* If you need the navigation tabs when the users get to the new "site", you'll either have to implement them using something else like a sideBySide layout of cards, or buttons, or a milestone etc. or you would have to abandon this approach.
Discussion posts and replies are publicly visible
© 2019 Appian. All rights reserved.