You’re offline. This is a read only version of the page.
48
"Our organization uses D365FO and is configuring workflows for Purchase Requisitions, Purchase Orders, Vendor Invoices, and Expense Reports. We are leveraging the Signing Limits functionality and Managerial Hierarchy to route documents for approval based on dollar amounts and a worker's authority.
Since D365FO requires a separate workflow configuration for each document type, we anticipate maintaining four or more distinct workflows (PR, PO, Invoice, Expense) that essentially use the same core logic (i.e., route to the first manager in the hierarchy with the authority to approve the amount).
Is there a standard or recommended approach (e.g., using a single X++ class, a Power Automate flow that feeds back to D365FO, or a consistent workflow template) to centrally manage or enforce the identical approval logic across these multiple document-specific workflows?
For those who have implemented this, what are the best practices for minimizing maintenance when the signing limit rules or approval matrix changes (e.g., updating a rule once versus updating four separate workflow configurations)?
Are there any limitations or pitfalls when relying solely on the Managerial Hierarchy and Signing Limits for all these different document workflows that we should be aware of?
We are seeking solutions to improve governance and reduce the administrative burden of maintaining multiple, identical workflow designs."
Share
Report
All responses (
Answers (
