Index Variants as children of parents

Testing Support

1- Useful links & tips

2- Documentation

3- Notes

  • [CMS] Hawksearch does not differentiate between pages (content) and products (product) in the dashboard and that is why a CMS page shows up under “Top Product Match” when searching for it in Hawksearch dashboard.

Connector: Variant attributes roll-up indexing (default)

By Default only Index parents with children attributes rolled up into the parent (Standard Way). This should be how the connector is setup when initially installed

Notes on Foundation:

  1. Following variant fields are NOT indexed or rolled up into the parent(product/bundle/package) as part of this approach:

    1. Child_Color, Child_Size, Child_DisplayName, Child_Code, Child_Url

    2. Inventory_{WarehouseCode} , Price_{MarketId}_{Currency}

  2. For Bundles and Packages only Variant entries(components) are indexed, anything else is NOT.

  3. Inventory_{WarehouseCode} , Price_{MarketId}_{Currency} are indexed only for Packages.

  4. ImageAlt, ImageURL are indexed only for products in foundation.

Opti setup: most common

Scenario(s) + steps

Full Indexing Status

Incremental Indexing Status

Notes

1

Manual/Scheduled Run

Manual/Scheduled Run

2

https://techromix.atlassian.net/browse/HC-44

Fields to check: SiteId | MetaTitle | Keywords | BackgroundImage | MainBody | Coordinates | Id | Name | StartPublish | StopPublish | IndexedOn | ContentLink | ParentLink | ItemType | Url |

Id = ContentLink for the CMS pages

3

CMS - Standard & Location Item page types are indexed

  • Create a Standard page & a Location Item page → run the indexing job → verify that page and its fields is available in Hawksearch

  • Update the page → run the indexing job → verify updates are available in Hawksearch

  • Delete the page → run the indexing job → verify it is deleted in Hawksearch

Pass
Fail
Pass
Fail

 

4

CMS - Other page types are NOT indexed

  • Create a Blog Item page & a Two Column Landing Page → run the indexing job → verify it is NOT available in Hawksearch

Pass
Fail
Pass
Fail

 

5

NO CMS - Catalog only setup

  • Verify that no CMS changes to Standard or Location Item page types (create, update, delete) are indexed

Pass
Fail
Pass
Fail

 

6

7

Verify that the Category structure is sent to Hawksearch

 

 

8

Edit the Category structure and verify it is updated in Hawksearch

 

9

Delete categories and verify in Hawksearch that:

  • the category is not available

  • the products under that category are not available

 

10

Product-variant catalog structure

  • variant information is rolled up as a list under the Product

  • variants are not sent separately

 

11

Variant-only catalog structure

  • not supported with this type of indexing

 

12

Products - Fields to check

  • from product: ID | Name | StartPublish | StopPublish | IndexedOn | ContentLink | ParentLink | ItemType | URL | Code | Category | CatalogId | DisplayName | Markets | Manufacturer | Model | ModelYear | Warranty | Brand | Department | OnSale | NewArrival | ProductStatus | Description | LongDescription | ImageUrl | ImageAlt

  • rolled up from variant: Size | Color | Sku | Mpn | Upc | Description

13

Verify that product fields are sent to Hawksearch for each product

 

14

Edit product information and verify that updates are sent to Hawksearch

  • Images and other digital assets will be indexed as part of a product

 

15

Delete product information and verify that it is also removed in Hawksearch

 

16

Update Parent of product and verify the Category ID and Parent link is updated

Test data/Input

  • CatALevel1 (under catalog) - 1073741845

    • CatALevel2 - 1073741846

      • CatALevel3 - 1073741847

  • CatBLevel1 - 1073741848

    • CatBLevel2 - 1073741850

  • Initial Parent: CatALevel3

  • New Parent: CatBLevel2

 

17

Product belongs to several categories

  • Parent link is displayed for main the primary category

  • Category ID is sent for all the categories the product belongs to

 

18

Product belongs to several categories

  • delete one secondary category and verify the Category link is removed from the product in Hawksearch

 

19

Delete a product’s Primary category

Input (tip: backup & restore DB)

  • prod#1 (Primary category only): LL SAMMY SHIRT

  • prod#2 (Primary and secondary categories): LUCIEN COTTON TWILL COAT

Output:

for product#1(under Primary category only):

for product#2(under Primary and secondary categories):

 

20

Delete product and verify the product is removed in Hawksearch

Test data:

  • LL POE CROPPED JERSEY PANT

 

21

|

Bundles - Fields to check:

  • from bundle: ID | Name | StartPublish | StopPublish | IndexedOn | ContentLink | ParentLink | ItemType | URL | Code | Category | CatalogId | DisplayName | Markets

  • rolled up from variant: Size | Color | Description (*only variants are considered children)

22

Bundle level information is sent to Hawksearch

