Looks good, +1 for changes history
BTW this should have better been in dev ML ;o)

Jacques

From: "Jacopo Cappellato" <[EMAIL PROTECTED]>
Bilgin,

it looks like a good start but I would like to get some feedback from others too. Also, it would be a good idea to add fields to store the quantity, cancelled units, unit price so that we can keep a record if they are changed: the fields will be populated only if the data in the OrderItem is changed.

Jacopo

On May 7, 2008, at 5:54 PM, Bilgin Ibryam wrote:

Jacopo, thanks for the suggestions.

As you said using OrderHeaderNote is a bit hacky solution, but extending OrderHeaderNote enity the way you suggested would allow us adding order
notes per order item. May be I can extend it later.

I think using "OrderItemChange" entity is a better way to go.
Do you mean something like this:

   <entity entity-name="OrderItemChange"
           package-name="org.ofbiz.order.order"
           never-cache="true"
           title="Order Item Change Entity">
     <field name="orderItemChangeId" type="id-ne"></field>
     <field name="orderItemChangeTypeId" type="id-ne"></field>
     <field name="orderId" type="id-ne"></field>
     <field name="orderItemSeqId" type="id-ne"></field>
     <field name="reasonEnumId" type="id"></field>
     <field name="comments" type="comment"></field>
     <prim-key field="orderItemChangeId"/>
     <relation type="one" fk-name="ORDER_ITCH_TYPE"
rel-entity-name="OrderItemChangeType">
       <key-map field-name="orderItemChangeTypeId"/>
     </relation>
     <relation type="one-nofk" rel-entity-name="OrderHeader">
       <key-map field-name="orderId"/>
     </relation>
     <relation type="one" fk-name="ORDER_ITCH_OITM"
rel-entity-name="OrderItem">
       <key-map field-name="orderId"/>
       <key-map field-name="orderItemSeqId"/>
     </relation>
     <relation type="one" fk-name="ORDER_ITCH_REAS" title="Reason"
rel-entity-name="Enumeration">
         <key-map field-name="reasonEnumId" rel-field-name="enumId"/>
     </relation>
   </entity>
   <entity entity-name="OrderItemChangeType"
           package-name="org.ofbiz.order.order"
           title="Order Item Change Type Entity">
     <field name="orderItemChangeTypeId" type="id-ne"></field>
     <field name="hasTable" type="indicator"></field>
     <field name="description" type="description"></field>
     <prim-key field="orderItemChangeTypeId"/>
   </entity>

What do you think about these entities? Should I commit them? Any other
solutions?

Thanks in advance
Bilgin


Reply via email to