Hi Everyone, I'm wondering about best practices here, and want to avoid going down a route that might lead to pain and suffering.
I need to track three custom pieces of data per sales order. This data is used for contacting the customer for payment. One piece of data is a purchase order number, then there are two others that are tracking numbers specific to the customer's payment system. This data is required to be "not-null". I've extended OrderHeader. Problem is, the order entry screens will fail at the end, because of the not-null constraint. (I added the constraints manually, due to a bug OFBIZ-6493) I started digging into the finalizeOrder request chain. I'd like to capture these three pieces of data on the setBilling screen that is part of finalizeOrder chain. It appears I'd need to do some pretty heavy lifting to augment this process, including modifying the ShoppingCart class, etc. Obviously someone has had to do this before, so just wondering if there are any best practices to avoid modifying the Java classes. -Forrest
