Examkin

Question

Difficulty: MediumCase Capture Mechanisms (Web-to-Case and Email-to-Case)

A company uses Web-to-Case to capture service inquiries submitted through its public website. Which two actions occur when Web-to-Case processing limits are exceeded or when a web submission fails custom validation rules? (Select 2)

  1. Submissions exceeding the daily request limit are sent as email notifications containing the case data to the Default Case Owner.Answer
  2. Submissions that fail custom validation rules generate an email containing error details and form values sent to the Default Case Owner.Answer
  3. C
    Excess web submissions beyond the daily limit are automatically stored in an internal holding queue until the 24-hour limit resets.
  4. D
    Form submissions that trigger validation errors display an interactive HTML error page directly on the submitter's browser.
  5. E
    Submissions exceeding daily limits are automatically converted into On-Demand Email-to-Case messages assigned to the automated process user.

Answer

Submissions exceeding the daily request limit are sent as email notifications containing the case data to the Default Case Owner, and submissions that fail custom validation rules generate an email containing error details and form values sent to the Default Case Owner.
When Web-to-Case reaches its daily organization limit or when a submitted payload fails validation rules during record creation, Salesforce sends an email containing the submitted values (and any error messages) to the designated Default Case Owner rather than creating a Case record or returning errors to the end user.

Step-by-Step Solution

1
Analyze Web-to-Case limit overflow handling.
Salesforce sends the submitted case details directly to the Default Case Owner via email when daily request limits are exceeded.
This guarantees that customer inquiry data is not lost during high-volume traffic spikes.
2
Analyze Web-to-Case custom validation failure handling.
Salesforce emails the form data and error logs to the Default Case Owner without creating the record or displaying error messages to the website visitor.
Because Web-to-Case generates HTML forms for external websites, backend validation errors cannot be safely rendered to end users and are delegated to the administrator/owner for manual resolution.

Key Concept

Web-to-Case limit overflow and validation error fallback mechanisms via the Default Case Owner.
Rate this question

Topics

Case Capture Mechanisms (Web-to-Case and Email-to-Case)

More questions from this topic