Since there's no looping in the workflow, the only option is probably to check each service item individually using conditions. To reduce the number of workflow blocks, you can group the checks by approver - for example, if one person is responsible for five systems, there's no need to create five separate checks, just one with an "any" condition. If you want all approval requests to be sent simultaneously rather than in sequence, make sure the "send approval" actions are placed at the very end of the workflow, after all the checks.

We have about 20 to 30 applications. So the only way is to have 30 conditions and send respective apporvals?. Thanks for clarifying. I really wish freshservice team could comeup with some solution for the looping part. Really makes the workflow powerful

​@Sri charan  you don’t need 30 conditions, you need a reader node. 

Then you set the Condition box to check the reader returned a valid record, if it does then there’s an approval required. Then you have the action block “SEnd approval mail to {{R1.Approver_Name}} or whatever your field is called. 

That way its ONE branch

Yes, there are no loops but you use a reader node to look for the matching approver. 

Wouldn't the Reader stop at the first record that meets the condition and fail to find the next one, which might have a different approval manager?

I haven’t tested this solution because we decided to separate the requests by software, but you can try using a bundle. From what I remember, if you enable the option with children, the workflow is triggered separately for each child item, so there’s no need for looping. I’m not sure how it would behave if you leave everything within a single service request - it will probably only send one approval - but you can test it and see how it works.
 

Yes, ​@Sri charan should be having separate requests for each application, you could bundle them together in the same request, if you only want one ticket, and then have the trigger to be requested item is added. 

Blending them all together will make it SUPER difficult to track who’s approved what, and take the appropriate action next. 

In my experience you should make it to where only one application can be selected per ticket otherwise what happens when one of the application owners rejects it? It also makes it much more complicated from an automator standpoint.

If you do one per ticket the workflow automator would trigger when the request is used. Use the reader action to get the custom object details, filter by record id is service request fields.application (or whatever you called the dropdown). Then use the send approvals action, send approval mail to the reader number and the approvers column.  (R4.Approvers)