Release notes for Episerver updates

Added ability to extend the Order Management module by adding placeholders in which partner developers can put their code.

Placeholder examples:

• Top of Cart/Order list.

• Top and bottom of Cart/Order list.
  

• New tab in Cart/Order details view.
  
• New tab in Contact Details view.
  

For more information, see the the Quicksilver site sample code and documentation (released with Commerce 13.26.0)
https://github.com/episerver/Quicksilver/blob/master/Sources/EPiServer.Reference.Commerce.Site/CSRExtensibility/react-app/README.md

Removal of Beta stamp for these features.

• For EPiReportController, the check for EPiBetaUsers role has been removed.
• For IOrderSearchService, the Beta stamp has been removed.

For the multiple order forms in cart as below code, the CreateOrderForm() are returning same OrderFormId (-2)

var orderRepository = ServiceLocator.Current.GetInstance<IOrderRepository>();
            var orderGroupFactory = ServiceLocator.Current.GetInstance<IOrderGroupFactory>();
            var currentMarket = ServiceLocator.Current.GetInstance<ICurrentMarket>();
            ICart cart = orderRepository.LoadOrCreateCart<ICart>(CustomerContext.Current.CurrentContactId, "Default", currentMarket);
            if (cart != null)
            {
                orderRepository.Delete(cart.OrderLink);
            }
            cart = orderRepository.LoadOrCreateCart<ICart>(CustomerContext.Current.CurrentContactId, "Default", currentMarket);
            cart.Forms.Remove(cart.GetFirstForm()); // We always remove the form provided by default form in a new cart as we need to populate all order forms with a bunch of custom property values later on.
            cart.Forms.Add(orderGroupFactory.CreateOrderForm(cart)); // Expected orderformid is -2, which it is
            orderRepository.Save(cart);
            cart = orderRepository.LoadOrCreateCart<ICart>(CustomerContext.Current.CurrentContactId, "Default", currentMarket);
            cart.Forms.Add(orderGroupFactory.CreateOrderForm(cart)); //Expected orderformid is -3 which it is in 13.18.2, but in 13.24.0 this is assigned -2 which leaves us with two order forms with the same id
            cart.Forms.Add(orderGroupFactory.CreateOrderForm(cart)); // 13.18.2 assigns -4 and 13.24.0 assigns -3, here the incrementation seems to be working again

source: https://pastebin.com/3e48Lihr

Fixed "Missing success message for Collect Report Data Job"

Steps to reproduce:

1. Go to CMS Admin view.
2. Succesfully run the scheduled job "Collect Report Data".
3. Once completed, look at the "History" tab (see attached image).

Expected: A message indicating a succesfully completed job.

Actual: Empty field.

The default behavior when tracking is to use Request.UserHostAddress inside the tracking data. This value does not correctly identify the client's IP address if the traffic between client and server passes thru any proxies.

We should prefer to pick the client's IP from the X-Forwarded-For request header, if available. The SkipUserHostTracking config setting should still be respected.

Several queries when using function fn_UriSegmentExistsOnSiblingNodeOrEntry with LOWER() which makes the indexes non-performant.

Displaying discount prices on a product listing uses the same logic as evaluating promotions on a cart, basically running the promotion engine with a virtual cart containing one item. It will run through all the steps of evaluation, including filtering for redemption limits etc.

In order to improve this mechanism, to get discounted prices for product listing, a cache has been added to IPromotionEngine extension methods (IPromotionEngineExtensions) so that it reduces loads from the database.

When searching for line items on the Order Management screen, each search result contains a link to the respective product page on the e-commerce website.

Documentation:

• Order Management screen in the Episerver User Guide
• Extending the search result display on Episerver World

1. Commerce 13.22.0 site with third-party addon named CyberSource connector 1.1.2 installed and configured (\\vnfile01\EPi-Share\AddOnsTeam\ADD-ON DOCS_3rd Party Add-on\52.CyberSourceConnector)
2. Deploy site to Azure.
3. Checkout an order using Google Pay method
Observed: Error message displays: Failed to process your payment.{"AuthorizationReply":

,"AfsReply":null,"ReasonCode":"101","Decision":"REJECT","RequestId":"5972916626986719203009","AdditionalInformation":null,"AdditionalProcessorResponse":null,"InvalidFields":null,"MissingFields":["c:card/c:accountNumber"],"IsSuccess":false}
Please see the video here for more detail: https://recordit.co/lBQqIjsezR
Note: Google pay works fine with local site. The issue only happens in Azure/CDN

Improve the performance of the promotion engine by being more aggressive when caching the results of an evaluation.

There is a new config value, EvaluablePromotionCacheExpiration, that controls the cache expiration.