DreamHouse Realty (DR) asks for some improvements in case management. They want to enforce process compliance so that cases are unable to be reverted…

Validation rules are the ideal declarative solution for this scenario. They can enforce complex business logic without code. To prevent a case status from reverting, a validation rule can use the PRIORVALUE() function to compare the field's previous value with the new one. To make fields conditionally required, a validation rule formula can check for specific criteria (e.g., ISPICKVAL(Status, "Closed")) and then ensure another field is not blank (e.g., ISBLANK(ResolutionNotesc)). This directly addresses both of the stated requirements in a single, efficient feature.

B. Create dependent picklist fields and set them as required.

This only controls the available values of one picklist based on another and cannot prevent status reversion or enforce requirements on non-picklist fields.

C. Use an approval process to check field criteria are met.

Approval processes are for formal record submission and locking, not for enforcing data integrity rules during routine editing across the entire case lifecycle.

D. Make the fields required on the page layout.

This makes a field universally required for all records using that layout, failing to meet the requirement for fields to be required only when specific criteria are met.

---

1. Salesforce Help Documentation, "Validation Rules":

Content: "Validation rules verify that the data a user enters in a record meets the standards you specify before the user can save the record... For example, you can have a validation rule that requires a user to enter a justification if they change an opportunity's amount by more than 10%." This supports the principle of conditional field requirements.

Reference: Salesforce Help, Article ID 000328373, "Validation Rules".

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

Content: The PRIORVALUE(field) function is explicitly defined: "Use this function to compare a field’s value to its previous value." This is the specific mechanism required to prevent a case status from reverting to an earlier stage.

Reference: Salesforce Help, Article ID 000323229, "Formula Operators and Functions P–Z", Section: PRIORVALUE.

3. Salesforce Help Documentation, "Examples of Validation Rules":

Content: This document provides multiple examples that directly map to the requirements. For instance, the section "Enforcing a value in a field based on the value of another field" shows how to make a field required conditionally. The logic can be adapted to prevent status reversion, such as CASE(Status, "New",1,"Working",2,"Closed",3,0) < CASE(PRIORVALUE(Status), "New",1,"Working",2,"Closed",3,0).

Reference: Salesforce Help, Article ID 000328374, "Examples of Validation Rules".