An architect has been asked to provide error messages when a future date is detected in a custom Birthdate _c field on the Contact object. The client wants the ability to translate the error messages. What are two approaches the architect should use to achieve this solution? Choose 2 answers
A.
Implement a third -party validation process with translate functionality.
B.
Create a trigger on Contact and add an error to the record with a custom label.
C.
Create a workflow field update to set the standard ErrorMessage field.
D.
Create a validation rule and translate the error message with translation workbench.
B.
Create a trigger on Contact and add an error to the record with a custom label.
D.
Create a validation rule and translate the error message with translation workbench.
Explanation:
For translatable birthdate validation, both a trigger with custom labels (B) and validation rules with Translation Workbench (D) are valid approaches. Custom labels in triggers allow: 1) Complex date validation logic; 2) Multilingual support through label translations; and 3) Consistent messaging across interfaces. Validation rules offer: 1) Declarative implementation; 2) Translation Workbench integration; and 3) No code maintenance. Third-party tools (A) add unnecessary complexity. Workflow field updates (C) can't set validation errors. The trigger approach provides maximum flexibility for complex date validation scenarios, while validation rules offer simplicity for basic future-date checks. Both leverage Salesforce's native translation capabilities - custom labels for triggers and Translation Workbench for validation rule error messages. This dual recommendation accommodates different technical preferences while meeting the core requirement of translatable error messages. The solutions can be implemented without external dependencies and will automatically display errors in the user's language based on their locale settings. This is particularly valuable for global implementations where birthdate validation needs to be enforced consistently across multilingual user bases.