Hi all,
I'm trying to make use of Git while developing Blue Prism processes.
I have several objectives with this, but my main motivation is:
- Creating a better structure for development
- Better version handling
- Making it easier to transfer processes/objects from DEV to TEST to PROD
- Disaster recovery
- Etc.
So far, I have:
- Set up a DevOps project/repo
- Created a PowerShell script for exporting all processes and objects using CLI AutomateC.exe
- Committed files from the folder where the PS script exports the files (i.e., my repo) to DevOps
The PS script uses the /listprocesses trigger to retrieve the names of all (published) processes and objects. The next step is to use the /export trigger on each of them.
I want to be able to export files from DEV using this script so that I can manually import the processes/objects I choose/need to TEST/PROD via Blue Prism's File->Import->Process/Object function.
The PS script works perfectly fine, except the exported files are named .xml instead of .bpprocess and .bpobject. Unfortunately, the /export trigger doesn't provide any parameters to decide the filename in the script.
As I also want the possibility to manually export a process/object to the same folder (the repo) via File->Export (which names the files as .bpprocess and .bpobject), the fact that the PS script names all files .xml won't do. Hence, I developed the script further by adding a renaming loop that renames all processes and objects to have the proper extension.
I'd be surprised if there are no flaws in my "logic" here, and I'm hoping there are others out there wanting to achieve something similar. If anyone is interested, I'd happily share the PS script here.
