11

Custom Labels are available in Flows. When you create a Formula, the labels are under "System and Global Variables"


10

You can assign a fault connector and screen to any lookup or DML action. This should capture a validation rule...although I'm not sure if it will on update of a child causing a validation rule on the parent. All you need to do is create a screen with a text output that uses the merge field {!$Flow.FaultMessage}: Then connect the action element to the ...


6

According to the documentation on Getting Flow Variables, you should call myFlow.getVariableValue: String accountId = (String)myFlow.getVariableValue('accountId');


4

When you build a flow one element has to be selected as start element There is a green arrow on above screenshot .Click that to assign it as start element .The green click Icon appears on all the elements and one element has to be set as start element .


4

the new Process Builder (beta) version only supports the latest version of the Google Chrome browser. Please try Chrome and if it's a rendering issue that should get resolved. Hope that helps.


4

Any classes that reference contact object will get this error unless they’re on API version 30 https://success.salesforce.com/issues_view?id=a1p30000000T3FOAA0.. So the simple solustion for your problem is update the version of your class to 30. Also note that there can be classes that cannot be updated to API version 30 because they require test methods ...


4

It says that you only ran a validation check. It even shows that in your screenshot (Check Only: true). Since all you did was validate it, it was not installed, so you will not be able to find it on the system yet.


3

Figured it out, was actually rather simple. I'm operating in the Leads object here. STEP 1 Create a Flow. The flow only needs two elements: a) a text variable, input only, which is called PB_LeadID b) a Delete Record action, which has a criteria of Id = PB_LeadID STEP 2 Create a Process: a) Insert your criteria (i.e. on Create, if fields are equal to ...


3

This is definitely possible, as long as the size of the group and number of daily emails is small enough to let you stay within flow and email limits (limits discussed in more detail at end) There are different approaches, depending on if you want to send one mass email to all of them, or a single customized email to each recipient. I'll assume the latter. ...


3

iframes have been disabled in Salesforce since 2015 to prevent clickjack. Please see resource here: https://help.salesforce.com/articleView?id=IFRAME-or-Web-Tab-Content-Displays-Blank-Page-1327107637323&type=1


3

I ran into this same exact scenario. Another solution that worked for me was changing the @InvocableMethod parameter to: List<List<String>> and then reference the variable accordingly in the rest of the code. Once I did that and went back to my visual workflow APEX call element, I could choose or create a collection in the input parameters.


3

As the error says, you need to contact Support. Once any file has an error of the Internal Server Error variety, all remaining files will also have that same error. There really is (most likely) only one broken flow in the bunch; you might try deploying them one at a time to find the offending file. I can ask my contacts to tell me what the error maps to, ...


3

From the input got from Pranay's answer, I was able to launch flow from quick action. I have created a quick action in Account like: Then I created recordId variable in my flow. Using recordId I added a record lookup to account details. No need to pass account id to flow. recordId is a reserved variable which holds current record id.


3

Download the Installation file, go to the Workbench, log in, click on Migration > Deploy, choose the downloaded file, click Next, and finally Deploy. You can use other tools if you prefer, but this is by far the easiest way for now.


3

The InvocableMethod interface is bulkified. This allows you to map flows within Process Builder in a bulkified manner. As the documentation states, your parameter must be... A list of a primitive data type or a list of lists of a primitive data type – the generic Object type is not supported. This means that to pass in a collection, you actually need to ...


3

You do not need a validation rule or a field. You can build this logic in the Flow directly. That design will look like the following: Obviously, you'll need to tweak this a bit to suit your purposes, but it should be straightforward once you have the proper layout.


3

The answer is "yes". There are a number of different ways to deal with it, depending on the UX you want, how this process should be initiated and the level of coding you are happy to do. My immediate recommendation would be to use a Screen Flow (this is covered in the Trailhead for flows), perhaps initiated from a Lightning Action that you add to the global ...


2

Yes, you can do that with a visual flow. It's simply evaluating a formula where the Event's StartDateTime, depending on how you set it up, evaluates using a formula similar to: DATETIMEVALUE( TEXT( MONTH( Today() ) ) & "/" & TEXT( DAY( Today() ) ) & "/" & TEXT( YEAR(Today() ) ) & TEXT(7:59 AM) ) Using Apex code it would be much ...


2

Something like this should work. You will obviously have to substitute in your values like your flow name, and the parameters, if any, you want to pass in, but this should get you started. {!RequireScript("/soap/ajax/29.0/connection.js")} String base = URL.getSalesforceBaseUrl(); var url = {!base}+encodeURI('/flow/FLOW_NAME&SOME_PARAM={!sObject.Id}&...


2

A possible workaround could be making a masterflow initiating the appropriate flow. You then only have to start this masterflow, and passing the name of the 'subflow' as a parameter: <flow:interview name="StartAppropriateFlow"> <apex:param name="flowName" value="{!NameOfTheFlow}" /> </flow:interview> hope this helps. Note that ...


2

I have worked with flows but haven't integrated them with VF pages, so might be I am missing something here, but can't we use literal names only in flow and render them using rendered attribute of outputPanel? Something like this: <apex:outputPanel rendered="{!renderFlow}"> <flow:interview name="Flow1"/> </apex:outputPanel> <apex:...


2

I ended up using the plug-in found here. There is an idea here that is under point threshold but the PM that created the plug-in commented that it is an enhancement they are working on. The only other way I've heard of people doing is dynamically creating the picklist values based on the options that have been chosen, but that only works if you have records ...


2

I think I understand what you are attempting to do here... It seems that you are using some version of the "Account.Name" instead of "Account.Id"? That seems to be the issue based on your error message, and not something else. Your Process Builder should look similar to this image:


2

These are the instructions from the Developer Documentation: Distribute a Flow to External Users Let external users run your flow by adding the flow to a Visualforce page and distributing that page externally. For example, through a Force.com site, Customer Portal, or Partner Portal. To add a flow to a Visualforce page, embed it by using the ...


2

This won't work because as you've already discovered, you can't nullify input elements in flows. You have to split it into two flows. Split it at the step that captures the input values. So at the step where you would usually present the inputs in the UI, call your new flow from within your current one to capture the input elements or whatever you want to ...


2

Unfortunately, Process Builder can only fire processes off of changes to the main object. If the Process could potentially be fired off of a change to an Account or a change to a Contact, you'll have to create the Process twice. For the Contact process, it'll have to fire when the contact change is made and the contact's Account field matches the right ...


2

I don't know if you specifically need to use the Process.Plugin interface, but if you annotate your method with the @InvocableMethod annotation, you can call your Apex via Flow and via Process Builder (an added bonus). There are some examples in the documentation: public class AccountQueryAction { @InvocableMethod(label='Get Account Names' description='...


2

Unless you have a way of splitting your flow into segments such that it only returns a portion of your records for each segment that totals less than 50k records at a time, you're going to want to convert that process into a batch or even a queueable process. A batch job can handle a nearly unlimited number of records using a query locator. It won't have ...


2

You will need to use the flow(BETA) component from app builder and drop that There is also a great blogpost explaining the procedure


2

Go to flow on which you want to create sObject variable. You can see a utility panel on left side. Click on Resources tab. You can see SObject Variable in list. Double click on that. A popup will open as in the image. Choose Input/Output type and Object type. Refer more on flow variables.


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