Last Updated on March 1, 2022 by Rakesh Gupta
Big Idea or Enduring Question:
- How to debug a Salesforce Flow as Another User?
After reading this blog, you’ll be able to:
- Debug a Screen Flow as another user
- Debug an Autolaunched Flow as another user
- Debug a Record-Triggered Flow as another user
- Debug a Platform Event-Triggered Flow as another user
- Debug an Omni-Channel Flow as another user
- Debug a Salesforce-Scheduler Flow as another user
Business Use case
Jestilla Zetkin is working as a System administrator at Gurukul On Cloud (GoC). She has created a Screen Flow to Clone a Public Group or Queue with Members. It was working for everyone except one user James Hardie. Let’s help Jestilla to debug this flow.
Guided Practice (We-do):
Debugging a flow in a sandbox org is now easier than ever with the ability to debug a flow as another user. System Administrators or Users with the following permissions (Modify All Data, View All Data, Manage Flows, Manage Users, and Customize Application) can specify the running user each time they debug a flow.
This will help us to catch flow exceptions such as unexpected permission, sharing, and profile configurations before they occur in production orgs.
To enable debug flows as another users, perform the steps below:
- Click Setup.
- In the Quick Find box, type Process Automation Settings.
- Select Process Automation Settings then select Let admins debug flows as other users checkbox.
- Once you’re done, click on the Save.
Note:- As of Spring’22 release Field Service Mobile Flow doesn’t support Debug as another users.
Proof of Concept
To run flow as another user perform the steps below:
- Open a flow in Flow Builder and click Debug.
- Select Run flow as another user.
- Choose the user and click Run.
I want to hear from you!
What is one thing you learned from this post? How do you envision applying this new knowledge in the real world? Feel free to share in the comments below.