Hi all!
I have been encountering the issue mentioned in the title for the first time. I'm currently building a Portal that serves as a starting point for a registration. One of the requirements is that the user can choose from 12 different languages, so I set up a record with the translation sets (since most of the locales are not supported by Appian). I created a service account for the Portal and gave it Viewer permission for the Record as well as the PM that is started from the form.
Initially, it worked, and you could start the Process from the web portal successfully with the provided data. But for some reason none of the underlying record data can be queried anymore, and starting the PM after filling out the required info doesn't either.
I attempted to find the source of the error in the portal log files but I'm seeing an ERROR <timestamp> Service account does not have access to record.
Not really descriptive, but I reviewed the service account's permissions in the Portal object and everything seems to check out. What other troubleshooting can I perform before having to open a case with Appian?
Thank you in advance,
Matthias
Discussion posts and replies are publicly visible
Hi Matthias Can you add the service account user to a group that has viewer rights to the record and process model and retry if it works.
Hi Matthias Brixius Please add service account to your Admin Group this will solve your issue.
Caution here to take is the Admin group should not have additional actions/privileges on portal which you might not want the basic users to access as part of service account user.
You can ask Appian support to add any required locales.
Thank you Stefan, that is an interesting tidbit of information! I'll keep that in mind for future development
Hello Harsha, thank you for the suggestion. I reviewed the permissions and even tested in the Record whether or not the specific service account user has access to the records. The user can see 100% of the records, so it would seem the issue lies elsewhere?
For the fun of it, I did attempt this. Sadly, no change in behaviour whatsover. On a hunch I also added the service account to the database group, which also made no difference
May be try changing the service account permission to process model as initiator instead of viewer.
Matthias Brixius what is the type of your service account?
Quick update: the solution was unpublishing the portal completely and publishing it again... weird issue.