In my model driven app, I have made a custom security role named "Budget" it was copied over from the default basic app user security role and granted permissions to the main "Request" table in my solution and I added organization level permissions for the (create, read, write, append, append to, share) operations on this Request table and then gave it organizations permissions for the business process flow associated with it. The way that the business process flow works is that on select stages, it assigns ownership to different teams for the request record. I have a team named Budget Team that has this Budget security role assigned to it. The Budget business unit is near the root business unit. My problem here is that once it gets to our "Budget Approval stage" and the request record gets assigned to the Budget team and the budget team is done modifying the record and saving it, they cannot click on the "next stage" button found in the business process flow because that same button automatically defaults to "Finish" even though it meets the condition to transition to the same stage.
For some users of our solution, it will allow them to click on next stage but for other users, that button will automatically default to finish. When we compared these users (security roles, teams, business units) they were all the same. No matter how many times we hard refreshed the browser this behavior kept repeating itself and I'm curious to know if anyone else has faced an issue similar to this and knows the fix for this. Any help would be appreciated.
5
Share
Report
All responses (
Answers (
