You are right. OR conditions don't work for multiple field. A workaround would be to use to 2 Get Record elements. One for UserId another for Email. After each Get Record use a Loop element to iterate over fetched records and add in a Record Collection Variable.
Flow would look something like this:
Record Collection Variable may contain duplicates which can ...
that's not possible for the moment if you can use only the standard components. there are 2 possible ways:
Custom Lightning Component
Packages from AppExchange (i'm not sure if there's a package for that, but you can give it a try)
You can upvote an idea that asks the same thing that you questioned.
I'm sorry for my english, i hope you understand what i ...
The "Lightning StyleSheets" attribute only adds the look of Lightning, but does not actually contain the full runtime. You need to expose the flow in a Lightning App or Lightning Component. Use lightning:flow to expose a flow in a compatible experience.
based on doc you should try ISBLANK
ISPICKVAL([Lead].LeadSource , 'Trig') &&
Calling Apex from a screen flow is easy to achieve. You simply have to make sure you can call the code via an @InvocableMethod. The approach I take is to have the invocable method in a separate class (what I call a "facade") that then invokes the required logic on my underlying class. This has a couple of benefits:
You can adapt the input parameters to be ...
A user from the Process Automation group came back to me with this:
1Q: Yes. Design the flow as if you are working on a single record. And scheduled flow does the bulkification for you.
2Q: Yes. You have access to all the fields on the record.
3Q: Scheduled Flow is run as the "Automated Process" user. This is different from Default Workflow User
Scroll down on the get record screen and select "Manually assign variables (advanced)". There should be an option at the bottom to specify setting the variable to null when no records are returned. Now, you can add a decision to check if this variable is null.
EDITED 11/12/2019 1:17pm PST
To solve this usecase, query the EntitySubscription Object to gather the users who should receive the email and leverage the Flow Core Action: Send email (instead of the Simple Email)
Addition by Kleinhomer 11/13/19 3:45 PM EST: Because the custom object that I made the email template off of didn't have an email address ...
You can use "Get Records" to retrieve the placements using as filter the account lookup field equal to the selected Account Id.
You can trigger it using Process Builder or a trigger based on the record update
You don't want to do Get Records and Update Records within a loop. Instead, you have to loop through your contacts and assign each ID to a collection variable. When that is done, you do the Get Records using the ID collection var and assign each contact to an Contact collection var.
Then you loop through the Contact collection, assign the desired values ...
The solution is simple actually it seems the standard DependentPicklist attempts to cache the initial values if they come directly from the object you have queried. To fix this issue, simply create a assignment element with the dependent and controlling picklist values as a text variable and use those values in Picklist 1 value, Picklist 2 value and even ...