Knowledge Base

Welcome to the SmarterCommerce documentation portal

What can we help you find?

SMARTERCOMMERCE

Search and Learn about Unified Commerce and Our SmarterCommerce Solutions
Digital Commerce Additional Manual

Considerations


Cases when Page Cache Dependency is released:

  • On Mappings Page selection change.
  • When change Page URL of Override Page selected on designers.
  • When Publish a Sitefinity Page: Designer Properties change.
  • When Publish a Template: Designer Properties Change.
  • When apply any change over Dynamic Content Dependency.
  • On Settings Module.

You must exit the page when changing values in the widget designer and publish.  This is to prevent the page from being cached with incorrect values (designer properties remain in Context).

The widgets that work in the template load the view with the shared information for all users according to the designer properties.

Widgets that have long cache support load dynamic content via ajax queries, the cached view has support for loading the required dynamic information.

The Catalog and Product Content widgets do not have any dependencies for changes in settings so if a setting is changed it is required to republish the pages, to see the changes applied.

Catalog and Product Content Get Status services cannot be marked as Read Only because modify the session values.

The Catalog (Catalog Nodes/Product List) and Product Content (Full-Main View) Widgets, load shared information about catalogs and products and with this information the page is cached, the user-specific information is loaded by AJAX request after page load.

Sitefinity pages cache is released when publishing a Page or Template. When publishing a template all related pages that are inherited from the template also release the page cache.

Bring It All Together

We bring together digital commerce, retail and call center channels with a united approach that leverages the power of onmi-channel while prioritizing JD Edwards connectivity.

CONNECT WITH AN EXPERT