A requirement that has come up quite a few times recently is the ability to quickly trigger a workflow with an input arguement that can be passed into the workflow. So in this guide I'm going to cover creating a task for a manager to call a customer before confirming a sale. The user will put in the agreed price before the task is created.
1) Open up your solution and add a new process
2) Name your process, set the category as "Action" and the entity that you want to run the action from (not the entity you want to populate)
3) Tick the "As BPF Action step" flag
4) Now lets get into creating your input argument, Select the "+" Sign
5) We now want to name the argument, set it as a string (for text) and if it is required or not, I also will have this as an Input Argument
6) We now want to add a task by selecting the Add Step and selecting Task
7) We will select "Local Values" and then "Arguments"
8) We now use the TaskText from the drop down and then add
9) Lets now select the field in the task we want to add the argument into.
10) For this instance i will also assign it to the "Sales Manager" team so they can pick it up
11) Once you have saved the task we then want to activate the action.
12) Lets open up the BPF that we want to add the action to.
13) Select the stage and add an "Action Step"
14) Set the sequence and then use the lookup to get the created action.
15) If you want to also update the opp you can also use the TaskText to update any text field on the opp.
16) When we get to the stage of the BPF click on the execute button.
17) A Popup will appear asking for the text. Add this and execute the action.
18) You will now see that you have a new task for that record and it will also appear in the managers queue to be completed.
Now as you see this is a very basic action step with only one argument but you can use this to update multiple entities at once. Another example i had recently was a customer asking for all Mobile Phone numbers to be updated at the end of a phonecall you could use this same structure to ask for this information at the end of the process. The one limitation that it has at the moment would be that you cannot use a lookup as part of a BPF Action (you can still use it in a normal action)
Thank you for this. Really helpful. But there is definitely a flaw currently in the system. If you use this Action step in the BPF on a particular stage, the Next Stage button there stops working. Did you get this problem too when you tried it? Or are you aware of a solution?