Documentation Center

Resolved issues

This section describes the issues resolved in this and previous releases of SmartTarget.

Resolved issues in SmartTarget 2014

This section lists the issues resolved in SmartTarget 2014.

Issue with SmartTarget cartridges

Problem: The SmartTarget cartridge and Session cartridge (Ambient Data Framework) did not always put in all of the claims they manage.

Solution: The cartridges have been fixed so that all the claims are available on every request.

List fields are duplicated for each Component in the system
Problem: Each field value in a Schema field of type List (except Keyword fields) becomes a separate attribute in Fredhopper when you publish a Component to SmartTarget that uses this Schema. For example, if you create two Components that use a list field and publish these to SmartTarget, two unique attributes are added to SmartTarget based on the Component TCM URI and list field. This makes these fields to all intents and purposes unusable as criteria for Promotions as you can only choose a value that is specific for a particular Component. Furthermore, it clutters the system excessively.

Resolved issues in SmartTarget 2011 SP2

No issues were resolved in SmartTarget 2011 SP2.

Resolved issues in SmartTarget 2011 SP1

Running the Fredhopper installer from the command line did not work. The installer and documentation have been updated in this release so that you can perform a headless installation.

Resolved issues in SmartTarget 2011

This section lists the issues resolved in SDL SmartTarget 2011.

Promotion Title field also available in the Web site
The displayed Title field of a promotion in the SmartTarget Manager also available in the Web site.
Versioning JARs and DLLs
Product versions have now been applied inside assemblies and JAR files.
Content Delivery deployment transactionality
Data deployed to Content Delivery and Fredhopper is now kept in sync. When publishing to Content Delivery fails, Content Delivery does not push content to Fredhopper.
This has been achieved by moving the processing of content for Fredhopper into the Finalize phase to ensure deployment only when Content Delivery succeeds.
Embedded Schemas
It was not possible to use fields in Embeddable Schemas. Fields in Embeddable Schemas are now passed on to Fredhopper correctly.
Schema field labels in SmartTarget Manager
End users were confronted with TCM URIs when managing promotions in SmartTarget. Field names now have user-friendly labels. For example, to be able to better identify Schema fields in the SmartTarget Manager, Schema fields are labeled as follows: SchemaName - FieldName - EmbeddableSchemaFieldName, for example -Order - Billing Address - City or Town.

Resolved issues in SmartTarget 2010 SP1

This section lists the hotfixes included in SDL SmartTarget 2010 SP1.

Hotfixes
The SDL SmartTarget 2010 SP1 release includes the following hotfixes:
  • 69705: Web service to allow FAS on remote machine in enterprise environment
  • 70381: Wrong identifiers on metadata
  • 72449: Duplicate items in a region when using more then one promotion
  • 72936: Negate attribute on Attribute Tag/Control to allow for negative filtering
XML multi-threading exception
When you deployed using multi-threading, the following error would sometimes occur:
org.w3c.dom.DOMException: WRONG_DOCUMENT_ERR: A node is used in a different document than the one that created it.
This problem has been fixed in SDL SmartTarget 2011.