Triggers in queues

[Anonymous]

Even though we have scheduler it would be nice if we can start a process trought a trigger in queues.

Basically when a queue as items we should be able to automaticaly start a process.

The only way we can do this right now is if we have a robot checking new queue items , this makes the machine and resourse always unavaliable but there are no cases being worked.

[FelixOehl]

It would be great to see this feature and something similar for 'hot folders' that don't require the need to tie up a licence full time in checking for new items.

[VarunB_R]

Dear Tiago Gonçalves,

By making the queue as an Active queue. 
We have an option of triggering the process using Queue.

[FelixOehl]

@Varun B R I wish it were so, but that's not the way that Active Queues work, as you can see from Dave's post on this thread​​.

If the resource group associated with the active queue finishes processing all items and a new item is subsequently added to the queue processing won't resume which is part of the desired behavior of a 'hot-queue'

[MichelGAILLARD1]

It will provide "on-demand" dynamic execution of a Business Process (BP Process) only when needed. We already have Active Queues definition that define a couple (Process,ResourcePool) that could be used in order to implement that idea.
Provide Request-Reply mechanism. Almost interactive processing of Queued Items, like for example BPC Interact forms submitted that provide answer to an agent.

[LuukOlthof]

I too feel this is needed functionality. 

At the moment you would need another process to monitor the queues and then start other processes when it detects new items. But this takes up a sessions which is not wanted at all. 

The desired behavior I would like to see is the following:

The ability to set a trigger on a queue so that when a minimum of X new Items are present in the queue a session is started for the associated proces and resources. X items should range from 1 to maximum. This way you could set it to 1, which means it will always start when new items are available. Or you could set it to some threshold, say 100. So that when there are a 100 items a sessions is created to start working the items.

If there is a sessions of the associated process running (that is working the items) and new items are added a new session should NOT start. We wouldn't want potentially many session created if new items keep being added while a process is already working them.

UiPath has implemented this functionality already, and let's be honest all companies looking to RPA will compare UiPath, AA and Blue Prism. So, this could make BP fall behind. 

[MelanieGiuliani]

Hi Tiago,

Thanks so much for submitting your idea! We are moving it into the Under Consideration status while we route the idea through our internal review process. 

We will update you as your idea moves along the lifecycle.

Thank you!
Melanie