Unlocking Wizard Restricted by User Role Access Using MTE

[JenniferGueldne]

At any given time, our organization has a large number of developers working within different business frameworks simultaneously in the DEV environment. Thus, our organization relies heavily on MTE to lock down content in the Studio between these different businesses. There are, however, seemingly serious gaps in the extension of MTE to the Unlocking Wizard.

When a user wishes to unlock a process, they are presented with the option to "unlock all processes" or "unlock selected processes." Regardless of which of these options the user selects or the content restrictions imposed by MTE and their user role, through the Unlocking Wizard, they have access to unlock ANY of the processes in the DEV environment. This poses a serious problem to any other developers currently working in DEV as it releases the lock their process and forces them to seek alternative methods in order to preserve their work.

MTE should be extended to the Unlocking Wizard to prevent users from unlocking processes that they should not have access to per the MTE restrictions imposed by their user role. This would significantly reduce risk in large organizations and protect on-going development work.

[robert.nicklin]

Hi Jennifer,

This has been addressed in the release of Blue Prism 6.6 and can be seen in the release notes on page 17. The release note for this particular item reads:

"An issue that allowed objects and processes being edited by a user to be unlocked by a user who did not have the appropriate permissions has been resolved."