|
The more complex the OLC to suit the flexibility of the builders needs, the greater chance there will be required yet missing fields. We use a system of assigning both a proofer AND a balancer to verify a zone before it's actually published. This seems to work well for us, but even so there are occasional missed things just because of the sheer scope.
Would it be reasonable to 'force' a minimum of specific field entries like weight, material_type, value, alias and general name before OLC can be quit and saved?
|