Written by Flow Components come with the ability to unlock a record through a Flow Action. There are two inputs to the Unlock Record Action. The first is the Unlock Record Id, or the Id of the record that you would like to unlock. The second is System Unlock which is a Boolean of True or False, defaulted to False.
The Unlock Record Flow Action runs in user mode without any additional setup. This means that a User who does not have the ability to unlock the record will not be able to. There is the ability for an admin to configure Flow Components to run in System Mode.
Even if the System Unlock Input Value is set to true, it will not necessarily run in System Mode. This is to ensure that a User has explicit permission to be able to use the Unlock Record in System Mode.
The Flow Component package comes with a Custom Permission, Enable Unlock Record In System Mode. This Custom Permission is required in addition to the Unlock Record Action to be set to True. The Custom Permission can be added to a Profile, a Permission Set, or the Permission Set that comes with Flow Components can be assigned to the User, which is also named Enable Unlock Record In System Mode. These two things together are required for the Flow to run in System Mode.
Hi Rich,
I made a Autolaunched Flow, new Action >
-Created a variable with the data type of text
-Named it recordId
-Selected Available for input
Added the variable(recordId) to the Unlock Record Id test box like it showed in the instrtuctions. Then added Unlock Record Action to be set to True.
After I added custom permissions from the package to the profile. Still not allowing me to change things in the record.
Same issue as Stefan. Added the custom permission to a profile, added to flow and process builder to test, but the records remain locked.
Is it possible to have this work for an partner community user? I was able to successfully implement the process builder and permissions with my internal users to get the unlocking to work, however it will not work for the partner community users with the same permission set used.
Hello, This component used in a flow is such a great solution. However, I followed all the instructions to the letter including adding the permission set and it’s still not unlocking the record even though the flow shows it ran successfully. Any ideas?
Have you enabled “Enable record locking and unlocking in Apex” in Process Automation Settings? Also, you need to ensure that the action has System Unlock set to true in the Flow.