Release notes for Optimizely CMS and Commerce updates

Fixed an issue where a second search would not produce a result. If you cleared the content index and then started Search & Navigation Content Indexing Job manually, the first search in the Search box of the catalog tree performs correctly, but the next one did not.

CatalogContentEventListener.IndexContentIfNeeded can get into an infinite loop when executing multiple threads. You should use ConcurrentDictionary instead of using standard dictionaries. 

Updated the Newtonsoft.Json dependency version from 12 to 13.

(Episerver.Find already supported Newtonsoft.Json 13)

Fixed issue with ability to set FindCommerce event indexing to allow for temporarily disabling of event indexing. 

CatalogContentClientConventions.AllowIndexingCatalogContent should be possible to set dynamically. Furthermore, IsListeningToPriceEvents, IsListeningToInventoryEvents and IsListeningToLowLevelApiEvents should be introduced, and also possible to set dynamically to allow fine grain control of the indexing.

Fix to improve performance of catalog intensive operations such as import, when loading language versions.

Steps to reproduce

1) Deploy a Commerce site using FindSearchProvider to Azure.
2) Make sure everything works as expected, i.e: you can search the catalog in Catalog Entry Search of Commerce Manager, the FindSearchProvider gets values from app settings of web app.
3) Update serviceUrl and defaultIndex in Mediachase.Search.config to invalid values, i.e:
serviceUrl="https://es-eu-dev-api01.episerver.net/BG2y7vnuQICkEqmEOVHAK7SVcuNX4xH4" defaultIndex="dinhnguyen_20190830".
4) Re-deploy the Commerce site.
5) Make sure app settings still have serviceUrl and defaultIndex values. And these values are valid.
6) Navigate to Commerce Manager -> Catalog Management -> Catalog Entry Search.

Expected
No errors, be able to search catalog.

Actual
"401 Unauthorized" error displays. Because the FindSearchProvider doesn't get values from app settings, it still gets value from Mediachase.Search.config file. If you restart the web app, then rebuild the Index in the Administration UI, it works as expected.

Precondition: Install FindCommerce to QuickSilver.

1. Create a Catalog name Catalog1 with avaiable Language: English
2. In Catalog1, create a Category name CategoryA. Publish it
3. Create a category name Sub1 that is child of CategoryA. Publish it
4. Create a Catalog name Catalog2 with available Language: Svenska
5. In Catalog2, create a category name CategoryB. Publish it
6. Move Sub1 from CategoryA to CategoryB
7. Go to Find/#configure/boosting. Then search by: Sub1

Expected: Sub1 of CategoryA isn't returned. Because it was moved to CatetoryB at step6
Observed: Sub1 of CategoryA is returned. If open it, error will occurs
Note: This issue also happens in FindCommerce 11.0.1

Precondition:

• Install FindCommerce on QuickSilver
• Catalog Fashion is avaiable at language: English and svenska

1. Go to CatalogUI, In catalog Fashion: create Category NodeA. Publish it at English and Svenska
2. Create a sub node of NodeA named SubNodeA. Publish SubNodeA at English and Svenska
3. Go to Go to Find > Overview > Explore, search for "NodeA"
4. Expand the detail NodeA at Svenska. Search for "ChildNodeRelations"
Expected: SubNodeA should be shown in "ChildNodeRelations"
Observed: SubNodeA isn't shown in "ChildNodeRelations" (bug)

Note: This issue also happens at FindCommerce11.0.1

Update the Find Commerce integration to use the Commerce 13 packages.

Precondition:

• Install FindCommerce to QuickSilver
• Run indexing job

1. Go to CatalogUI
2. Create a catalog named TestCatalog with default language: English. Then publish it
3. In TestCatalog, create a Category then publish it
4. Go to Find/overview/explore, search for TestCatalog
5. Expand to see detail TestCatalog at English
6. Search for: ChildNodeRelations
Expected: the catalog at step3 is shown in the ChildNodeRelations
Observed: the catalog at step3 isn't shown in the ChildNodeRelations

Note: This issue also happens at FindCommerce 11.0.1