Salesforce Fact #408 | Reuse method invoked from flow and LWC

Suppose we have a similar method logic which gets called by LWC and Flow. Now, we can create two different methods since LWC expects @AuraEnabled(Cacheable=true) annotation, whereas flow allows @InvocableMethod annotation.

But we can simplify this by keeping the logic in the method annotated with @InvocableMethod and calling this method from the other method. This avoids writing redundant code and keeps it simple.

Attached is the screenshot.



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