ContentConnect

The category report now also includes hidden categories. This feature can be enabled and disabled by a new filter in the report.

Due to this new feature, the Password parameter in the project app configuration is now mandatory and must not be empty.

Furthermore, the client id needs the permission to perform GET requests on the following DataAPI ressources:

The template Preview Generation has been updated:

Old. 

$CMS_SET(set_replaceTracker, "(<!-- Demandware Analytics)((.|[\\t\\n\\r])*)(</script>)")$

New. 

$CMS_SET(set_replaceTracker, "(<!-- Demandware Analytics)(?s:.)*(</script>)")$

This update prevents a possible Stackoverflow exception. It is highly recommended to perform this update in existing projects manually as well.

Demandware was renamed to Salesforce Commerce Cloud. Therefore the module got a new name as well: ContentConnect for Salesforce Commerce Cloud

ContentConnect supports the usage of the Content Integration API. Chapter 8 of the documentation describes the integration with FirstSpirit.

Besides the steps described in the documentation, further adjustments are necessary to use the Content Integration API in existing projects.

First, in the format template preview_generation the following code snippet should be moved to the top of the enclosing JSP scriptlet:

$-- Inject CMS preview content: Replace placeholder with actual CMS content --$
$CMS_FOR(for_item, [0..stringToReplace.size-1])$
    html = html.replaceFirst(
        "$CMS_VALUE(stringToReplace[for_item])$",
        "$CMS_VALUE(stringToInsert[for_item].toString().quoteJS())$");
$CMS_END_FOR$

Second, the new template include_html must be created manually. Use the following content:

//!Beanshell

import java.net.URL;
import java.net.URLConnection;
import java.io.IOException;
import java.io.InputStream;
import java.io.InputStreamReader;
import java.net.MalformedURLException;

String includeURL = gc.getVariableValue("includeURL").toString();
String name = gc.getVariableValue("name").toString();
String password = gc.getVariableValue("password").toString();
String isProtected = gc.getVariableValue("isProtected").toString();
String html = "";

includeURL = includeURL.replaceAll(" ","%20");
URL url = new URL(includeURL);
URLConnection urlConnection = url.openConnection();

if (isProtected.equals("true")){
    import org.apache.commons.codec.binary.Base64;

    String authString = name + ":" + password;
    byte[] authEncBytes = Base64.encodeBase64(authString.getBytes());
    String authStringEnc = new String(authEncBytes);

    urlConnection.setRequestProperty("Authorization", "Basic " + authStringEnc);
}

InputStream is = urlConnection.getInputStream();
InputStreamReader isr = new InputStreamReader(is);

int numCharsRead;
char[] charArray = new char[1024];
StringBuffer sb = new StringBuffer();
while ((numCharsRead = isr.read(charArray)) > 0) {
    sb.append(charArray, 0, numCharsRead);
}
html = sb.toString();
html = html.replaceAll("\\$", "$");

return(html);

With the new version it is possible to configure more than one FirstSpirit page template for detail pages for categories. Therefore the cartridge needs to be updated in exisitng projects.

The ContentConnect API has been extended with this version of the module.

First, the package com.espirit.moddev.demandware.manangers has been extended. Besides ProductManager, it now contains the interfaces LibraryManager and SlotConfigurationManager. Using these interfaces one can delete content assets, library folders and slot configurations.

Another important change is the introduction of the package com.espirit.moddev.demandware.factories. This package contains the class ManagerFactory that can be used to create instances of the interfaces mentioned above. If the ContentConnect module is installed, ManagerFactory will be accessible server-wide and can therefore be used e.g. in BeanShell scripts, workflows or schedule entries.

Analogous to ManagerFactory, XmlCollectorFactory provides means to create instances of the interface XmlCollector.

ManagerFactory as well as XmlCollectorFactory used to be FirstSpirit executables in previous versions of the ContentConnect module. These executables are still present, but their implementing classes have been renamed to ManagerFactoryExecutable and XmlCollectorFactoryExecutable. Despite this change, adjustments in existing projects are not necessary, since executables are accessed by their name. The names of the two executables haven’t been changed.

More information about the ContentConnect API can be found in the provided Javadoc documentation.

The ContentConnect module now allows to easily create detail pages for products and categories. For this purpose a button is shown on every report item, that opens the form of a project specific page template. A detail page will be based on this template and the form input.

Figure 2. Anlegen einer Detailseite

Figure 3. Dialog zum Anlegen einer Detailseite

DemandwareConnect 1.5.0 contains several changes and new features. Therefore it is necessary to perform some migration steps if a prior version of the module is installed. These steps are listed below and should be executed in the same order they are listed:

After the installation of the new module some templates need to be adjusted.

If the scripts CreateProductManager (reference name "createproductmanager") and CreateXmlCollector (reference name "createxmlcollector") do not exist, they need to be created using the stated reference names and the following contents:

CreateProductManager. 

#!executable-class
ManagerFactory

CreateXmlCollector. 

#!executable-class
XmlCollectorFactory

The initialization of the xml collectors needs to be adjusted in the project settings template. Furthermore, the instantiation of Connector must be replaced because now the interface ProductManager must be used to request product information in templates.

Xml collector for the content library:

old. 

$CMS_SET(ps_xmlCollector,class("com.espirit.moddev.demandware.xml.DemandwareXmlCollector").newInstance())$

new. 

$CMS_RENDER(script:"createxmlcollector",variableName:"ps_xmlCollector")$

Xml collector for the content slot configuration:

old. 

$CMS_SET(ps_xmlCollectorContentSlot,class("com.espirit.moddev.demandware.xml.DemandwareXmlCollector").newInstance(false))$

new. 

$CMS_RENDER(script:"createxmlcollector", variableName:"ps_xmlCollectorContentSlot", createLibraryNode:false)$

Object for requesting product information:

old. 

$CMS_SET(ps_DWRconnector,class("com.espirit.moddev.demandware.products.Connector").create(#global))$

new. 

$CMS_RENDER(script:"createproductmanager", variableName:"ps_productManager")$

Some components in the module have been renamed. Therefore all occurrences of FSDWC_ need to be replaced by DemandwareConnect_. The product drop handler is one of the components that have been renamed.

The interface ProductManager is incompatible with the public interface of the formerly used class Connector. Therefore, the retrieval of product information must be adjusted:

queryProduct(old). 

ps_DWRconnector.queryProduct(for_product.id)

loadProduct (new). 

ps_productManager.loadProduct(for_product.id)

Besides the replacement of Connector by ProductManager, the interfaces Product and Category have been modified as well. Corresponding template changes might be necessary.