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
10 months agoJames
10 months agoTrinidad
10 months agoNobuko
9 months agoMireya
9 months agoQuentin
10 months agoCarisa
10 months agoYesenia
10 months agoGeorgeanna
11 months agoCammy
10 months agoKenneth
10 months agoQueenie
10 months agoStephaine
10 months agoTiara
11 months agoVivan
11 months agoJoaquin
10 months agoGlory
11 months agoJospeh
12 months agoGeoffrey
12 months agoThaddeus
12 months agoLashunda
1 years agoDaren
1 years agoIzetta
1 years agoJade
11 months agoDelfina
11 months agoAhmed
1 years agoDaron
1 years agoArlette
1 years agoRyan
1 years ago