HI. I have seen that FLOW has been upgraded in late August 2018 to allow the workflow creator to specify the "REQUESTOR" when creating an APPROVAL ACTION. In the past all emails from an Approval workflow indicated to the recipient that the approval request had originated from the 'workflow creator' and not the person who triggered the workflow. This is a great and I imagine a much anticipated feature improvement.
However, I cannot seem to find a way to update an existing workflow to use this feature as the 'Requestor' element of an existing Approval Action is missing. If I create a NEW Approval Action I can see the "Requestor" element. The screen shot shows this best.
How do I go about editing an existing "Approval Action" to include the "Requestor" element? I have tried exporting and modifying the underlying JSON definition but did not have any luck importing it as a new flow that I could test whilst the original stayed in production. Plus this seemed to be a problematic way to attempt it in any case.
Also, there would be a lot of work to delete the original Approval Action and create a new one due to the dependant downstream flow conditions and actions.
thank-you in advance
For your question to delete the original Approval Action and create a new one due to the dependant downstream flow conditions and actions,I afraid that the only way should be delete the dynamic content of the "Start an approval" action in your dependant downstream flow conditions and actions, and then delete the "Start an approval" action and add a new one.
Thank you for posting on the Flow Community Forum! Have you had an opportunity to apply @Pieter_Veenstra‘s recommendation to adapt your Flow? If yes, and you find that solution to be satisfactory, please go ahead and click “Accept as Solution” so that this thread will be marked for other users to easily identify!
Thank you for being an active member of the Flow Community!
Flow Community Manager
Thanks to @Pieter_Veenstra and @v-yuazh-msft your suggestions were useful. However, I did find that I needed to create a separate Approval Action in parallel to the existing and then create the same conditions and the copy&paste as much as I could from the original downstream actions across to the new Approval flow and its child actions. Some, I had to recreate as the Copy was difficult and sometimes would not complete correctly.
luckily the Flow was small with only a few downstream actions. If this had been larger and more complicated then the end result could not be guaranteed as I am sure something would get missed.
My suggestion to Microsoft is to allow either
a) cloning a complete branch in parallel to provide at least a template to work from or....
b) allow us to edit this element in an existing action item
Your requirment couldn't be achieved in microsoft flow currently.
If you would like the functions that you mentioned should be supported in microsoft flow,please submit an idea to Flow Ideas Forum:
Speakers, submit your sessions now! Call for speakers ends Feb. 10!
We've updated and improved the layout and uploading format of the Power Automate Cookbook!
Fill out a quick form to claim your user group badge now!
We've given our badges an overhaul and also added some brand new ones!
Learn how to build the business apps that you need.
Find out where you can attend!
Watch & learn from the Power Automate Community Video Gallery!