PLAT-ADMN-202 practice question 33 of 35

The Recruiting ream at AW Computing captures thejob acceptance and date of hire of a candidate on the Job Application custom object. Once the candidate accepts the recruiter s job offer, the date of hire should be entered and not be changed on subsequent cecord edit. Which validation formula should the app builder use?

Full set: 311 questions

Domain Productivity and Collaboration

Answer options
A: NOT(ISCLANK(Job_Accepted_c)) && ISCHANGED(Hire_Date_c) Correct answer
B: (ISBLANK(Job_Accepted_c) II NOT(lSCMANGED(Mire_Daie_c))
C: NOT{IS&lANK(Job_Accepted_c)) II ISCHANGED(Hire_Date_c)
D: (lSBLANK(Job_Accepted_c) && NOT(lSCHANGED(Hire_Date_c))
Correct Answer:
A. NOT(ISCLANK(Job_Accepted_c)) && ISCHANGED(Hire_Date_c)
Explanation

The requirement is to prevent the HireDatec from being changed once a candidate's job acceptance is recorded. A validation rule triggers an error if its formula evaluates to TRUE. The formula NOT(ISBLANK(JobAcceptedc)) && ISCHANGED(HireDatec) correctly implements this logic. NOT(ISBLANK(JobAcceptedc)): This part evaluates to TRUE if the JobAcceptedc field has any value, indicating the job offer has been accepted. ISCHANGED(HireDatec): This part evaluates to TRUE if the HireDatec field is being modified during the current record edit. && (AND): This logical operator ensures the rule only fires when both conditions are met, fulfilling the requirement to lock the hire date only after acceptance.

Why Incorrect

B. (ISBLANK(JobAcceptedc) || NOT(ISCHANGED(HireDatec))): The OR (||) logic is incorrect. This rule would incorrectly prevent saving a record if the job is not yet accepted OR if the hire date is not being changed.
C. NOT(ISBLANK(JobAcceptedc)) || ISCHANGED(HireDatec): The OR (||) operator is too broad. It would prevent saving any record that is marked as accepted, which is not the desired behavior.
D. (ISBLANK(JobAcceptedc) && NOT(ISCHANGED(HireDatec))): This logic is incorrect as it would fire when a job is not accepted and the hire date is not being changed, which is unrelated to the business requirement.

References

1. Salesforce Help Documentation, "Formula Operators and Functions":

ISCHANGED(field): "Compares the value of a field to the previous value and returns TRUE if the values are different. If the values are the same, this function returns FALSE." This function is essential for detecting the modification attempt.

ISBLANK(expression): "Determines if an expression has a value and returns TRUE if it does not. If it contains a value, this function returns FALSE." Used with NOT() to confirm the acceptance field is populated.

&& (AND): "Returns a TRUE response if all values are true; returns a FALSE response if one or more values are false." This operator is crucial for ensuring both conditions must be met.

2. Salesforce Help Documentation, "Examples of Validation Rules": The principle is demonstrated in similar examples, such as preventing changes to a closed opportunity. A common pattern is to check if a status field has a certain value (ISPICKVAL(StageName, "Closed Won")) AND another field is being changed (ISCHANGED(Amount)). The question uses NOT(ISBLANK()) as the status check, but the logical structure (Condition1 && Condition2) is identical.

Scroll to Top