Salesforce Fact #565 | Mass close open tasks using flow

Suppose we need to close all open tasks at once for multiple records. Why not have a flow automation for this.

In order to implement this, we can have a screen flow which can be reused across multiple objects and which will be invoked from the list view button. We can pass the objectCode as an input variable value which would be used for navigating back to the list view page on completion of the flow and also we can pass an input variable which will denote whether WhatId/WhoId needs to be considered.

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