21-08-20 01:58 PM
Answered! Go to Answer.
24-08-20 11:42 AM
There isn't a REST API that you can use unfortunately. You could potentially create a Blue Prism process that will execute the CLI command to list out the known processes, import, export, or whatever you want. And then you could expose that process as a SOAP webservice.
You could also consider reading data directly from the Blue Prism database. We generally don't recommend that you query the main database directly (and you may not have permissions to query the DB directly), but if you have access to something like a read-replica, this might be possible.
Neither of these are perfect solutions, but hopefully they can achieve what you're looking for.
24-08-20 11:42 AM
There isn't a REST API that you can use unfortunately. You could potentially create a Blue Prism process that will execute the CLI command to list out the known processes, import, export, or whatever you want. And then you could expose that process as a SOAP webservice.
You could also consider reading data directly from the Blue Prism database. We generally don't recommend that you query the main database directly (and you may not have permissions to query the DB directly), but if you have access to something like a read-replica, this might be possible.
Neither of these are perfect solutions, but hopefully they can achieve what you're looking for.
24-08-20 01:44 PM
25-08-20 01:49 AM
For a package that already exists, you can create a release and export it from the CLI using:
AutomateC /exportpackage "Package Name" /release "Release Name" /sso
If the /release <release_name> parameter is not specified, the name of the release will automatically be set to "<package_name> - Release #", where the release number is incremented automatically.
Change /sso to /user <username> <password> if necessary.
For detecting which Processes are new or Updated, you can probably look at the audit logs, for example:
Automatec /getauditlog /age 1m /sso
And look for messages matching:
The user '{0}' modified the business object '{1}'
The user '{0}' created the business object '{1}'
The user '{0}' imported the business object '{1}'
The user '{0}' created the process '{1}'
The user '{0}' modified the process '{1}'
The user '{0}' imported the process '{1}'
You might also be able to find the information you want from the system report command:
Automatec /report "C:\Users\Public\system report.txt" /sso
25-08-20 02:58 AM
Hi James
Your command will create a new release for that package. What I need to automate is if somebody created a new release (only at that moment, he or she can export that release as an XML file), I want to export that release as an XML file and import it to the next environment, a kind of promotion process. But the problem is I find no way to re-export that release as an XML file.
Thanks for the audit log and report information, I will look into that next.
Jirong
_______________________________________________________________________
If you received this email in error, please advise the sender (by return email or otherwise) immediately. You have consented to receive the attached electronically at the above-noted email address; please retain a copy of this confirmation for future reference.
Si vous recevez ce courriel par erreur, veuillez en aviser l'expéditeur immédiatement, par retour de courriel ou par un autre moyen. Vous avez accepté de recevoir le(s) document(s) ci-joint(s) par voie électronique à l'adresse courriel indiquée ci-dessus; veuillez conserver une copie de cette confirmation pour les fins de reference future.
25-08-20 04:49 PM
25-08-20 05:11 PM
26-08-20 02:47 AM