Flow designer

[solanovale]

I have been task with unifying the current workflows (15) into a single use flow designer. I was planning on using a decision table for the approvals. Problem is that some of the catalog items require more than one approval depending on the value of several variables (for example License type, role...).  I cant use the "Get Variables" action as that is meant for 1 single catalog item and I have no clue on how to get the variables so that I can process that decision. Any suggestions?

[GlideFather]

Hi @solanovale,

I have done something similar in two different approaches.

First one was a flow variable (you can create it in the top-right corner). Here you can script your approval logics - a few if statements or a switch one, then in your flow you can use this flow variable(s) to achieve your desired outcome.

Another thing was a custom table where each catalog item was associated against up to 3 approvals - for example 1st Approval: yes x no, 1st Approval type: Manager, 2nd Approval yes x no, 2nd Approval type: Specific - group, etc... you had an easy form to decide what and how many approvals are required and then there was a general flow to ask one approval with 2 subflow (for the additional 2nd and 3rd approvals) and it was checking the approval properties as per the table so if yo uwanted to change any approval it was without touching the flow and you could just update the data. But I remember it was very complex to test it and to achieve the reminders if any of the approvals were not yet approved etc... 

It's late and I don't know if it makes sense what I tried to explain, feel free to ask :))

[lauri457]

Just create a new action that gets you the variables similar to the "get variables" for record producers. And for the oob action you can just set the item variables as global to have them appear in the slushbucket when they are using that flow.

Just be careful in designing things like this. The recommendation to minimize the amount of flows is to unify processes and promote maintainability. Making monolithic flows that just bake the logic from multiple flows in them typically do not contribute to that.