KernDX

Appearance

UTIL_ValidationRule ​

Class · Group: Validation

apex
global inherited sharing class UTIL_ValidationRule

Formula-driven declarative validation framework for advanced validation scenarios that standard Salesforce validation rules cannot handle. This framework enables: Cross-object validation requiring queries Complex conditional logic exceeding native formula limits Validation with sophisticated bypass rules Shadow mode for safe production testing Warning severity that logs but allows save Important: This framework complements standard validation rules. Use native Salesforce validation rules for simple field checks. Use this framework for advanced scenarios.

Usage Patterns ​

Configure via TRG_ExecuteValidationRules trigger action:

apex
// No code required - configure via TriggerAction__mdt to use TRG_ExecuteValidationRules

Direct Programmatic Usage ​

apex
// Validate records programmatically
List<UTIL_ValidationRule.ValidationResult> results =
    UTIL_ValidationRule.validate(Trigger.new, Trigger.old, TriggerOperation.BEFORE_INSERT);

// Apply errors to records
UTIL_ValidationRule.applyErrors(Trigger.new, results);

Bypass Usage ​

apex
// Bypass all validation for an object
UTIL_ValidationRule.bypassObject('Account');
try
{
    insert accounts;
}
finally
{
    UTIL_ValidationRule.clearBypass('Account');
}

Since: 1.0

Example:

apex
List<UTIL_ValidationRule.ValidationResult> results =
    UTIL_ValidationRule.validate(Trigger.new, Trigger.old, TriggerOperation.BEFORE_UPDATE);
UTIL_ValidationRule.applyErrors(Trigger.new, results);

See Also: ValidationRuleGroup__mdt, ValidationRule__mdt, TRG_ExecuteValidationRules

Properties ​

PropertyDescription
global interface INT_BulkValidationContextOptional interface for bulk-optimized validation contexts.

Methods ​

MethodDescription
global static void applyErrors(List<List<UTIL_ValidationRule.ValidationResult> results)Applies validation errors to the trigger records.
global static void bypassGroup(String groupDeveloperName)Bypasses all validation rules in the specified group.
global static void bypassObject(String objectApiName)Bypasses all validation rules for the specified object.
global static void bypassRule(String ruleDeveloperName)Bypasses a specific validation rule.
global static void clearAllBypasses()Clears all bypasses for the current transaction.
global static void clearBypass(String identifier)Clears a specific bypass (object, group, or rule).
global static void executeForTrigger(List<List<SObject> oldRecords, TriggerOperation operation)Executes validation rules for the current trigger context.
global static Boolean isBypassed(String identifier)Checks if a specific bypass is currently active.
global static List validate(List<List<SObject> oldRecords, TriggerOperation operation)Validates a list of records against all applicable validation rules.

Inner Classes ​

ClassDescription
ValidationErrorRepresents a single validation error or warning.
ValidationResultResult of validating a single record.

Method Details ​

applyErrors ​

apex
global static void applyErrors(List<SObject> records, List<UTIL_ValidationRule.ValidationResult> results)

Applies validation errors to the trigger records. Error severity violations call record.addError() to block save. Warning severity violations are logged but don't block save.

Page-level addError calls coalesce in Database.SaveResult. When the validation rule targets the whole record (i.e. kern__ErrorDisplayField__c is blank — page-level error), each violation invokes record.addError(message). Salesforce's platform behaviour for page-level addError is to COALESCE multiple calls on the same record into a SINGLE Database.SaveResult.Error entry — only the LAST rule's message is surfaced via getErrors(). Field-level addError (record.addError(field, message), used when kern__ErrorDisplayField__c is set) is per-field unique and does NOT coalesce.

Subscribers that want to see ALL violations on a record should consult the framework's own ValidationResult.errors collection, which preserves every violation regardless of page vs field scope. The Database.SaveResult.getErrors() collection should be treated as a "save blocked" / "save succeeded" boolean, not as a complete error inventory.

