I created page approval workflow for one of our SharePoint site. The workflow works fine when I login as Global Admin user. However, When regular users try to submit page for approval, they get stuck at following screen. The continue button is disabled and does not allow users to Submit the request.
Solved! Go to Solution.
Hi @imran7799 ,
Service is healthy. Please try again.
I'm not seeing a screenshot, but I suspect the problem is with the user's permissions. I've seen this before when running a flow to approve and item that has Require Approval turned on in the list. In order to kick off such a flow on a selected item (page) the user has to have Approver permission to that document library. I suspect that may be your problem.
For some reason it did not liked my image. Here is the screenshot attached.
I understand users would need approval privileges to approve the item. But in my case users are not able to even submit the workflow for approval. With respect to permission, the user I am testing with is has site owners (full access) on the site.
Still not seeing an attachment.
Are you saying that it doesn't work when trying to do it as a Site Owner? If so I don't know what's wrong. But if it works for the site owner, but not the regular users then it would be a permissions issue. As I said, for a selected file trigger the flow will run in the user's context so the user needs to be able to make the approval changes in the flow. Regular users can't update the Approval column, only approvers can do that.
Are you using a template? There may have been changes to the actions that affect the functionality of the flow.
I have found the issue to be that the user who wishes to submit a request for approval requires their permission level to have 'Approved Items - Approve a minor version of a list item or document.' checked.
Without this, they can only establish a SharePoint connection, and cannot proceed to create the Approval and Notification part of the approval flow.
I did some more testing and this appears to be a regression bug. It happens to any flow using the selected file trigger with approvals, even the built-in request sign-off flow. I have reported it to Microsoft and will let you know when I hear something back.
@Pstork1 : Thanks. I think this is tenant specific as well, because I have implemented this flow for other clients and it's working fine there.
I think its probably due to changes made to either selected file trigger or approvals action in the last few months. It has worked for me in the past also. So existing flows built earlier in other tenants may work fine. But the ones built with current actions may not. So I don't think its tenant specific.
Tested with a new flow or an existing approval flow?
ISV Studio is designed to become the go-to Power Platform destination for ISV’s to monitor & manage published applications.
See the latest Power Automate innovations, updates, and demos from the Microsoft Business Applications Launch Event.
Find your favorite faces from the community presenting at the Power Platform Community Conference!