How to fix cache issue in SFCC Sitegensesis

Templates are usually cached to improve the page load performance. One limitation of using cache is that we are required to invalidate the cache every time we make some change in business manager. For example changing the site preference value. We can prevent a portion of the template from getting cached by using remote include.

Remote Include

Let me show this with an example. Let us assume that productdescriptionpage.isml is cached and site preference(textdisplay) is used to either display or hide the text.

For using Remote Include, we first create a pipeline and then call the pipeline using isinclude. A simple pipe can be created using start node and interaction node. The interaction node should contain isml with the above snippet. Show.xml contains Text pipeline.