4 Replies Latest reply on Sep 12, 2013 10:12 PM by Gopinath Ramasamy

    ATG extending OOTB enumerated data type

    PrincessPoonam

      Hi All,

        

      If i have to add a extra payment group/option to an data-type="enumerated" in ATG repository, should we ,

       

      1) Use the OOTB table in our extended orderRepository.xml???? Coz ATG recomends to use auxiliary when extending the OOTB properties.

      2)Should we mention all the OOTB options along with my custom option????

      3) Will there be any SQL change for adding a extra option in the enumarated data-type????

      4)Can you please let me know more about  data-type="enumerated" .

        

      <item-descriptor name="paymentGroup" sub-type-property="type" version-property="version" expert="true" cache-mode="simple" display-name-resource="itemDescriptorPaymentGroup" item-cache-timeout="180000">

      <table name="dcspp_pay_group" type="primary" id-column-name="payment_group_id">

            <attribute name="resourceBundle" value="atg.commerce.OrderRepositoryTemplateResources"/>

           <property name="type" data-type="enumerated" default="paymentGroup" expert="true" category-resource="categoryInfo" display-name-resource="type">

              <attribute name="useCodeForValue" value="false"/>

              <option value="paymentGroup" code="0"/>

              <option value="creditCard" code="1"/>

              <option value="giftCertificate" code="2"/>

              <option value="storeCredit" code="3"/>

               <option value="MyPaymentGroup" code="3"/>

              <option value="invoiceRequest" code="5000"/>

              <attribute name="resourceBundle" value="atg.commerce.OrderRepositoryTemplateResources"/>

              <attribute name="propertySortPriority" value="10"/>

            </property>

      ..............................................................

      </table>

       

      Regards