cancel
Showing results for 
Search instead for 
Did you mean: 

Version Control in bluprism

Anonymous
Not applicable
I'm starting this forum with regards to version control in blueprism to allow access of modifying an object/process same time by multiple users. Suppose if one person is working on a process(say process 'A') and if some other person wants to work on the same process(process 'A'), we don't have a flexibility of the same unless any one of the person has to close/complete working on the process. it would be helpful if we have multiple users access for a process/object at the same time similar to version controlling concept
4 REPLIES 4

AndreyKudinov
Level 10
If two users change process at the same time, how do you suggest conflict resolution should work? Consider splitting big process in smaller parts to avoid locking whole process for changes.

Anonymous
Not applicable
This is for what we will have version controlling. Everytime a user check-in his/her code to sever a version will be assigned to it and everytime a new user wants to edit the code he/she will download the latest version from server to their local machine. Once modification done, again the updated code is check-in to the server with the new version number

AmiBarrett
Level 12
The most feasible way of doing this would be for them to frequently do live updates (like you'd see on a Google Doc), rather than version controlling. Otherwise, there's too much potential for code collision. Unfortunately, Blue Prism isn't exactly the most efficient at doing its transactions, especially if the resources connect to the controller before they go to the DB. This would also require a redesign of their version history system. Probably the only way around that would be to introduce a secondary master/slave system, but that's probably way too complex for them to implement.

Shruti_AnilNark
Level 4
The main aim of Blue Prism is simplify the processes that we build. I completed the Advanced Consolidated Exercise and it emphasizes on the breaking of a big functionality into many small objects. So technically the way it is designed to work efficiently doesn't require a Github standard coding repository.