Problem

BC Customer/Vendor workflows require users to submit for approval before a restricted record is created for the customer/vendor.

Example

Even with Vendor Approval Workflows enabled, I could create a vendor in my name, post a bogus invoice, and cut a check without requesting approval for the vendor.

Solution

If the Customer/Vendor Approval Workflow is enabled, add a Restricted Record upon insertion of the record. At the end of the approval process, all restrictions are removed (not just the one imposed by the workflow).

It is a shame that I had to build this extension to resolve this deficiency. It should be common sense that workflow-enabled customers and vendors should not rely on the honor system for a user to submit said record for approval before restricting it.

Bonus Points

Add a table that allows for users to select the one or many customer/vendor fields that should trigger modification restrictions. Current approval workflows. There currently exists a stock workflow that triggers when records are modified, but users can only conditionally proc this workflow on one field at a time.