cancel
Showing results for 
Search instead for 
Did you mean: 
Status: Not Planned

I believe it is advantageous to include the list of default objects within the learning edition of Blue Prism (which was the case prior to 7.3). I can't speak on behalf of everyone but we currently don't have a training environment within our Enterprise install of Blue Prism and utilise the learning edition to run training of the Blue Prism product.

Not having these included with the learning edition requires us to provide a release file to each trainee, or have them download what they need from DX directly.

Also, I note that the documentation is not correct for verifying an installation as it still points to the VBO folder, which is now empty as of 7.3.

2 Comments
Hello,
 
Upvoted. In addition, perhaps including the possibility of allowing installation as an option would also be a possibility.
Status changed to: Not Planned

Hi @TravisDahlheimer,

Thank you for taking the time to raise an idea.

Firstly, thanks for pointing out the error in our documentation since we moved the Core VBOs to the DX - I'll pass on this feedback to get the guide updated.

In terms of your main idea, I'm going to have to advise that this won't be something we'll take forwards. In Blue Prism Enterprise 7.3 we moved core VBOs to the DX for a few different reasons...

 

Firstly, locally shipped VBOs are always out of date as soon as even one of the VBOs have been updated, which happens much more frequently than customers traditionally upgrade. This means that historically there were always multiple versions of the same VBO floating around - there could be a currently imported version of the VBO, which was imported from the "shipped" VBO folder when the product was on an older version, the latest "shipped" version in the VBO folder if the product had been upgraded since last import and then the DX version of the VBOs. In this scenario, the DX would always be the place where users can find "the latest" and most stable version. To remove these problems, the solution was to remove the locally shipped VBOs and point all users to the DX. This also made sense because updates to these VBOs are now performed by the DX team, so moving them there made it easier for updates to be posted.

 

Importing the core VBOs by default into the Trial/Learning edition of Blue Prism Enterprise effectively reintroduces some (if not all) of these problems, so for this reason we'll not be taking this forwards. I hope this makes sense - please let me know if you have questions. Based on this response, I'm going to update this idea to Not Planned.

 

Regards,

Rob