Dynamic kit data assets
Dynamic kits data assets are created in the same way as other catalog assets. The dynamic kit components must have their own SKUs as does the dynamic kit.
This information does not apply to the Sterling Configurator dynamic kit integration.
You must decide how and where you want to store information about which components go with which dynamic kits. WebSphere Commerce does not provide database tables or rules for you store this information.
Configuration of dynamic kits must be handled outside of WebSphere by a product configurator.
By default, the only relationship information WebSphere Commerce can store about dynamic kits is a predefined or base configuration of a dynamic kit. Entries the CATENTREL table indicate which components belong to the predefined or base configuration.
<!-- Define a Catalog Entry for the Dynamic Kit -->
<catentry catentry_id="10551" baseitem_id="10551"
member_id="70000" catenttype_id="DynamicKitBean" partnumber="MYKIT-0101" mfname="IBM"
markfordelete="0" buyable="1" />
<catentdesc catentry_id="10551" language_id="-1" available="1"
published="1" name="MYKIT-0101" shortdescription="MYKIT-0101DynamicKit" />
<itemspc baseitem_id="10551" itemspc_id="10551"
member_id="70000" partnumber="MYKIT-0101" markfordelete="0" discontinued="N" />
<baseitem baseitem_id="10551" member_id="70000"
partnumber="MYKIT-0101" itemtype_id="ITEM" quantitymeasure="C62" markfordelete="0"
quantitymultiple="1.0" />
<!-- Define the base configuration for your Dynamic Kit -->
<catreltype catreltype_id="DYNAMICKIT_COMPONENT"
description="The predefined dynamickit to component relationship" />
<catentrel catentry_id_parent="10551" catentry_id_child="1011"
catreltype_id="DYNAMICKIT_COMPONENT" quantity="1" sequence="1"/>
<catentrel catentry_id_parent="10551" catentry_id_child="1012"
catreltype_id="DYNAMICKIT_COMPONENT" quantity="1" sequence="2"/>