3

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 ...


3

The versioned FlowDefinition object is no longer recommended as of API 44.0, in favor of the unversioned Flow, which is the point at which behavior around Flow versions changed in the Metadata API. Using API version 43.0 or prior to retrieve FlowDefinition should return the original versioned files.


2

If anyone needs this in the future, here's the code: Trigger Trigger OppContactRoleTrigger on OpportunityContactRole (after insert, after update){ AddPrimaryContactToOpportunity.runFlow(); } Class public class AddPrimaryContactToOpportunity { public static void runFlow() { for(OpportunityContactRole ocr : (List<OpportunityContactRole>) ...


2

In order to use conditional visibility with custom LWC components, there are two things that need to happen. Dispatch the FlowAttributeChangeEvent when you want to notify the flow runtime that a change has been made. Use automatically assigned variables in the conditions that need to be notified of the change. As per Flow Conditional Visibility ...


1

Obviously your deployment command doesn't take your "--apiversion 47.0" for real. Try increasing your API version in the project file. Or try clearing the .sfdx folder in order to delete any cached stuff, that way it might recognize your requested change in the API version.


1

Here is the same question and a useful proposed solution from the thread: public with sharing class MySchedulable implements Schedulable { public void execute(SchedulableContext sc) { // Call FLOW to do actual work (no input args) new Flow.Interview.MyFlow(new Map<String,Object>()).start(); // Call FLOW w/ input args - keys are case ...


1

So the issue I see here is that calling a flow is not a bulkified process, but to get you a little further, here is you code reworked: public class AddPrimaryContactToOpportunity { public static void runFlow() { //I admit, this is not bulkified for(OpportunityContactRole ocr : Trigger.new) { Flow.Interview flow = ...


1

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.


1

based on doc you should try ISBLANK AND(NOT(ISBLANK([Lead].Source_Opportunity__c)), (ISBLANK(TEXT([Lead].Source_Opportunity__r.Source_details__c)) && NOT(ISBLANK(TEXT([Lead].LeadSource))) && ISPICKVAL([Lead].LeadSource , 'Trig') && NOT(ISBLANK(TEXT([Lead].Source_Opportunity__r.Business_Line__c))) && ISPICKVAL([Lead]....


1

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 ...


1

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


1

https://help.salesforce.com/articleView?id=flow_ref_elements_data_get.htm&type=5 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.


1

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 ...


1

You can use "Get Records" to retrieve the placements using as filter the account lookup field equal to the selected Account Id. UPDATE: You can trigger it using Process Builder or a trigger based on the record update


Only top voted, non community-wiki answers of a minimum length are eligible