26-08-22 09:48 AM
26-08-22 01:21 PM
26-08-22 01:26 PM
26-08-22 01:36 PM
Hello,
Within the Hub Control Room, the running / stopping of automations is all through Schedules currently. We have not extended yet with the capability to run ad-hoc processes that are not modelled as a workflow within a schedule.
Background:
Schedules is probably the incorrect word to use now within Blue Prism, because it indicates it must always be run on a clock. In reality, the vast majority of automations are modelled as a multi-task workflow where each task runs 1 (or more) Blue Prism defined RPA processes. A Schedule is the Blue Prism concept to set that up, even though the workflow does not have to run based on a clock, as we also trigger via APIs or people selecting to "run now".
At one point during the development of Version 7, we looked to change the terminology to be more reflective of what a Schedule now is, but for consistency, we choose to keep the current terminology (for now).
30-08-22 05:13 PM
30-08-22 05:40 PM
Hello @Tejaskumar_Darji
That's right.
My question back is: Why do you want to run ad-hoc individual processes?
Reason for asking:
01-09-22 02:28 PM
02-09-22 05:19 PM