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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.