Dynamic kit and predefined dynamic kit data assets with the Sterling Configurator integration

Dynamic kit data assets and predefined dynamic kit data assets are created in the same way as other catalog assets.

Before creating dynamic kit data assets or predefined dynamic kit data assets, review the relationship between dynamic kits and predefined dynamic kits.

Both dynamic kits and predefined dynamic kits are catalog entries. A predefined dynamic kit is defined as a child catalog entry of a dynamic kit and can only be associated with one dynamic kit. A dynamic kit can be associated with multiple predefined dynamic kits.

The definition of a dynamic kit must include a model. The model definition is shared with the dynamic kit's child predefined dynamic kits.

Multiple components can be defined for a predefined dynamic kit, and different predefined dynamic kits can have different components.

The CATRELTYPE table describes containment relationships between catalog entries. For example, a dynamic kit can "contain" multiple child predefined dynamic kits; a predefined dynamic kit "contains" components. In the CATRELTYPE table, the dynamic kit and predefined dynamic kit relationship is defined as DK_PDK. The predefined dynamic kit and component relationship is defined as PDK_COMPONENT.

Here is a sample XML definition of a dynamic kit and a predefined dynamic kit:


<!-- 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 a Catalog Entry for the Predefined Dynamic Kit -->
<catentry catentry_id="10552" baseitem_id="10552"
member_id="70000" catenttype_id="PredDynaKitBean" partnumber="MYPDK-0101" mfname="IBM"
markfordelete="0" buyable="1" />
<catentdesc catentry_id="10552" language_id="-1" available="1"
published="1" name="MYPDK-0101" shortdescription="MYPDK-0101PDK" />
<itemspc baseitem_id="10552" itemspc_id="10552"
member_id="70000" partnumber="MYPDK-0101" markfordelete="0" discontinued="N" />
<baseitem baseitem_id="10552" member_id="70000"
partnumber="MYPDK-0101" itemtype_id="ITEM" quantitymeasure="C62" markfordelete="0"
quantitymultiple="1.0" />

Here is an example of how to define a predefined or base configuration:

<!-- Define the base configuration for your Dynamic Kit -->
<catreltype catreltype_id="DK_PDK"
description="The dynamickit to predefined dynamickit relationship" />
<catentrel catentry_id_parent="10551" catentry_id_child="10552"
catreltype_id="DK_PDK" quantity="1" sequence="1"/>

<catreltype catreltype_id="PDK_COMPONENT"
description="The predefined dynamickit to components relationship" />

<catentrel catentry_id_parent="10552" catentry_id_child="1011"
catreltype_id="PDK_COMPONENT" quantity="1" sequence="1"/>
<catentrel catentry_id_parent="10552" catentry_id_child="1012"
catreltype_id="PDK_COMPONENT" quantity="1" sequence="2"/>