I've seen this automated but only a piece of it since there are a lot of things to think through before just blanket importing releases in an automated way.
Regardless of exactly what you do, you will need to use CLI commands using AutomateC. I would not ever spy the UI of Blue Prism to accomplish anything unattended. Not that it can't be done, but you seriously need to exhaust all other options before doing something like that.
There are two places you can look at for info on AutomateC, and I suggest you use them both.
Go into Blue Prism and press F1 (or click the ? button and then click 'Show Help Topic'). From here, you can search for 'command line' and then look at the Topic entitled 'Blue Prism Command Line Options'. This is a great resource because it gives explanations of using AutomateC CLI commands. The problem here is that not all of the available commands are listed. For example, '/setev' is not in this list but it is an available AutomateC command that sets environment variables. Use #2 below to see the full list of commands (there's only a few that are left out of the F1 Help)
Go to your command prompt, navigate to your BP Automate folder (C:\Program Files\Blue Prism Limited\Blue Prism Automate) and then run the command 'AutomateC /help' to get a full list of commands that are available. You'll see that the list is similar to the one in F1 except that it has a few more.
There are at least two commands you'll be interested in, maybe more:
/exportpackage [/release ]
/importrelease
Notice that this says 'importrelease' not just 'import'. A lot of people mistakenly try to use /import which is for a single process/object.
So, an example use of these commands would be like this:
automatec /sso /dbconname ""Name of Lower Environment's Connection"" /exportpackage ""Name of Package"" /release ""Name of Release""
automatec /sso /dbconname ""Name of Higher Environment's Connection"" /importrelease ""Release Path""
You'll want to test this yourself before assuming it works because I can't fully test it now. I'm assuming the exportpackage command exports into the Blue Prism Automate folder or somewhere like that. I don't have admin rights on the machine I'm using right now so it's throwing an error for me saying I don't have access to the path. I don't see a way to choose the destination path. If anyone else knows how to do this, please let me know.
Dave Morris, 3Ci at Southern Company