If you have various tasks that a centralized process could perform, then you could dedicate one session/license to be consumed 24/7 in order to perform those tasks. For example, if you had 10 licenses (technically 1 license that can run 10 concurrent sessions) and you had 9 Processes that may or may not need to run simultaneously, you could consume 1 session of your license with a process that just checks a list of file/folder locations, looking for input files. This process itself could take an input of an Excel spreadsheet that lists out the folder locations, input file names/locations, processes associated with those input files, resources on which the processes should be run, etc. Then you'd use the Utility - AutomateC object to spin up sessions of the processes whenever they are needed. This is called Dynamic Scheduling and there's some info on it in the Documents section of the Portal.
If this sounds complex, it actually can be quite easy. It just depends on how dynamic you need it to be. At a very basic level, you may have one process per machine so that you always know the machine will be available for use by that process. Then business users could drop input files into the input directory any time they like.
Of course, you could go really easy with it. Give the business user a batch file that they can run any time they like. So, they would (1) drop the input file where it goes and (2) run the batch file that sends a command to Blue Prism to spin up the session that they're allowed to run. In 6.3+ you can restrict which processes they are allowed to run so you don't get crazy things happening.
Dave Morris
3Ci at Southern Company
Atlanta, GA
