Appian Community and Appian Academy are being upgraded. As a part of the upgrade, Appian Community is currently in read-only mode, and user registration is disabled until August 3. We apologize for any inconvenience this may cause, but a more secure, stable, and performant Community experience is coming soon!
The new Appian Community launches August 3, followed by Appian Academy on August 7. During the migration, Appian Community Edition, Appian Academy, Documentation, Certifications, Instructor-led Customer Training, Partner Sales Training & Accreditation, and Forum (for Appian Partners and Customers only) will remain available.
Hi,
I am trying to call the Appian RPA robotic process from Appian. I have created a connected system and integration object. In the integration object i have selected the operation as 'Execute Robotic process' but I don't see any robotic processes to select.
The following message is displayed there "You do not have permission to retrieve the list of robotic processes.".
I could see the robotic processes when I login to RPA with same login and I have the same permissions to resource, user and robotic process. I do not know what is missing here. Please advise.
Discussion posts and replies are publicly visible
The permission that matters are the permissions on the service account. Under 'Users' in the RPA console, make sure your service account has the correct permissions tags
Hi Danny, Thanks for your response.
I do have the same issue. Can you confirm what all permissions needs to validated to resolve this issue.
Hi Abhay - this may be caused by having robotic process permissions that do not match your resource permissions.
You can check the Appian RPA permissions for the Users, Robotic Processes and Resources in the Appian RPA Console menus by clicking on the lock (Permissions) icon in the Actions column.
You can check the service account user type under Security in the Admin Console, and verify the user is a member of the Service Accounts group.
See the following for details:
docs.appian.com/.../security.html
Thanks Randall Richeson. It seems the user permission was missing. It worked after I corrected it.