Does anyone have any experience with advanced process scheduling in Orchestrator apart from simple cron expressions, intervals and specified datetimes? For instance, is it possible to set up triggers (i.e. a certain mail enters the mail inbox) or have one robot automatically switch what process to work on based on transaction priorities across different queues?
Let us imagine the following scenario:
• We have one robot
• We have 4 processes, P1, P2, P3 and P4
• P1 has 100 transactions, with each transaction requiring a 3 minutes average processing time
• P2 has 20 transactions, with each transaction requiring a 10 minutes average processing time
• P3 has 5 transactions, with each transaction requiring a 2 minutes average processing time
• P4 has one transaction, requiring 10 minutes processing time
• All of the processes are to run between 08:00 and 17:00
• P1 can run whenever, so long as it is finished at 17:00
• P2 must be run every 20th minute
• For every fourth transaction handled in P2, one transaction from P3 must be handled immediately afterwards
• P4 is triggered if the stock price of Apple rises with 0.2 % from yesterday’s closing price (alternatively if a mail with the subject “GoGo4” enters the Outlook Inbox)
The above situation would require interval scheduling, switching between processes automatically on one robot, business rules (only start P3 if [P2 handled today]mod4==0), and external triggers (apple stock or mail inbox).