A developer needs to prevent the creation of Request _c records when certain conditions exist in the system. A BequestLogic class exists that checks the conditions.
Oh, this is a classic case of 'prevent and protect.' I'd go with option A, but I'm also partial to option C. Decisions, decisions... Maybe I should just flip a coin and hope for the best?
Hmm, this one's tricky. I'm leaning towards option B, but I better double-check the logic to be sure. Don't want any bugs sneaking in, or I'll be the one doing the bequest, if you know what I mean.
Option C looks like the correct implementation. The BequestLogic class checks the conditions, and this option seems to handle the prevention of Request_c records accordingly.
Scarlet
27 days agoCathrine
15 days agoFlorinda
1 months agoMinna
1 months agoJina
12 days agoVincent
2 months agoAaron
6 days agoAliza
11 days agoDarrel
20 days agoBritt
1 months agoElina
2 months agoAnnice
2 months agoElina
2 months ago