I saw in the Chicago Salesforce Saturday Trailblazer Community a post about the Accept button in Case Queue Lists not showing in lightning. In case you’re not familiar, when you go to a queue on the Case object (or any object), there is a button on the List View that allows a User to Accept the Case (or other object, like Leads).
This works in classic, but not lightning, and the post asked for people to vote for an idea for Salesforce to add it (you should go vote here). The first thing I thought, this could be done with Flows! So, here is the declarative solution (with just a very little Visualforce Page to launch our Flow) to help accomplish this in Lightning!
First, we need to create our Flow. Continue reading
One of the best parts for a Manager in Salesforce is the My Team’s list view, like you are able to see in Opportunities. Sadly, this doesn’t translate to Custom Objects, so it is not as “easy” to select My Team’s, in this case a custom Project object, Projects. Luckily, you can use Roles to help achieve this result!
Throughout the sales cycle, there may be certain fields that you would like to required by stage. There are different ways to do this, for example changing record types by stage and having required fields or using validation rules to require fields if the stage is equal to a certain value. Each way to do this has its own benefits and also its own negatives. I had this need come up with a specific caveat, that it should be very easy for someone who is an admin be able to manage it with ease, as well as show users what fields would be required when the stage was selected. My first thought was to use a Flow that would walk the users through the fields that would be required at that stage and at the end of the Flow, update the stage to the new value. Although this sounded great, it would require someone to update a Flow to add new fields to the requirement. Flows are great for requiring fields to be entered through required fields on a screen, but managing a change in a picklist value, with record types, as well as adding or removing required fields as the business dictates, makes a Flow a lot to manage. Enter another level of Salesforce adminvelopment. (Yes, I saw on the community someone posted, adminveloper, and adminvelopment is a byproduct of adminveloper.)
Some things just go together, like:
Peanut Butter and Jelly
Bread and Butter
Cinnamon and Sugar
Tom and Jerry
Thunder and Lightning
I’m sure you get the picture! Now, I’m still warming up to the idea of calling Flows Thunder, but they go together with Lightning Process Builder just like Thunder and Lightning. The same way that Lightning comes first and is followed by Thunder, Lightning Process Builder can run and kickoff a Flow as an output. You get an update in a flash followed by a roar of business process! Ok, enough with the symbolism!
This For The Community post has been brought to you by the world famous Salesforce Community, the Official: Salesforce Workflow Automation group! Thanks @Jay Singh!
Jay came to me with a question:
Hope you are doing well! I know that you’re a Salesforce flownatic and I just happened to bump into something while creating a flow. I’m trying to get the Contact Roles from the Account module and try to get them to populate over to the Opportunity Contact Roles. So if a Contact Role gets created under the Account, it should appear automatically on the Opportunity’s contact roles. Do you think you can create a blog post for this particular flow. I will truly appreciate it.
Thanks in advance,
As I told Jay on my initial response, kicking off workflow from the Account Contact Role doesn’t quite work with the Standard Salesforce Account Contact Roles. A Custom Object can be used to kickoff workflow, so, upon his blessing to use a Custom Object, we’ll look at how to accomplish his question using Process Builder to launch the Flow. He also said that:
it should update all Opportunities and should only include the Contacts that I am adding from the Contact Roles
Ok. Custom Contact Role tied to the Account, when that is launched, add the new Contact Role as an Opportunity Contact role to every Opportunity on the Account, that’s our goal. Let’s get started!
There was a post in the Official: Salesforce Workflow Automation:
One of the field that user inputs on the screen is picklist in Salesforce. What is the best element to use for that. Do I need to create all picklist values as choices or is there any other way? Appreciate your help.
The short answer is, every picklist must be created in each Flow by a Dropdown List and Choices. There is a long answer (very long!), and it’s Custom Settings! Custom Settings were reviewed in Learning Flow 1.B. Find Related Records and Have Users Select Them in a Screen – Select a Contact and Price Book. The Custom Settings reviewed in that post were Hierarchy, the Custom Settings in this post will be List.
Start by going to Setup and search Custom Settings in the Setup Search Bar. Click on Custom Settings. For the Label, type Picklist Fields, and for the Object Name, type Picklist_Fields. Select List for the Setting Type, Visibility can be Public. For description, type, picklist fields for different objects based on Record Type. Continue reading
Welcome to my first post! This post will be a great start to learning Salesforce Visual Workflow, also known as Flows, where we will be able to create a button that when pressed, will update the Salesforce record. This question was asked in the Orange County User Group. #ForTheCommunity
Does anybody know the exact parameter in regards to saving a record automatically using a custom button? I’m trying to execute it by using Save=x & Save=1 but it just hasn’t done the magic yet. Please assist. Appreciate it.
Thanks in advance,
There was a way using URL hacks that you were able to create a link, have it update the record, and save. For some, that is not available anymore… But don’t worry, Flows to the rescue! Continue reading