Hi everyone !
This is my first message here, but I’ve been using Make for the past months already, so getting familiar with it.
I’m trying to build an automation which will search on a data store and list the 2 agents receiving the least calls. I’ve set the limit to 2, and I have more than 2 rows in the table, so I know I’ll always receive 2 bundles as an output.
What I’m now trying to do is to process each of the 2 bundles separately, with different actions, for example agent from bundle 1 should be flagged as “A”, and agent from bundle 2 should be flagged as “B”.
However, I can’t seem to find how to process each bundle with a different action. I know that by default each bundle is processed separately, but with the same outcome, not a different one.
Is there an easy way to achieve this ?
Thanks in advance for anyone taking the time to read / provide additional insight !
Ben
Hey Ben,
In your case, I think a router would work perfectly. So after your search module, you would have a router, and then each separate path would be for a specific ‘agent’
For each path, you would need to ensure only bundles matching your criteria go through it.
So for example in your agent A route if that agent has some id or something returned by your search that lets you uniquely identify it, you would use that to setup your filter.
Hope this helps.
3 Likes
Hi IOA_Harman,
First of all, thanks a lot for taking the time to answer !
You’re right, I’m thinking of using a router as well, however I’m struggling with setting up the filters on each path. There are about 10 rows in the data store, and the query from the data store search will dynamically highlight 2 different agents each time (depending on the call volume they receive). I’m attaching a table example to give an overview of how it would look like.
So I would ideally like to set up a router with a filter like : Bundle order number 1 and Bundle order number 2, but I’m not sure it is possible with the data store outcome (see screenshot below).
Many thanks,
Ben
Hey Ben,
If bundle position 1 and 2 is enough, then you can set this up like this:
You would aggregate your search datastore module, and then iterate it so you can use the bundle order position variable from the iterator.
Let me know if this works for you
3 Likes
Hey Harman,
I’ve tried it and it does solve my problem, that’s exactly what I was looking for, but didn’t think of using the aggregator + iterator in this order. Thanks so much !
3 Likes
Awesome, glad it’s working 
2 Likes