Input/Test data:

  • bundle#1 (with variants): “LL Bundle 2Variants”

  • bundle#2 (with products ): “LL Bundle Linked”

  • bundle#3 (with variants ): “LL Bundle 1Variant"

Output:

 

23

Update Parent of a bundle and verify the Category ID and Parent link is updated

Test data/Input

  • CatALevel1 (under catalog) - 1073741845

    • CatALevel2 - 1073741846

      • CatALevel3 - 1073741847

  • CatBLevel1 - 1073741848

    • CatBLevel2 - 1073741850

  • Initial Parent: CatALevel3

  • New Parent: CatBLevel2

 

24

Bundle belongs to several categories

Test data:

  • bundle#1 - “LL Bundle 3Variants”:

    • primary category: 1073741841 (LL Misc)

    • secondary categories: 1073741839(Sweaters), 1073741840(LL_Jackets)

    • delete: 1073741839(Sweaters)

  • bundle#2 - “LL Bundle Linked” :

    • primary category: 1073741841 (LL Misc)

    • secondary categories: 1073741839(Sweaters), 1073741837(LL Shoes)

    • update primary category to: 1073741840(LL_Jackets) and vice-versa for incremental

Output:

 

25

Delete a Bundle’s Primary category

Input:

  • bundle#1 (Primary category only): LL Bundle Primary2delete

  • bundle#2 (Primary and secondary categories): LL Bundle 2delete2

Output:

bundle#1(under Primary category only):

bundle#2(under Primary and secondary categories):

 

26

|

Packages - Fields to check:

  • from package: ID | Name | StartPublish | StopPublish | IndexedOn | ContentLink | ParentLink | ItemType | URL | Code | Category | CatalogId | DisplayName | Markets | Inventory_{WarehouseCode} | Price_{MarketId}_{Currency}

  • rolled up from variants under Package entries: Size | Color | Sku | Mpn | Upc | Description

*only variants are considered children

27

Package level information is sent to Hawksearch

Input/Test data:

  • package#1 (with variants): “LL Package 2Variants”

  • package#2 (with packages): “LL Package SingleMarket”

  • package#3 (with variants): “LL Package 2Delete2”

Output:

 

28

Update Parent of a package (kit) and verify the Category ID and Parent link is updated

Test data/Input

  • CatALevel1 (under catalog) - 1073741845

    • CatALevel2 - 1073741846

      • CatALevel3 - 1073741847

  • CatBLevel1 - 1073741848

    • CatBLevel2 - 1073741850

  • Initial Parent: CatALevel3

  • New Parent: CatBLevel2

 

29

Package (kit) belongs to several categories

Test data:

  • package#1 - “LL Package Canada” has:

    • primary category: 1073741841 (LL Misc)

    • secondary categories where it’s linked: 1073741839(Sweaters), 1073741840(LL_Jackets)

    • delete: 1073741839(Sweaters)

  • package#2 - “LL Package Spain” has:

    • primary category: 1073741840(LL_Jackets)

    • secondary categories: 1073741841 (LL Misc), 1073741839(Sweaters)

    • update primary category to: 1073741837 (LL Shoes)

Output:

 

30

Delete a package (kit)’s Primary category

Input(tip for testing: backup & restore DB):

  • package#1 (Primary category only): LL Package 2Delete3

  • package#2 (Primary and secondary categories): LL Package 2Delete5

Output:

package#1(under Primary category only):

package#2(under Primary and secondary categories):

 

31

|

32

Product published on multiple markets in Optimizely

Input:

  • all products have markets: Australia, Canada, Spain, UK, USA

    • Product#1 - LL JADE HIGH BOOT

    • Product#2 - TRINITY STRAPPY MID SANDAL

    • Product#3 - KARLIE TROUSER

Tests & Output:

 

33

Bundle published on multiple markets in Optimizely

Input:

  • all bundles start with markets: Australia, Canada, Spain, UK, USA

    • Bundle#1 - LL Bundle 2delete2

    • Bundle#2 - LL Bundle 3Variants

    • Bundle#3 - LL Bundle 2Variants

Tests & Output:

 

34

Package (kit) published on multiple markets in Optimizely

Input:

  • all kits start with markets: Australia, Canada, Spain, UK, USA

    • package#1 - LL Package 2Variants

    • package#2 - LL Package 2Delete4

    • package#3 - LL Package SingleMarket

Tests & Output:

 

35

|

36

Multi-language for products - product & variant level information is sent for each language

Input/Test data:

  • product: LL SHEER CREPE PANT (published in both en & fr)

Tests & Output:

 

37

Multi-language for products

Input/test data:

  • languages: english, french (mapped with spanish in Hawksearch)

  • product#1: DANIEL COOL WOOL JACKET

  • variant #1 for product#1: SKU-39101253

  • product#2: LL SHEER CREPE PANT

