We have customized a form that I do NOT want users to save their own layouts. I have disabled the menu and context menu, but they are using hot keys for saving layouts. Is there a way to stop them from associating a hot key with Save Layouts?
Why not a BPM that actually blocks the personalization from saving? Personalizations are saved in Ice.XXDef and Ice.XXChunk.
2 Likes
I’d be a little weary of a bpm blocking system related items. Since this is a single application, you could remove the save layouts from the toolbar *which you have done. Hot key setup in a customization? I’ve never done that I can play around and see if I stumble on something.
4 Likes
Personalization records are stored per user, app and form. “Form” meaning each customization. So you can tailor them very narrowly. We’re also talking about a basic “allow/block new row” logic. It’s not like we’re trying to manipulate the blob field. Risk is minimal.
I’ve never had to push a BPM on this into production. I have dabbled in it.
2 Likes
I having a feeling I am over-thinking this. Since the hot keys are by form, I can just disable the options menu for that form and be done. No point in making it more complicated than I need to.
2 Likes