, I ran a full approval test from a Purchase Reque...
# ask-stanley-ai
m
, I ran a full approval test from a Purchase Request (PR) to a Purchase Order (PO), using only Employee Center roles. What I noticed is that PO approval doesn’t fully work from the Employee Center. Access to the PO is limited to: • The user who originally created the PR • The PR approver (typically the supervisor) The PO approval workflow is triggered, but any other approvers (e.g. second level or beyond) cannot act on the PO from the Employee Center. They get a permission error when trying to access the PO (insuffisant permission ). Is this expected behavior in NetSuite? And if so, what would be the recommended way to allow multi-level PO approval involving Employee Center users?
c
AI generated answer (using internal Slack threads):
Based on the conversations, it appears that the behavior you're experiencing is expected in NetSuite. The Employee Center role is designed to limit access to certain functionalities, including the ability to approve Purchase Orders (POs). This is to ensure that only authorized personnel can approve these transactions. However, there are ways to work around this limitation. One common method is to create a custom approval process using workflows. This allows you to set your own rules and approval hierarchy, which can include Employee Center users. For example, you could create a workflow that triggers when a PO is created. This workflow could then send an approval request to the appropriate approver(s), based on your business rules. The approver(s) could then approve the PO directly from the workflow email, without needing to access the PO record in NetSuite. Please note that creating custom workflows requires a good understanding of NetSuite's workflow engine and may require some SuiteScript coding. If you're not comfortable with this, you may want to consider hiring a NetSuite professional to assist you. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******
Slack thread 1: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.882532537
Slack thread 2: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.87062639
Slack thread 3: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.868640721
Please provide your feedback on this answer.