8:05 AM
@vicky_molokh-unsilenceMonica was tempted to reply with a Derpy picture, but she has nothing to do with this.
Just SharePoint being SharePoint.
Back before MS decided to replace the old workflow infrastructure with Flow (a new product), you could create a workflow template and associate it to multiple libraries.
So, if you needed five different libs to use the same approval workflow, you just had a single template referenced by all five libs. That way, if you needed to do some change you would need to update only the single template.
With Flow a specifi workflow is tied to a specific library.
So, if five libraries need to use the sale flow, you will have to duplicate the flow for each lib.
You will easily understand that this means you end up with 5 separate copies that you have to maintain. Have to change some text in a mail send during the approval? Update it five times!
And may Celestia save you if you have....let's say... FIFTY libs that need the flow....
So, I started trying to implement a workaround....
But as it always seems to happen with SharePoint... I can get to 90% of my needs... before I hit a stone wall. Try to go to the left? A lava pit. On the right? Poison ivy grove. Climb it and it ends on a vertical drop with no hope to jump to the other side...
