Environment Neutral Version History IDs

[Jeff__Addinell]

Currently it can be challenging to match the active version of a process/object in the production environment with the version history item in the development environment that it was imported from. Please see the post "Cross Environment Version Control" in the Product Forum for more detail.

The idea is for the Blue Prism product to display an ID column in the Version History table of each process/object. Blue Prism would ensure that this ID is globally unique. This ID would be preserved when importing process/objects into other Blue Prism environments. Because the ID is preserved it is then simple to say which version in one environment matches with which version in a different environment.

This could be implemented in a number of ways:

1. These IDs could be user-inputted as an optional field within the existing with Blue Prism Save dialog with Blue Prism ensuring global uniqueness, or

2. These IDs could be automatically assigned GUID values by Blue Prism

[Jeff__Addinell]

EDIT: The first implementation method (user-inputted IDs) actually would not need to be globally unique, just unique over the scope of the process/object in question.