Hmm, I'm not so sure about option A. While the automatic updates are nice, I've seen some declarative customizations break when Salesforce makes changes. I think B and D are the safest bets here.
Agreed, Ahmed. I think options B and A are the way to go. Declarative customizations may be more maintainable, but I wouldn't say they're immune to errors. That's just wishful thinking.
Haha, 'can't generate runtime errors'? That's gold! I'd love to see the developer who can create a 100% error-proof customization. I'm going with B and D as the best options.
I'm not convinced that declarative customizations can't generate runtime errors. That seems a bit too good to be true. I think option B is the strongest answer here.
I agree with Ryan. Declarative customizations are definitely more low-maintenance, and the fact that they automatically update is a huge plus. I'm not sure about the test class generation though - that seems a bit far-fetched.
Hmm, this is an interesting question. I think the key benefits of using declarative customizations over code are the reduced maintenance and the automatic updates with each Salesforce release. What do you all think?
upvoted 0 times
...
Log in to Pass4Success
Sign in:
Report Comment
Is the comment made by USERNAME spam or abusive?
Commenting
In order to participate in the comments you need to be logged-in.
You can sign-up or
login
Buddy
5 months agoJames
5 months agoTrinidad
5 months agoNobuko
4 months agoMireya
5 months agoQuentin
6 months agoCarisa
5 months agoYesenia
5 months agoGeorgeanna
6 months agoCammy
5 months agoKenneth
5 months agoQueenie
5 months agoStephaine
6 months agoTiara
6 months agoVivan
7 months agoJoaquin
6 months agoGlory
6 months agoJospeh
7 months agoGeoffrey
7 months agoThaddeus
7 months agoLashunda
7 months agoDaren
8 months agoIzetta
8 months agoJade
6 months agoDelfina
7 months agoAhmed
8 months agoDaron
8 months agoArlette
8 months agoRyan
8 months ago