Component visibility is an awesome admin super power where you can conditionally show information to the user that is relevant to them. Otherwise, hide that noise from them. Love being able to use component visibility in Lightning App Builder with components and also in Flow Builder when building screen flows. Keep component visibility in mind… Continue reading Use Component Visibility to Show Information At the Right Time in Screen Flow
Use Dynamic Actions to show actions relevant to the user at the right time.
As someone who performs user administrative tasks, you may need to freeze a user right away. Or you may be aware of a user’s upcoming departure date. Rather than having to remember to freeze them later, wouldn’t it be great if you can schedule the user’s freeze date/time? Or, what if you can lookup the… Continue reading Freeze a User – Now or in the Future
If you have configured the standard screen flow lookup component and get an error “Record is not createable.” when you test it as a user, this is due to the fact that the running user of a flow must have the Create permission on the source object. For example, to search a contact’s creator, the… Continue reading Trick: Running User Must Have Create Permission to Field Used in Screen Flow Lookup Component
Eliminate requiring your users to remember things they need to do in Salesforce. Drive consistency to users with a to-do list on the record page using the Actions & Recommendations component in Lightning Experience. (Note: The main intent of the Actions & Recommendations component is to show flows, quick actions, and recommendations from your Next… Continue reading Give Your Users a To-Do List with the Actions & Recommendations Component
A very much awaited feature is coming in Summer ’21 – we will have the ability to use the IsNew(), IsChanged() and PriorValue() syntax in formulas as you can in workflow rules and processes in record-triggered and scheduled flows. Here are a few lessons learned from implementing this use case: Use the IsNew(), IsChanged() and… Continue reading Use IsNew(), IsChanged() and PriorValue() in Flow Formulas
Create a dynamically created record detail link in flow
Sometimes, a customer service rep (CSR) may service a person that is associated with multiple WhatIds (accounts, policies, opportunities, etc.) and when they create a task or log a call, they can only relate the task to one account, policy, opportunity, etc. There is no option to relate it to multiple things. Instead, they create the first log a call or task and relate it to the one account, policy, opportunity, etc. and then they clone the log a call/task and relate it to another account, policy, opportunity, etc. If there is another account, policy, opportunity, etc., they need to repeat the cloning step again.
What if, we can make this more efficient for the CSR?
What if, they can select the accounts, policies, opportunities, whatever they need to relate the task to on one screen and upon submit, it clones the tasks for each account, policy, opportunity, or whatever it is for them?
Let’s delight those CSRs and increase their overall productivity so they can move onto the next customer.
Learn this cool trick to bypass validation rules in your process or flow, just like you can with workflow rules.
This blog post was inspired by Yvonne Navas. Here are a few lessons learned from implementing this use case: Use an email alert with a Classic Email Template to send an email with a file attachment Use a record triggered after save/update flow to send the appropriate email Business Use Case: Addison Dogster is the system… Continue reading Send An Email with an Attachment When an Event is Created or Event Date Revised