The case object is a core part of the Salesforce platform. It helps manage and track customer issues and inquiries. You can use this standard object to handle support requests effectively. The case object acts as a central repository for recording and monitoring customer interactions. It allows you to streamline your customer service processes. In order to improve the support efficiency, it is important to assign cases to the right teams or individuals. Although you can manually assign the record, it is possible to use the standard case assignment rules as well. Case assignment rules determine how cases are assigned to users or put into queues.
When you create a new case record, you can just mark "Assign using active assignment rule" to run case assignment rules.
However, if you are creating the case record using Salesforce Flow, there is no standard option to run the case assignment rules. This option exists just for lead assignment rules. Moreover, when you create a case using flow, you have to set the correct owner id. Otherwise, the system doesn't run the case assignment rules and assigns the case to the current user. If you really want to use the logic that you have in your assignment rule, you will have to build the same logic again in the flow.
In this post, you can find a custom invocable action (Apex class) that runs case assignment rules for any case record that you want.
How to Use the Action
1- Install the action using the installation links below.
2- Add a new action to your flow and search for "Apply Case Assignment Rules", this is the name of the action that you installed.
3- Give a name to the action and provide the id of the case record that you want to assign.
You can use this action in any flow type that supports the action element.
Here is a screen flow that clones a case record with its related records. It uses this custom action to assign the new case record. Read this post to learn how to create a flow to clone a record with its related records.
Installation Links
Use this link to install in production or developer edition environments.
Use this link to install in sandbox environments.
Is that a future method or synchronous?
It is synchronous.
Hi Yumi, I tried using this on a case after save flow as an immediate action on create and it doesn't work. However, if I add a scheduled path of 0 min after creation, it works.
Do you know of this limitation?
Thanks!
I'm also noticing that this doesn't work when a guest executes a screen flow from a public page which creates the case.
Is your screen flow working in system context - view all data?
Hi Jay,
It works in asynchronous path as well. I will check if it is possible to use it in the immediate path.