I think there have been two topics mixed in this thread. One is about triggering a process (from events external of Blue Prism) and the other one is about semaphores (hand-shake mechanisms). Since the second topic depends on the actual implementation and integration scenario, I try to add some info about triggering process execution.
Blue Prism offers several ways to start a process.
- One is of course the scheduler and manual start of process.
- Exposing processes and objects as web services
- Starting via CLI, command shell
Those interfaces can be called by external systems.
An interesting approach for mail based execution was discussed here:
Trigger Process in Blue Prism when email arrives in OutlookPer default the processes are executed as soon as they are triggered. Unfortunately there is no built-in queuing mechanism but could be implemented by creating a master process that manages requests and handles execution (eg via work queue).
With immediate execution there is no control if there is a free runtime resource available. If there is none free, the execution will fail. At least in case of exclusive process execution. Simultaneous processes could be run in background, in case only limited runtime resources are available.
Another topic is the number of available licenses. Licenses limit the number of parallel executed processes. If you have one license, only one process will run. If tried to start another process when the first one is still running, it will fail.
If possible, the execution should be planned to avoid issues with random peak times, going over the limits of your infrastructure.
Regards
------------------------------
Walter Koller
Solution Manager
Erste Group IT International GmbH
Europe/Vienna
------------------------------