Service Request Automation

[loginerror (Maciej Kuźmicz)]

Here are a few suggestions:

Robot Triggers

I don’t think we are going to make the Orchestrator a monitoring tool for external events very soon. For this you may use tools like zapier a robot that checks constantly and call the orchestrator via api then get the result via webhooks.

For now, you would need to have two robots/processes (it can be one robot that does first the check and then the processing):

• one that will be checking constantly and adding items to the queue
• one that will be scheduled to process that queue of items as many times as you need

In a few updates, you will also be able to set a trigger in Orchestrator on new queue items, see here:

Automatically run bots on new queue item

Will be implemented soon with these high level specs: A queue will have associated no more than one “ consumer” process At the Consumer Process level we may enable “activation”. Once the activation is enabled we set the following properties: **trigger on new queue item **max number of simultaneous jobs - default 1 **min number of queue items to trigger a job (don’t count deferred ones) - default 1 **ramp-up - default 1 - start 1 bot per x queue items **Non Working Days Calendar (optio…