When using the Approval Workflows for Vendors, Customers and Items (Vendor Approval Workflow, Customer Approval Workflow and Item Approval Workflow) - typically this is used for newly created records.
The new record can still be used on a range of Purchase and Sales documents, BEFORE it is approved.
For example, you can create a Purchase Order for a vendor that is NOT yet approved and then send/email the Purchase Order to the vendor, before the vendor is approved.
Ideally, there needs to be a complete block (restriction) so that you cannot insert a new customer, vendor or item record until suck time is the required approval is done.
Comments
I also recognise and support this idea, especially for vendor approvals, where this comes through regularly in colleague and customer feedback.It seems more efficient and safe to prevent a vendor/customer/item being used until it's approved, or at least offer that option. You could argue that the likes of Purchase Document approval workflows are a way to prevent e.g. PO's being released before vendor approval, but this still allows the user to spend time preparing a PO before realising it can't be sent to the vendor (yet), and you're relying on approver(s) to know that the relevant vendor hasn't been approved yet.
Category: General
Having control of maker checker over customer, vendor and item master is highly important to avoid the errors as all your transaction runs around these 3 components majorly.
Category: General
Business Central Team (administrator)
Thank you for this suggestion! Currently this is not on our roadmap. We are tracking this idea and if it gathers more votes and comments we will consider it in the future. Best regards, Business Central Team