Cute Trick #4: Navigation Flows Spring Cleaning – Users vs. Administrators

Say you’re working on a Planning Cloud project and you’ve created a custom navigation flow with your own clusters and cards. At some point the home page starts looking a little cluttered, or you may hit the cluster / card visibility limit and need to hide some things.

Or maybe you want to hide as many buttons as you can so you can keep your users focused when they log in to do their forecast, but you, as an admin, still want to see all the things.

Hyperbole and a Half: This is Why I’ll Never be an Adult

The quickest solution is to have two navigation flows: a decluttered one for your users, and the original, fully loaded one for everyone else (aka yourself). This is how you do it.

Select your custom flow, and from the gear, create a copy:

Your new navigation flow will show up on the list as Inactive. Flows can only be edited while inactive, so go ahead and edit it to hide all the cards you don’t want your users to see.

Good candidates for hiding?

  • OOTB clusters / cards for anything you might not be using in your project: Are you using Infolets? Dashboards? Reports?
  • Anything you don’t want your users to access directly: Do you want your users to access forms only from your custom clusters? Hide the Data card. Are all your business rules run-on-save from forms, and you don’t want your users to execute them directly? Hide your Rules card.

Lastly, use the Assign to field at the top of the screen to assign the newly decluttered flow to your user group / role.

Flows can only be assigned to one group or role at a time, so hopefully you have all your users under one group or role umbrella (assuming you want them all to see the same thing. If not you can repeat these steps, but beware of having to maintain too many flows!)

Save and Close your new flow and make it Active. You will now have two custom active flows, one for users, one for everyone else. If everyone else is only your admins, your “cluttered”, everyone else flow is now your admin flow. DONE!

You can add an extra level of safety by making your “cluttered” -now admin- custom flow strictly for admins. This way, anybody that is mistakenly set up as neither doesn’t see anything they don’t need to see. Inactivate your original custom flow, edit it and make it admin only. Remember to activate when done. You will end up with this (update your descriptions to match!).

Now all your admins will land in the original custom flow, your users will see the cleaned up flow when they log in, and anybody that is wrongly set up will see the OOTB flow (which, if your users know what they are supposed to see, should promptly trigger a support call!). You could even take this a step further and create a bare bones flow for those in limbo, as opposed to using the OOTB Default flow!

Leave a Reply

Your email address will not be published. Required fields are marked *