ADM-201 · Question #10
Ursa Major Solar is a Canadian company that has the following set up in Salesforce: - They have activated Web-to-Case on their corporate website. - Auto-Response is configured so that customers are th
The correct answer is B. In an Active Case Flow, change the name of the Queue to World.. To route cases that do not match existing assignment rule criteria to a specific 'Queue - World', the active case assignment automation (potentially a Salesforce Flow) must be configured with a fallback to that queue.
Question
Ursa Major Solar is a Canadian company that has the following set up in Salesforce:
- They have activated Web-to-Case on their corporate website.
- Auto-Response is configured so that customers are thanked for logging the case and activated
Assignment Rules based on the province (CANADA) in which the customer resides.
- Case ownership is therefore determined and routed to the corresponding queue - North, South,
East, or West. Customer Cases that do NOT meet the existing criteria need to be assigned to Queue - World. Which solution will satisfy this requirement?
Options
- AIn Case Support Settings, change Default Case Owner to Queue - World.
- BIn an Active Case Flow, change the name of the Queue to World.
- CUsing a Workflow Rule, change the owner of new Cases outside CANADA to Queue - World.
- DUsing a Trigger, change the owner of Cases outside CANADA to Queue - World.
How the community answered
(26 responses)- A4% (1)
- B77% (20)
- C15% (4)
- D4% (1)
Why each option
To route cases that do not match existing assignment rule criteria to a specific 'Queue - World', the active case assignment automation (potentially a Salesforce Flow) must be configured with a fallback to that queue.
Changing the Default Case Owner in Case Support Settings is the standard declarative fallback for cases that don't meet *standard assignment rule* criteria. However, if an "Active Case Flow" is explicitly called out as the mechanism, it implies the logic resides within that flow, making this option potentially overridden or not applicable.
If the case assignment logic is managed by an "Active Case Flow" (a Salesforce Flow), then the Flow itself must contain the decision logic to route cases that do not match specific criteria (like Canadian provinces) to a designated fallback queue, such as 'Queue - World'. This ensures all cases are assigned appropriately within the automated process, assuming 'change the name of the Queue to World' is a misphrasing for 'assign to Queue - World'.
Workflow Rules are a legacy automation tool and typically execute *after* assignment rules. Using them for this purpose would be less efficient and potentially redundant if the assignment logic is handled by a Flow or standard rules.
Using an Apex Trigger is a programmatic solution, which is generally considered a last resort when declarative tools like Flows or Assignment Rules can meet the requirement; this scenario typically has declarative options.
Concept tested: Case Assignment Fallback Logic (within Flow context)
Source: https://help.salesforce.com/s/articleView?id=sf.flow_overview.htm&type=5
Topics
Community Discussion
No community discussion yet for this question.