Merging / Migrating / Combining User Session Data (Cart Merge while User Logon in Websphere Commerce)

-
Cart Merge while User Logon in Websphere Commerce

MigrateUserEntriesCmdImpl

MigrateUserEntriesCmd will not do merge. It just migrates guest user details to current logged in user. We will have to use OrderItemMoveCmd for merge. OrderitemMoveCmd can only merge different orders of same customer only. That’s the reason we call MigrateUserEntriesCmd from LogonCmd first, followed by OrderItemMoveCmd.

Consider the below order flow.

Register a new user "testuser" in the site and logout before adding any items to cart.Come back to the site as a guest user.Add an item to cart .During checkout   try to login as "testuser" registered before.Order\OrderItems memberId will be changed from guest to that of registered user. There willn't be any order left for the Guest user.This can be achived with the help of MigrateUserEntriesCmdImpl.

This task command is used to migrate resources owned by one user to another. The mandatory resources that are migrated are Addresses.By default, this command will not merge the shopping cart for the 2 users.For e.g it does not do anything if the logged in user has a previous shopping cart. That scenario is handled with  the help of OrderitemMoveCmd.


OrderItemMoveCmdImpl

Consider the below order flow.

Come to the site as a registerd user and add items to cart .Logout from the site.Now the registered user has a pending order.Again come to the site as as guest user and add an item to cart.During Check out   login as registred user "testuser".The guest order will be removed and items will be copied to the registered user.For that reason we will call logonCmd which will call MigrateuserentriesCmd (Which copies items from guest to registered)followd by OrderItemMoveCmd.

Customize the
Stores\WebContent\StoreFronAssetStore\UserArea\AccountSection\LogonSubsectionUser\UserLogonForm.jsp file.

In the UserLogonForm.jsp file, replace

<input type="hidden" name="URL" value="<c:out value="${continueAfterLogonURL}"/>" id="WC_UserLogonForm_FormInput_URL_In_Logon_1"/>


With the following code snippet:

<c:url var="orderMove" value="OrderItemMove">
<c:param name="URL" value="OrderCalculate?URL=StoreCatalogDisplay"/>
<c:param name="page" value="account"/>
<c:param name="fromOrderId" value="*"/>
<c:param name="toOrderId" value="."/>
<c:param name="deleteIfEmpty" value="*"/>
<c:param name="continue" value="1"/>
<c:param name="createIfEmpty" value="1"/>
<c:param name="calculationUsageId" value="-1"/>
<c:param name="updatePrices" value="1"/>
<c:param name="storeId" value="${storeId}"/>
</c:url>
<input type="hidden" name="URL" value="<c:out value='${orderMove}' />" id="WC_RememberMeLogonForm_FormInput_URL_In_Logon_1" />

Comments

Post a Comment

Popular posts from this blog

Websphere Commerce Data Load using CSV \Websphere Commerce Data Load using XML

-
Websphere Commerce Data Load using CSV \Websphere Commerce Data Load using XML Data can be loaded into WCS tables using data load utility. Data load utility works in the steps as mentioned below. 1.Data Reader The data reader reads the input file, and transforms the input into a data object. Data objects are typically map objects. Eg: CSV data reader \XML Data Reader 2.Business Object Builder The business object builder instantiates the business object and populates it from the data in the data object. Eg:The table object builder 3. Business Object Mediator The business object mediator converts the business object into physical object. The table object mediator is always used with the table object builder. Eg: table-based mediator 4. Data Writer The data writer writes the physical object into the database. This tutorial uses the default data writer to write the generated physical objects into the database. There are three configurations files and a i
Read more

Websphere Commerce Catalog Subsystem

-
  Websphere Commerce Catalog Subsystem The Catalog Subsystem contains all logic and data relevant to an online catalog, including catalog groups (or categories), catalog entries, and any associations or relationships among them.    Master Catalog It is the single catalog that contains all products, items, relationships, and standard prices for everything that is for sale in your store. Every store in the Web Sphere Commerce system must have a master catalog. It is possible to share the master catalog across stores. Master Catalog Restrictions 1)The master catalog must be a proper tree, which means that there are no cycles. e.g.The parent category "Women" has a subcategory "WomenDress". It is important that WomenDress and any of WomenDress's subcategories like tops,jeans etc are not the parent category of "Women" category. 2)A catalog entry or category cannot belong to multiple parent categories in the master catalog. To place a
Read more

Calculation Framework in Websphere Commerce.

-
  OrderCalculateCmd OrderCalculateCmd invokes the Promotion engine. PromotionEngineOrderCalculateCmdImpl implements OrderCalculateCmd class. OrderCalculateCmd is invoked when we add, delete, update or merge item/s in cart. This command calculates the order  total based on the sequence in which calculationUsageId is passed into the command. WebSphere Commerce provides the below predefined calculation usages: Calusage_id    Description -1                         Discount -2                         Shipping -3                         Sales Tax -4                         Shipping Tax -5                         Coupon -6                         Surcharge -7                         Shipping Adjustment   CalculateOrderCommand iterates over the array of Calusageids passed in requestProperties and invokes the below methods accordingly for each calusageid. initialize, apply and summarize methods As a part of InitializeAdjustment and InitializeCoupon commands, respective calmethod and calrule com
Read more