![]() If you create an autolaunched flow, you’ll have to create any required input variables yourself. ![]() This gives you access to all of the fields on the record that triggered the flow(and its parent records!!!). For scheduled and record triggered flows, you can access an auto created global variable called $Record. The type of flow you create will impact your experience. From Setup, enter “Flows” into the Quick Find box, select Flows, and then click New Flow. For most logic in these editions, it is easier to use a process. Using this pattern, you can offload especially complex processes to Apex, but still have your flow builder maintain control of the overall process!Įssentials and Professional editions of have a limit of five processes (per process type) and flows (per flow type) in each organization. Note, it is possible for developers to write Invocable Apex methods that you can call from a flow (similar to calling a subflow). Your Salesforce edition limits how many flows you can create. The logic in this flow is so complicated that it makes debugging a pain, plus it makes documenting and managing the flow difficult. An example of this is the flow shown in the Overview section. ![]() There is complicated logic involved that is better managed with Apex code. Generally, you should not use a flow in the following situations: If you are modifying an existing process that was built with Process Builder or workflow, then you should consider a number of factors when deciding whether to modify the existing process or migrate it to Flow.įlows are able to create, edit, and delete records in Salesforce, send emails, show relevant data and gather input from users, and generate outbound messages. If you need to generate a new automated business process, or user guided experience that does not reach the complexity threshold for Apex Code, then flow is your go-to tool.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |