Soru

Zorluk: Çok zorCase Capture Mechanisms (Web-to-Case and Email-to-Case)

A Support Administrator at a high-volume retail company is preparing for an annual promotional event. The company captures online support requests using standard Web-to-Case. On the day of the sale, incoming web form submissions dramatically spike and exceed the organization's maximum daily Web-to-Case limit. What happens to the customer submissions that are sent after the daily limit has been reached?

  1. The excess submissions are converted into email messages sent directly to the Default Case Owner specified in Support Settings.Cevap
  2. B
    The excess submissions are placed into an internal temporary queue and automatically created as records when the limit resets 24 hours later.
  3. C
    The web submission endpoint rejects the incoming POST requests immediately and returns an HTTP 503 Service Unavailable status code to the client browser.
  4. D
    The excess submissions successfully generate Case records, but their ownership is transferred to the Automated Process User while bypassing assignment rules.

Cevap

The excess submissions are converted into email messages sent directly to the Default Case Owner specified in Support Settings.
When an organization reaches its 24-hour Web-to-Case limit, Salesforce does not drop the data or throw a web server error. Instead, it forwards an email containing the web form fields and customer details directly to the Default Case Owner defined in Support Settings so support managers can manually handle or process the request.

Adım Adım Çözüm

1
Identify the Case capture mechanism and the operational boundary condition.
The scenario describes Web-to-Case reaching its maximum daily request limit during a traffic surge.
Salesforce enforces governor limits on Web-to-Case requests per 24-hour period based on organization edition.
2
Analyze standard Salesforce system behavior when Web-to-Case limits are exceeded.
Salesforce routes the submitted form data via email to the designated Default Case Owner listed in Support Settings.
This failover mechanism prevents data loss while protecting system resources from unthrottled record creation.

Anahtar Kavram

Web-to-Case Daily Limit Overflow Behavior
Bu soruyu puanla