Some fixes and enhancements that are included in this package are not automatically
enabled because you might not need them on your environment. The following list describes optional
fixes and enhancements that you can manually enable. Review the following section to see if you want
to enable any new features or apply any particular fixes.
Procedure
-
Fixes and enhancements related to Stores and Mobile:
-
Enabling interim fix JR56672 - Enable this fix if
you want your store to be able to override publish option at product and category level.
- Optional:
Enabling store-related interim fixes - Enable these fixes
if you encounter any of the following issues in your Aurora starter store.
- JR51843 fixes an issue where a shopper's order history, wish list, and other store pages display
empty product information when a product is not in the current sales catalog
- JR51876 fixes an issue where non-English characters display in the browser title after you
republish the Aurora starter store.
- JR52816 fixes display issues and link-related issues in the Facebook Like
and Facebook Activity widgets
- JR53899 supports the use of commas (;) in the price range fields of the price range facet
- JR55162 fixes an issue where, if you are integrated with Sterling Configurator, the
"Change configuration" option incorrectly displays on the Check
out pages even if the predefined dynamic kit is not configurable.
- JR56588 fixes an issue where some mobile page actions fail with Cross-Site-Request-Forgery
(CSRF) errors.
Note: This fix was included in an earlier cumulative interim fix package
(JR56287), therefore this fix might already be enabled. If you previously installed JR55049 and
enabled this fix, then you do not have to complete this step
- Optional:
Enabling interim fix JR55605 - Enable this fix if
you want to enhance the SEO URL keyword generation utility performance for environments with an
Oracle database.
Note: This fix was included in an earlier cumulative interim fix package
(JR56287), therefore this fix might already be enabled. If you previously installed JR55049 and
enabled this fix, then you do not have to complete this step
- Optional:
Enabling interim fix JR55526 - Enable this fix if
you encounter issues where where a shopper cannot scroll on an Aurora mobile store if the shopper is
using Google Chrome browser Version 48 or newer.
Note: This fix was included in an earlier cumulative interim fix package
(JR56287), therefore this fix might already be enabled. If you previously installed JR55049 and
enabled this fix, then you do not have to complete this step
- Optional:
Enabling interim fix JR54726 - Enable this fix if
you want your store to redirect to the product URL when a shopper clears all defining attributes for
a product.
Note: This fix was included in an earlier cumulative interim fix package
(JR55049), therefore this fix might already be enabled. If you previously installed JR55049 and
enabled this fix, then you do not have to complete this step
- Optional:
Enabling interim fix
JR54193 and JR53752 - Enable these fixes if you encounter the following issues:
- Discount widget does not show a promotion if the promotion is set at the SKU level
- After resolving a SKU on the Product Display page, several widgets incorrectly display product
information rather than SKU information
Note: This fix was included in an earlier cumulative interim fix package
(JR55049), therefore this fix might already be enabled. If you previously installed JR55049 and
enabled this fix, then you do not have to complete this step
- Optional:
Enabling interim fix JR52714 - Enable this fix
if you are integrated with Sterling Selling and Fulfillment Suite 9.4 and you want to be able to
view the Order Details page for a store order.
Interim fix JR52714 addresses an issue where an order details service call that includes the
ModificationType input parameter does not return the JSON response in the expected format. You can
enable this fix to ensure that users can see order history details on the
Order
Details page when side-by-side integration is enabled between WebSphere Commerce and
Sterling Selling and Fulfillment Suite.
Note: This fix was included in an earlier
cumulative interim fix package (JR53438), therefore this fix might already be enabled. If you
previously installed JR53438 and enabled this fix, then you do not have to complete this
step
-
Fixes and enhancements related to Search:
- Optional:
Enabling interim fix JR57713 - Enable this fix if
you encounter ArrayIndexOutOfBoundsException errors after an inventory index update.
- Optional:
Applying interim fix JR56748- Enable this fix if
you need to use the deleteFromDeltaTable parameter when you run the
UpdateSearchIndex utility.
- Optional:
Enabling
interim fix JR56299 - Enable this fix if you notice that Search cache invalidations are not
propagated to production server.
Note: By completing this step, you also enable the following features:
- The ability to use the di-buildindex utility on an Oracle 12c database
- The ability to use an option to incrementally publish or unpublish a product or category for
each language independently
- Ensures that the full image is displayed when a thumbnail image is selected.
- Ensures that the sequence of products in the product list page on the storefront matches the
sequence that is defined in Management Center
- Ensure that the user-defined product sequence is respected when you enable Search Result
Grouping and hero product.
- Enables the ability to override the item's sequence value with its parent product's sequence
value in the search index.
- Optional:
Enabling interim fix JR55670 - Enable this fix if
you notice situations where SKUs are not displayed in the sequence that is specified in the
Management Center.
Note: This fix was included in an earlier cumulative interim fix package
(JR56287), therefore this fix might already be enabled. If you previously installed JR55049 and
enabled this fix, then you do not have to complete this step
- Optional:
Enabling interim fix JR53912 - Enable this fix to
resolve an issue where some keyword suggestions can lead to empty search results if the keyword
belongs to a different store, catalog, or Catalog Filter.
Note: This fix was included in an earlier cumulative interim fix package
(JR55049), therefore this fix might already be enabled. If you previously installed JR55049 and
enabled this fix, then you do not have to complete this step
- Optional:
Enabling interim fix JR54703 - Enable this fix if
you want to specify a list of URI prefixes to be skipped, so that the store path is not added to
image URLs.
Note: This fix was included in an earlier cumulative interim fix package
(JR55049), therefore this fix might already be enabled. If you previously installed JR55049 and
enabled this fix, then you do not have to complete this step
- Optional:
Enabling interim fix JR54025 - Enable this fix if
you want support for boosting fields from an extension index using sum and product Solr
functions.
Note: This fix was included in an earlier cumulative interim fix package
(JR55049), therefore this fix might already be enabled. If you previously installed JR55049 and
enabled this fix, then you do not have to complete this step
- Optional:
Enabling interim fix JR54001 - Enable this fix if
you want a search configuration to limit the spell check correction to display collation query
results only. If you do not enable this fix, you might notice that for searches that include
misspelled words, WebSphere Commerce combines collation query suggestions and non-collation query
suggestions into one list under the "Did you mean" results.
Note: This fix was included in an earlier cumulative interim fix package
(JR55049), therefore this fix might already be enabled. If you previously installed JR55049 and
enabled this fix, then you do not have to complete this step
- Optional:
Enabling interim fix JR53857 - Enable this fix to
ensure that the site content crawler can crawl pages that use HTTPS in the storefront.
Note: This fix was included in an earlier cumulative interim fix package
(JR55049), therefore this fix might already be enabled. If you previously installed JR55049 and
enabled this fix, then you do not have to complete this step
- Optional:
Enabling interim fix JR54149 - Enable this fix if
you want to avoid returning a smaller result set when the Solr minimum match option is used with
synonyms.
Note: This fix was included in an earlier cumulative interim fix package
(JR55049), therefore this fix might already be enabled. If you previously installed JR55049 and
enabled this fix, then you do not have to complete this step
-
Fixes and enhancement related to Runtime:
- Optional:
Enabling interim fix JR55289 - Enable this fix if
you want support for configuring cross-origin resource sharing (CORS) headers and X-Frame-Options
header with a servlet filter.
Note: This fix was included in an earlier cumulative interim fix package
(JR56287), therefore this fix might already be enabled. If you previously installed JR55049 and
enabled this fix, then you do not have to complete this step
- Optional:
Enabling interim fix JR55834 - Enable this fix if
you want to enhance token-based CSRF protection on REST APIs when cookies are used for
authentication and the corresponding WCToken/WCTrustedToken are not provided.
Note: This fix was included in an earlier cumulative interim fix package
(JR56287), therefore this fix might already be enabled. If you previously installed JR55049 and
enabled this fix, then you do not have to complete this step
- Optional:
Enabling interim fix JR52486 - Enhancement: Enable
this fix if you want to use your custom search profile
wc-rest-resourceconfig.xml as the default search profile.
Note: This fix was included in an earlier
cumulative interim fix package (JR53438), therefore this fix might already be enabled. If you
previously installed JR53438 and enabled this fix, then you do not have to complete this
step
-
Fixes and enhancements related to Messaging and Integration:
- Optional:
Enabling interim fix JR55718 - Enable this fix if
you are integrated with Sterling Visual Modeler and you encounter an input validation error when
launching the Test and Compile window from Visual Modeler and clicking the
Add button.
Note: This fix was included in an earlier cumulative interim fix package
(JR56287), therefore this fix might already be enabled. If you previously installed JR55049 and
enabled this fix, then you do not have to complete this step
-
Fixes and enhancements related to Marketing and Promotions:
- Optional:
Enabling interim fix JR55599 - Enable this fix if
you notice an issue where a dialog activity with a "Customer Registers" trigger does not work when
the "Account activation via Email" option is enabled.
Note: This fix was included in an earlier cumulative interim fix package
(JR56287), therefore this fix might already be enabled. If you previously installed JR55049 and
enabled this fix, then you do not have to complete this step
- Optional:
Enabling interim fix JR54177 - Enable this fix if
you want to resolve an issue where a business user cannot activate promotions that have public codes
if the promotions were edited within the Promotion list view.
Note: This fix was included in an earlier cumulative interim fix package
(JR55049), therefore this fix might already be enabled. If you previously installed JR55049 and
enabled this fix, then you do not have to complete this step
- Optional:
Enabling interim fix JR54737 - With JR54737, you can customize some promotion error messages
that display to shoppers to provide shoppers with more information about how to resolve errors that
they encounter while shopping in your store.
Note: This fix was included in an earlier cumulative interim fix package
(JR55049), therefore this fix might already be enabled. If you previously installed JR55049 and
enabled this fix, then you do not have to complete this step
-
Fixes and enhancements related to Catalog:
- Optional:
Enabling interim fix JR56935 - Enable this fix if
you notice performance issues when you change Rule Based Sales Category (RBSC) rules.