Empirically: a record violating two page-level rules (e.g. RequireAccountIndustry + PhoneOrWebsiteRequired) returns getErrors().size() == 1 with only the second rule's message — but ValidationResult.errors.size() == 2 reports both correctly.

Parameters:

  • records (List) - The list of records (Trigger.new)
  • results (SObject) - The validation results

Since: 1.0

Example:

apex
UTIL_ValidationRule.applyErrors(records, new List<ValidationResult>());

bypassGroup ​

apex
global static void bypassGroup(String groupDeveloperName)

Bypasses all validation rules in the specified group.

Parameters:

  • groupDeveloperName (String) - The DeveloperName of the ValidationRuleGroup__mdt to bypass

Since: 1.0

Example:

apex
UTIL_ValidationRule.bypassGroup('SalesCloud_Account_Validations');

bypassObject ​

apex
global static void bypassObject(String objectApiName)

Bypasses all validation rules for the specified object. This is the highest level of bypass and takes precedence over group and rule bypasses.

Parameters:

  • objectApiName (String) - The API name of the object to bypass (e.g., 'Account')

Since: 1.0

Example:

apex
UTIL_ValidationRule.bypassObject('Account');
try
{
    insert accounts; // No validation rules fire
}
finally
{
    UTIL_ValidationRule.clearBypass('Account');
}

bypassRule ​

apex
global static void bypassRule(String ruleDeveloperName)

Bypasses a specific validation rule.

Parameters:

  • ruleDeveloperName (String) - The DeveloperName of the ValidationRule__mdt to bypass

Since: 1.0

Example:

apex
UTIL_ValidationRule.bypassRule('Account_Requires_Primary_Contact');

clearAllBypasses ​

apex
global static void clearAllBypasses()

Clears all bypasses for the current transaction.

Since: 1.0

Example:

apex
UTIL_ValidationRule.clearAllBypasses();

clearBypass ​

apex
global static void clearBypass(String identifier)

Clears a specific bypass (object, group, or rule). For each bypass type the identifier was actually registered under, emits a validation CLEAR audit entry carrying the matching prefixed target (object:/group:/rule:) so the clear correlates to its originating bypass. An identifier that is not currently bypassed removes nothing and emits nothing.

Parameters:

  • identifier (String) - The object API name, group DeveloperName, or rule DeveloperName to clear

Since: 1.0

Example:

apex
UTIL_ValidationRule.clearBypass('Account');

executeForTrigger ​

apex
global static void executeForTrigger(List<SObject> newRecords, List<SObject> oldRecords, TriggerOperation operation)

Executes validation rules for the current trigger context. This is the main entry point for trigger-based validation.

Parameters:

  • newRecords (List) - The list of new records (Trigger.new)
  • oldRecords (SObject) - The list of old records (Trigger.old), may be null for insert
  • operation (List) - The trigger operation

Since: 1.0

Example:

apex
// In a trigger action class
UTIL_ValidationRule.executeForTrigger(newRecords, oldRecords, TriggerOperation.BEFORE_UPDATE);

isBypassed ​

apex
global static Boolean isBypassed(String identifier)

Checks if a specific bypass is currently active.

Parameters:

  • identifier (String) - The object API name, group DeveloperName, or rule DeveloperName

Returns: Boolean - True if bypassed

Since: 1.0

Example:

apex
Boolean result = UTIL_ValidationRule.isBypassed('value');

validate ​

apex
global static List<UTIL_ValidationRule.ValidationResult> validate(List<SObject> newRecords, List<SObject> oldRecords, TriggerOperation operation)

Validates a list of records against all applicable validation rules.

Parameters:

  • newRecords (List) - The list of new records to validate
  • oldRecords (SObject) - The list of old records (may be null for insert)
  • operation (List) - The trigger operation determining which rules apply

Returns: UTIL_ValidationRule.ValidationResult - List of ValidationResult objects, one per record

Since: 1.0

Example:

apex
List<ValidationResult> result = UTIL_ValidationRule.validate(records, records, TriggerOperation.BEFORE_INSERT);