Skip to main content

Use of PartOf in Hybris

Definition

 PartOf modifier is used to define the aggregation relationship between Parent and Child objects. To explain it better I would say PartOf is used to defining cascade delete. When we delete a Parent object then all its child objects(partOf) will be deleted automatically.
Why or When to use PartOf?
PartOf may make sense when the relationship involves "is part of" description. For example, an OrderEntry record(AbstractOrderEntry) is part of its parent Order(AbstractOrder), and older entries will never be shared between multiple orders. If the Order were to vanish, the OrderEntry should as well, and an order entry without an Order would be a problem.

How to use PartOf?
Looking into the following items.xml snippet we can able to understand the importance of PartOf
This also can be defined at the attribute level. Like
    <itemtype code="User"
              extends="Principal"
              jaloclass="de.hybris.platform.jalo.user.User"
              autocreate="true"
              generate="true">
        <deployment table="Users" typecode="4" propertytable="UserProps"/>
        <attributes>
            ...
            ...
            ...
            <attribute autocreate="true" qualifier="addresses" type="AddressCollection">
                <modifiers read="true" write="true" search="false" optional="true" partof="true"/>
                <persistence type="jalo"/>
            </attribute>
            <attribute autocreate="true" qualifier="carts" type="CartCollection">
                <modifiers read="true" write="true" search="false" optional="true" partof="true"/>
                <persistence type="jalo"/>
            </attribute>
        </attributes>
    </itemtype>

On the removal of an order, if we want to remove all associated order entries automatically, then we can define partOf in its relation like
 <relation code="AbstractOrder2AbstractOrderEntry" localized="false" generate="true" autocreate="true">
        <sourceElement type="AbstractOrder" qualifier="order" cardinality="one">
            <modifiers read="true" write="true" search="true" optional="true"/>
            <custom-properties>
                <property name="ordering.attribute">
                    <value>"entryNumber"</value>
                </property>
            </custom-properties>
        </sourceElement>
        <targetElement type="AbstractOrderEntry" qualifier="entries" cardinality="many" collectiontype="list"
                       ordered="false">
            <modifiers read="true" write="true" search="true" optional="true" partof="true"/>
        </targetElement>
    </relation>

Comments

Post a Comment

Popular posts from this blog

Performance Improvement in Hybris eCommerce

Below points will specially help   grocery   based projects where adding   50-60 products per cart   is a common trend and where   complex promotions   are used using   drools   engine. Add/Update to cart     à   In OOB Hybris whenever any new product is added to cart or quantity of existing product is updated in cart (from PLP, PDP, Search page etc) then calculateCart() method is called in order to calculate total price of the cart. This call can be prevented (to increase   performance ) in case the business requirement is to just show notification of add to cart without total price in minicart. View Cart   à   In case 50-60 products are added in cart and approx. 30% of the products have promotions applied then OOB Hybris view cart can take between 10-15 seconds to load (based on complexity of promotion). In order to avoid custom waiting 10-15 sec to see view cart this operation of can be split into below 3 steps so that every 3-4 seconds rendering of data starts and custom
Post a Comment
Read more

SmartEdit & its Personalization in Hybris

SmartEdit introduced  in 6.0 Hybris version and  Personalization (based on SmartEdit)  enabled in 6.1 Hybris version Onwards . SAP Commerce SmartEdit allows content managers to easily create and manage their website content on-the-fly in different inflection points and make it available to their customers with the click of a button. Personalization (based on SmartEdit) provides an integrated, user-friendly way of building experiences that are relevant to your customers, which is key to driving engagement and conversion.  Personalization encompasses modules and extensions that facilitate using Personalization Mode in SmartEdit to create a fully customized user experience. Personalization capabilities work across both content and commerce in an integrated way, so that you can build customer experiences consistently across channels and functionality. Using SmartEdit for Customer Experience, you can see the end-customer experience as you build it, all the while working in one set o
Post a Comment
Read more