I agree with David, I wondered why you did use the Extensibility Pattern, but
thought you had a good reason.
I wondered also if you plan to provide UI(s) for the changeReason ? Would you
use only a dropdown using enumerations from the
Enumerations entity ? Maybe a text field (area?) to allow user to explain more
could be used ? A kind of Note if you like.
Jacques
from.: "David E Jones" <[EMAIL PROTECTED]>
It might be good to simplify it a little and use a changeTypeEnumId (or the
like) instead of the type field and related entity.
There is probably nothing special we would want to add to the type entity, so
the Enumeration, with a special EnumeractionType,
is adequate.
-David
On May 10, 2008, at 2:07 AM, Bilgin Ibryam wrote:
Hi everybody,
there was a small discussion in the user list about the need of a new
entity for storing the changes done on order items.
You can find the discussion here and the new entity in OFBIZ-1773
http://www.nabble.com/Where-to-store-the-reason-for-canceling-some-quantity-of-Order-Item-to17101121.html
Any other comments before I commit it?
Thanks,
Bilgin
