It’s useful to extend the existing functionality of your Business Process Flow (BPF) and include automations in the form of a flow. Some things are worth keeping in mind when you incorporate a Flow. Part two focuses on bringing the Flow created in Part 1 to our BPF.
Adapt the Business Process Flow
We go to Powerapps portal to edit the Business Process Flow I currently am working on. Make sure you work on the same solution where your Flow is created. A tip here is to not work in the default solution!
When you select edit, the canvas editor will show to edit the several stages with components and actions. Select the desired stage, in this case the the develop stage.
When you drag and drop it to the correct place, it should look similar to this:
Now it’s time to glue all things together and choose the flow created in Part 1.
Add BPF to Model-Driven App
A model-driven app contains all visual building blocks (forms, views, dashboards, charts,…) to show the data in Dynamics 365 CE. Because the BPF is a custom one, you still need to add it to the desired App to be able to use it. To do so, open the app designer and check following:
The user is now capable of sending an email just by clicking the “Run Flow” button inside stage 2 of the BPF. When triggered, the end user is prompted with the parameters specified in the trigger action in the flow, in this case the Email Subject. To inform the user the flow has run successfully, I added the set succeeded on the process log record. If I did not so, the flow would have shown up as processing.
Thanks for the update on the ends to succeeded information, I understand that the user must refresh after calling the workflow to see it, right?