17-11-22 04:39 PM
17-11-22 05:30 PM
17-11-22 06:02 PM
13-07-23 03:26 PM
Hello Vinod,
I trust you're doing great today.
Please, were you able to resolve this? As I am currently experiencing the same thing on Blue Prism 6.10.5
Hello @Eric,
Please what might be the way around this?
Thanks
13-07-23 03:58 PM
The only tickets I've seen come across with regards the exceptions while creating a release have to do with situations where the constituent parts of the overall release are to big. In other words, all the dependencies together with the main process were to big for the 32-bit Automate.exe to read into memory. Do you know if your release includes a lot of dependencies? If so, you might try breaking it up into multiple smaller release files.
Cheers,
13-07-23 06:06 PM
Thanks @Eric Wilson for your swift response.
I am quite new to Blue Prism and might be asking a whole lot of questions.
Please,
Thanks for your time.
------------------------------
Kingsley David
------------------------------
14-07-23 02:15 AM
Hi Kingsley David,
14-07-23 02:15 AM
@David Kingsley - If its about Packages and releases - When you go to Releases Tab in Blueprism -> Package Overview -> Create a New Package -> Drag drop the process onto the second section to be part of package - you do have options when you do right click on the dragged process -> Select dependencies where you get a list of all the dependent objects and environment variables your process is using, see below :
It allows you to select dependencies (Objects and Environment Variables) - all of them or you can choose to skip any on them if not required ! - The other dependencies that you might need to Manually drag drop are Credentials and Work Queue - You can then create releases from this package.
and other ask about multiple releases - its generally One Process with all their dependencies (you don't need to select the Utility/Blueprism VBO ones) they could go in separate releases or might already be present in your other environment, You usually select specific Objects, Env Var, Credentials, Work Queues - all that you created on your own which is specific to that particular process.
14-07-23 07:19 AM
Hello @Mukesh Kumar and @Harish M,
Thanks for your responses.
The challenge is I cannot see the dependencies.
Each time I click on "Select Dependencies" when creating a release on this particular Process, then the sequence error suffices.
For the process in question, I have two versions ProcessA_0.0.1 and ProcessA_0.0.2, and both of them are giving me the same error when I attempt to select dependencies when creating a release.
What can I do at this point?
Thanks
14-07-23 03:31 PM
Do you already know what the dependencies of your process are? In other words, do you know what VBOs, work queues, and environment variables (if any) are being used? If so, try selecting them manually from the left window and dragging them over instead of using the Select Dependencies option.
Additionally, you should open a ticket with Global Support about this issue, if you haven't already.
Cheers,