Hi Lizzeth,I am assuming this is not the issue, but wanted to mention it regardless because it has caused issues for us in the past with approvals.. The employee doing the approval (and whoever is submitting) needs employee records that are linked to the user, and it won't work without that link. Again, I don't think this is the issue here, but it's on my checklist when investigating security issues and I thought I'd mention it..Thanks.
After reviewing the task recording I have some feedback.
The first recording you sent points to the WorkflowWorkList form, this form is unique in that because of its design it has to handle workflows from all over the system. When this happens within AX, Microsoft has a couple different options to handle security. Sometimes they do it in code (like when deleting an address) but in this case they actually do it in data.
The datasource for this form is the WorkflowWorkItemTable, on this table is actually a column named MenuItemName. This column is used to determine which menu item should be used for this particular workflow (they are all of type Display). Which workflows a user's sees on this page is based on which menu items they are assigned. So for example, if you assign the user Read permission to the PurchReqTable menu item display, they would be able to see Purchase Requisition workflows.
If you've found this thread useful, dive deeper into User Group community content by role