Docs  /  NVXEAW Extended Approval Workflow  /  Tasks

Document specific approval workflows

2024/04/26 • 2 min. to read
In BC Standard, it's not possible to setup an Approval Workflow which fetches the required approvers directly within the purchase / sales document. In the Purchase Header and Sales Header tables, as well as on all related pages two new fields were added:

Approver Type	You can choose between the values: "Blank", "User", "Workflow User Group"
Approver Code	Depending on the “Approver Type”, either an individual user or a workflow user group (group of multiple users) can be selected.

Link: Related Pages These 2 fields have the following logic: • Both fields are non-editable. • Both fields may only be changed if the status of the Purchase / Sales Header is OPEN • A new logic and function is implemented, which automatically creates and assigns a “Workflow User Group” to a specific Purchase / Sales Header based on defined rules and settings. The assigned BC Approval Workflows will be send to the Users as defined in these new fields “Approver Type” and “Approver Code”. In the workflow table in BC a new “Approver Type” option: Document Specific was added. If this Approver Type "Document Specific" is set, the approval must always be sent to the user or workflow user group as specified in the Purchase/Sales Header in the new fields “Approver Type” and “Approver Code” The feature Customizing Execution of Approvals the assigned User / Workflow User Group will be used and considered when executing the Approval Workflow.

Approver Limit Type

//TODO