CLI Import Error - You do not have permissions to edit this process

[JamesACA]

Hello,

I have a particular problem that I cannot seem to solve. I will try to add as much detail as possible but feel free to ask for more context.

Currently we are looking to integrate Azure DevOps pipelines to our release manager workflow. To do this the pushed release files will be stored on the application server where a service account (SVC-BP-R-ADM) will run a CLI to import the files. We have tested the CLI with various accounts (admin accounts and non admin). We created a new access group “G_RPA_R_Release” which is assigned to the user role “Release Manager”. The service account mentioned is in that access group.

When using the Blue Prism UI to do the import in QAB we did encounter a problem in the beginning because our folders in Studio had access rights assigned to them (image 1). Once we figured that out (image 2) we were able to do a successful release using the Blue Prism UI. When we go to the command line we get the same error as in image1 “You do not have permissions to edit this process”. The user role “release manager” was not changed from it’s default configuration. I can confirm the CLI working with “image3”. In that image the PowerShell on the left was opened as the SVC user (despite it saying ADM-Arruja) and for extra precaution I also configured to the script to run as a different use. This is all in our development environment. I temporarily assigned the release access group to the admin role and got the same error. We get the same problem in PreProduction, however there are no access rights assigned to those folders.

We want to get past the error in image 3.

Thank you,

image2iamge2image3

[david.l.morris]

@JamesACA

If you haven't edited the user role "Release Manager", I don't think it actually has enough permissions to do its job. Kind of weird to me, but that appears to be the case. I even checked in v7.4 just now, and an unedited user role of "Release Manager" cannot import releases containing processes or objects. Of course I could be just confusing myself since I only did a bit of testing.

Could you check the permissions given to the Release Manager user role and verify that it doesn't have the permissions Object Studio > Import Business Object and Process Studio > Import Process? If it doesn't have those permissions, then I would go ahead and add them along with any other imports that you need. For me, the Release Manager user role was already able to import Skills.

I'm not sure what to think about that you gave the admin role to the group and it didn't work then. I suspect that they didn't actually have the admin role synced into Blue Prism by the time you tested it. A Sys Admin can do anything. And while it of course could be some kind of bug, I would first assume it to be a permissions syncing issue there.

[JamesACA]

@david.l.morris thank you for the reply!

I verified and they do have those options selected. I tested with and without them before and no dice. I do find it strange about the sys admin role, and I might try again and get screenshots (for my own sanity). I do restart the servers after I change the user roles (I do not believe it is required, but I do it for good measure).  The most bizarre part to me is that with the UI it works and without the UI it doesn't work. 

Here are some more details not included in the original post. I did create 2 connection types: one that connects to the database and one that connects to the application server (itself). I did this because originally I wanted to run a test with a digital worker account and I could not log in (via the application server). I later put the pieces together that the connection type was different so I created a new connection. In my CLI I did try both connection types and neither worked.

I will let you know how things unfold and I am open to any thoughts!