cancel
Showing results for 
Search instead for 
Did you mean: 
asilarow
MVP
Status: New

Currently, the Blue Prism studio is heavily reliant on an active connection to the SQL database.

This can be problematic, especially for remote workers in areas of poor internet connectivity (like on a train).

It could be modified, to run a LocalSQLDB by default (same as the learning edition does), and save the changes there in the first instance, syncing to the SQL server database whenever the connection is available - think cloud save games here.

 It would of course require additional config like version checks, user locks, concurrent saves, etc... but would definitely improve the Enterprise version user experience. 

4 Comments
Rambo27
Level 8

@asilarow Great thought 😀

Walter.Koller
Level 12

I can imagine this but it probably needs a full fletched versioning control system with merge, diff, conflict resolution, ... 

What will be challenging is keeping audit trails in sync though and ensuring license limitations.

There is always the possibility to create your own local DB and import the objects from central repository. Then work locally and afterwards export from local DB to central repository when finished. 

Denis__Dennehy
Level 16

Good idea but might be complex to build.

I always had a local database on my laptop just for this offline on a train scenario. Grab free SQL Server Express, create a new BP database connection pointing to it,  import a release with everthing you want to work on before travel.

In reality you are still hamstrung on the train because most applications you want to work on are also not available because of no network, so all you can reliably work on is process logic and stubbing out objects to save time when you have a reliable network.

Good idea!!