Salesforce Fact #417 | FLS on Fields(Beta) option in screen flow

While using Fields(Beta) option in screen flow, do you know the execution context and FLS defines the field visibility to the user.

In this example, we have made the Account Type field as read only for a profile. Now, when the flow runs with the option: User or System Context - depends on how the flow is launched, then the field does not appear to the user. But for the other two options related to System context, the field appears and it is read-only to the user.

Attached are the screenshots.








Comments

Post a Comment

Popular posts from this blog

Salesforce Fact #192 | Call batch apex from flow

Image
Generally apex batch jobs are scheduled to run at particular time intervals. But suppose we have a use case where we need to run the batch job on adhoc basis. We can call the batch apex from a screen flow in that case and the screen flow can be invoked from a button. So, the batch job can be executed on demand. Attached are the screenshots.
Read more

Salesforce Fact #457 | Get current user role name in flow

Image
In apex, in order to get the current user role name we need to query the UserRole object. We cannot get it directly using UserInfo object since it has only one method related to role i.e  getUserRoleId(). Using this Id returned we can get the data from UserRole object. But that is not that complex in flow. In case of flow, we can directly get the current user role name using the syntax: {!$UserRole.Name}. Attached are the screenshots.
Read more