An App Builder at UVC would like to prevent users from creating new records on an Account related list by overriding standard buttons. Which two should the App Builder consider before overriding standard buttons?
I feel like we practiced a question similar to this, and I recall that relocating and relabeling buttons is possible, but I can't remember the details.
I'm pretty confident on this one. The key is to look for the options that mention overriding standard buttons, which are B and D. I think those are the two correct answers.
Okay, I've got this. The two things the App Builder should consider are that standard buttons can be overridden with a Visualforce page (option B) and that standard buttons can be overridden, relocated on the detail page, and relabeled (option D).
Hmm, I'm a bit unsure about this one. I know we can override standard buttons, but I'm not sure about the specific details. I'll need to think this through carefully.
I also think option D) Standard buttons can be overridden, relocated on the detail page, and relabeled could be a good choice. It gives more flexibility in customizing the user experience.
I agree with Ettie. Overriding standard buttons with a Visualforce page seems like the best option to prevent users from creating new records on an Account related list.
Overriding standard buttons? Sounds like a job for a superhero app builder! B and D are my picks, but I hope they have a strong caffeine addiction to power through this.
Edwin
4 months agoNathalie
4 months agoJules
5 months agoKizzy
5 months agoDeane
5 months agoSamuel
5 months agoJames
5 months agoRolland
6 months agoHana
6 months agoWinfred
6 months agoGlory
6 months agoCharlene
6 months agoChauncey
7 months agoJanessa
12 months agoJames
12 months agoKirk
1 year agoAdolph
11 months agoSerina
11 months agoCharlena
11 months agoFletcher
11 months agoShalon
1 year agoArlyne
1 year agoBuffy
11 months agoGracie
12 months agoEttie
1 year agoGregg
1 year agoDerick
1 year ago