svn commit: r684812 - /ofbiz/trunk/applications/order/entitydef/entitymodel.xml

Author: jleroux
Date: Mon Aug 11 09:54:39 2008
New Revision: 684812

URL: http://svn.apache.org/viewvc?rev=684812&view=rev
Log:
Some fields descriptions from BJ comments on user ML

Modified:
    ofbiz/trunk/applications/order/entitydef/entitymodel.xml

Modified: ofbiz/trunk/applications/order/entitydef/entitymodel.xml
URL: http://svn.apache.org/viewvc/ofbiz/trunk/applications/order/entitydef/entitymodel.xml?rev=684812&r1=684811&r2=684812&view=diff
==============================================================================
--- ofbiz/trunk/applications/order/entitydef/entitymodel.xml (original)
+++ ofbiz/trunk/applications/order/entitydef/entitymodel.xml Mon Aug 11 09:54:39 2008
@@ -1617,26 +1617,50 @@
       <field name="statusId" type="id"></field>
       <field name="fromPartyId" type="id"></field>
       <field name="priority" type="numeric"></field>
-      <field name="custRequestDate" type="date-time"></field>
-      <field name="responseRequiredDate" type="date-time"></field>
+      <field name="custRequestDate" type="date-time">
+        <description>
+          Created date and custRequestDate most likely are the same. To be checked...          
+        </description>
+      </field>
+      <field name="responseRequiredDate" type="date-time">
+        <description>
+          responseRequiredDate is the time the customer needs a response.
+        </description>
+      </field>
       <field name="custRequestName" type="name"></field>
       <field name="description" type="description"></field>
       <field name="maximumAmountUomId" type="id"></field>
       <field name="productStoreId" type="id"></field>
       <field name="salesChannelEnumId" type="id"></field>
       <field name="fulfillContactMechId" type="id">
-          <description>
-              Field to support a location of a cust request--ie, product literature sent to an address, service call at a localtion, etc.
-          </description>
+        <description>
+          Field to support a location of a cust request--ie, product literature sent to an address, service call at a localtion, etc.
+        </description>
       </field>
       <field name="currencyUomId" type="id"></field>
-      <field name="openDateTime" type="date-time"></field>
-      <field name="closedDateTime" type="date-time"></field>
+      <field name="openDateTime" type="date-time">
+        <description>
+        Used when the customer service person responsible for the request open it for action.
+        Then you take the customer requestdate and openDateTime to see the efficiency of the customer service people.
+        </description>
+      </field>
+      <field name="closedDateTime" type="date-time">
+        <description>
+          Used when the customer service person responsible for the request close it as resolution
+          In some customer response systems, the openDateTime and closedDateTime can happen more than once as the customer is not satified
+          with the resolution.          
+        </description>
+      </field>
       <field name="internalComment" type="comment"></field>
       <field name="reason" type="description"></field>
       <field name="createdDate" type="date-time"></field>
       <field name="createdByUserLogin" type="id-vlong"></field>
-      <field name="lastModifiedDate" type="date-time"></field>
+      <field name="lastModifiedDate" type="date-time">
+        <description>
+          Last modified date can be till the closedDateTime which is when the customer service people say it is resolved.
+          This gives when the last action was done to see if the steps to resolve the request are happening in a timely manner.              
+        </description>
+      </field>
       <field name="lastModifiedByUserLogin" type="id-vlong"></field>
       <prim-key field="custRequestId"/>
       <relation type="one" fk-name="CUST_REQ_TYPE" rel-entity-name="CustRequestType">