Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.
For more information and upcoming events around #dominoforever, please visit our Destination Domino Page
Sensitive info should be protected using Reader fields or Reader sections.
I never liked having the back door: View/Ctrl-Shift-Goto. I am always concerned that users will stumble on that and get access to info they shouldn't have - payroll views for example.
That would be very useful for some of the apps I have used where all agents are normally kept hidden and we can run them from designer client of course but then to have a method of running them on a user workstation to perform some fix, or inside an application could be good. The View / Goto for hidden views function is incredibly useful when debugging an app on a user machine.
Maybe having a free-for-all access to all hidden agents might be a bit too far, but what i thought there should be myself which might work similarly is to allow Agents to drop into defined sub-menus on the Actions menu like Action bar entries do, e.g.
Agent for Sales to use
> Hidden Agents
Where any hidden agents appear in a sub folder when you do Control Shift or if Designer or Manager in ACL say so less likely to be fiddled with by users.
As I'm sure you do, we find apps with little fixes issued to users increasingly desperately named to get themselves to the actual menu list "A1. Some fix", "000. Some more important fix" etc. and end up growing over the years and taking over the Actions menu. Showing hidden agents or allowing categorising of actions in the menu would help tidy that be organised.
Otherwise resort to a wrapper agent which is visible to users, send them a button to run an agent or notes:// url should work too I guess.
Illogical and inconsequent IMHO.
All the power is given to the devleoper, so if he descides the agent is not supposed to be visible to users, then it should stay like that.