Tests & Output

 

38

Multi-language bundles - bundle & variant level information is sent for each language

Input/Test data:

  • bundle: “LL Bundle 3Variants” (published in both en & fr)

Tests & Output:

 

39

Multi-language bundles

Input/Test data:

  • languages: English, French (mapped with Spanish in Hawksearch)

  • bundle#1: “LL Bundle English 2” (published only in en)

  • bundle#2: “LL Bundle Linked” (published in both en & fr)

Tests & Output:

 

 

 

 

40

Multi-language packages - package & variant level information is sent for each language

Input/Test data:

  • package: “LL Package 2Variants” (published in both en & fr)

Tests & Output:

 

41

Multi-language packages

Input/Test data:

  • languages: English, French (mapped with Spanish in Hawksearch)

    • package#1: “” (published only for en)

    • package#2: “LL Package 2Variants” (published on both en & fr)

Tests & Output:

 

42

|

Default indexing approach supports price indexing only for package types

43

Package (kit) with price on single market

Input:

  • package#1 (Canada market) - LL Package Canada / Price_CAN_CAD / 150 CAD

  • package#2 (Spain market) - LL Package Spain / Price_ESP_EUR / 85 EUR

Tests & Output

 

44

Package (kit) with multi-currency prices

Input:

  • package#1 | package#2 - LL Package 2Variants | LL Package SingleMarket

  • 5 markets for each package

    • Australia / Price_AUS_AUD / A$110 | A$180

    • Canada / Price_CAN_CAD / CA$150 | CA$200

    • Spain / Price_ESP_EUR / 75EUR | 85EUR

    • UK / Price_UK_GBP / 90 | -

    • US / Price_US_USD / $130 |

Tests & Output

 

45

|

Default indexing approach supports price indexing only for package types

46

Package with inventory for single warehouse

Input:

  • package#1 (Canada market) - LL Package Canada (Inventory_Toronto : 455)

  • package#2 (Spain market) - LL Package Spain (Inventory_Madrid: 1250)

Tests & Output

 

47

Package with inventory in multiple warehouses

Input:

  • package#1 | package#2 - “LL Package SingleMarket” | “LL Package 2Variants”

  • 5 markets for each package

    • Australia / Inventory_Sydney / 35 | 202

    • Canada / Inventory_Toronto / 25 | 201

    • Spain / Inventory_Madrid / 30 | 203

    • UK / Inventory_London / - | 205

    • US / Inventory_Los Angeles / - | 204

Tests & Output

 

Opti setup: “2 websites” variation

Scenario(s) + steps

Full Indexing Status

Incremental Indexing Status

Notes

1

Manual / Scheduled Run

Manual / Scheduled Run

2

|

CMS - Fields to check: SiteId | MetaTitle | Keywords | BackgroundImage | MainBody | Coordinates | Id | Name | StartPublish | StopPublish | IndexedOn | ContentLink | ParentLink | ItemType | Url |

3

CMS - Standard & Location Item page types are indexed

 

4

CMS - Other page types are NOT indexed

  • Create a Blog Item page & a Two Column Landing Page → run the indexing job → verify it is NOT available in Hawksearch

 

5

NO CMS - Catalog only setup

  • Verify that no CMS changes to Standard or Location Item page types (create, update, delete) are indexed

 

6

Categories & category structure

7

Verify that the Category structure for each Catalog is sent to Hawksearch

 

 

8

Edit the Category structure on Catalog A and verify it is updated in Hawksearch → The catalog structure in Site B is not affected

 

9

Products / Bundles / Packages

10

Edit in Catalog A:

  • product, variant, bundle, package in one language → verify the changes are displayed in Hawksearch and Catalog B is not affected

  • Prices in different currencies → verify the changes are displayed in Hawksearch and Catalog B is not affected

Test Data/Input:

Product + variant: LUCIEN COTTON TWILL COAT

Package: LL Package 2Delete3

Bundle: LL Bundle Primary2delete

 

11

Delete categories from catalog B

Output:

  • Catalog A is not affected

  • the category is not available

  • the products under that category are not available

  • the variants under that category are not available

 

12

Delete products/ variants/ bundles / packages in Catalog B

Test Data/Input:

Product + variant: LL JADE HIGH BOOT

Package: LL Package 2Delete5

Bundle: LL Bundle 2delete2

Output:

  • Catalog A is not affected

  • the category is not available

  • the products under that category are not available

  • the variants under that category are not available

 

13

Move from Site A to Site B:

  • a category → verify the Catalog ID and ParentLink are updated

  • a product → verify the Catalog ID, Category and ParentLink are updated

  • a variant → verify the Catalog ID, Category and ParentLink are updated

  • a bundle → verify the Catalog ID, Category and ParentLink are updated

  • a package (kit) → verify the Catalog ID, Category and ParentLink are updated