============================================================================= Oracle Endeca Tools and Frameworks GENERAL (3.1.1) * Release Date: December 2012 * The release notes may have been updated since the release date. The latest release notes are available through the Oracle Endeca Commerce documentation page on the Oracle Technology Network at http://www.oracle.com/technetwork/indexes/documentation/endecaguidedsearch-1552767.html or by contacting Oracle Technical Support for Endeca Commerce Products. INSTALLATION (3.1.1) * Refer to the "Tools and Frameworks Installation Guide" for installation information. BUG FIXES (3.1.1) Workbench * WB-1543: You can now create content collections with Chinese characters in their names using Internet Explorer. There are no longer issues creating content items within them. * WB-1720: Developer Studio now allows you to configure Workbench settings through the "Tools>Workbench Settings" menu. * WB-1820: Content item promotion now works against multiple live MDEX engines. Endeca Assembler * ASM-373: The spurious dimensionToExpand parameter is no longer created by the NavigationContainerHandler. The workaround of adding it to the removeAlways property in the Assembler context file is no longer needed. Documentation * WB-1552 and WB-1553: The "Oracle Endeca Workbench Help", the "Oracle Endeca Commerce Workbench User's Guide", and the "Tools and Frameworks Cartridge Catalog" have been restored in this release and merged into a single guide named the "Oracle Endeca Workbench User's Guide". KNOWN ISSUES (3.1.1) Workbench * WB-1109: The reference application reserves different url paths for mapping static resources. No page can be named "images/", "css/", "js/" or "mobile/static". * WB-1197: If Workbench or CAS is running on Windows with a user that doesn't have Administrator privileges, the initialize_services script for Media MDEX fails. Both Workbench and CAS must be run by users with Administrator privileges. * WB-1239: Under certain conditions, the Rich Text Editor text area occasionally scrolls obscuring a portion of the toolbar. * WB-1301: It is possible to create pages for mobile devices within the Search And Navigation Pages collection, and pages for desktop clients within the Mobile Browse Pages collection. These pages do not function with the included renderers, and should instead be included within the appropriate collections. * WB-1307: Under certain circumstances, it may not be possible to delete text from Rich Text Editor if the text was pasted from a Microsoft Word document. * WB-1412: It may not be possible to copy and paste content within a Rich Text Editor if another instance of the Rich Text Editor is already present on the screen. * WB-1414: If Workbench runs under SSL, all Media MDEX-based images appear blank in the authoring environment. * WB-1429: The legacy record selector fails with a large numbers of records. It is being deprecated in favor of the SpotlightSelectionEditor which allows you to select from larger datasets. * WB-1451: When viewing an application in an authoring environment you may see the following error: "... cannot be displayed because it contains errors." This can happen because the browser is not authenticated with Workbench. To prevent this error, ensure that the browser has an active session with Workbench. * WB-1530: Leaving EAC Admin Console open for prolonged periods of time while it is enabled for auto-refresh results in increased volume of data written to Workbench catalina.out log file. * WB-1563: In Experience Manager, creating a new folder or a collection will empty the clipboard. This does not result in data loss. The user has to repeat the cut or copy operation to re-populate the clipboard. * WB-1573/BUG14605: The formatting for empty reports in Workbench is occasionally poor. * WB-1589: When importing a site into Workbench, error logs may contain spurious error messages referring to [PublishService]. These occur due to premature attempts to publish the content to the MDEX Engine prior to the completion of the import operation. The final [PublishService] operation should resolve successfully. * WB-1635: The content tree in Experience Manager may expand beyond the viewable area. In these cases, refresh the tree to make all content visible. * WB-1675: The authoring reference applications come with logging turned on and log to the same log server as the live reference applications. Logging can be disabled for the authoring apps by modifying their assembler-context.xml file. * WB-1911: Reordering of selected records in the SpotlightSelectionEditor and in BoostBuryRecordEditor does not always work in Internet Explorer 8. In cases where reordering does not work for a specific record, it generally still works for other records in the same table. * WB-1950: Switching templates from using SpotlightSelectionEditor to deprecated RecordListEditor results in existing content not displaying properly in the editor UI, and the microbrower will not behave properly with respect to selected records. User has to re-select the records. * WB-1965: Some users may see incorrectly encoded characters while exporting content. Be sure to update your system level encoding, and verify the encoding of all export files you create using the export_content.bat script. * WB-1969: Internet Explorer may try to run Workbench in compatibility mode which causes many display issues. Turn off compatibility mode for accessing Workbench. * WB-1976: You cannot add an LDAP user with an invalid email address using the User Management tool. You can, however, add an LDAP group that contains a user with an invalid email address, but you cannot modify any permissions for that user. To fix this, an LDAP administrator must correct the user's email address directly in LDAP. * WB-1984: If you have configured Workbench to use SSL for Web browser connections, the Preview feature in Experience Manager might stop working when you resubmit a page in Internet Explorer. * WB-2027 and WB-2100: When you add a user segment in Workbench, do not enter a name with the percent sign (%) or ampersand (&) characters. No error message displays when you save it, but this action results in a user segment name with a string of numbers instead of the intended name. Similarly, when you add an entry or synomym in the Thesaurus, do not enter a percent sign (%) or an ampersand (&). This results in a blank entry for both one- and mult-way entries. There is no error message. * WB-2045 The Back and Forward buttons in Internet Explorer 9 might be disabled when you try to use the Preview feature in Experience Manager. * WB-2078 The Selected Records dialog in Experience Manager does not support saving the ampersand (&) character in a navigation state or search query. * WB-2107 If you create an application with a number as the first character in its name, dynamic slots do not work for that application in Experience Manager. * WB-2118 Content XML generated by the SpotlightSelectionEditor is incompatible with the microbrowser when downgrading to the RecordListEditor. If you change editors and then modify the search query for a dynamic content spotlight, you must remove and then re-select the dimension values for the navigation state before saving changes. This issue is not present when using the RecordListEditor to spotlight static records. * WB-2122 If you create a site with the same name as one you have previously deleted, all users who had access to the original site at the time of its deletion will have the new one appear in their list of available sites in Workbench. However, they will not have access to any tools that they were not explicitly granted, and their home page for that site will be empty. * WB-2124: If a Workbench administrator adds an LDAP group (A) as a member of another LDAP group (B), then an LDAP user who is member of group A but not group B cannot log in to Workbench. Endeca Assembler * ASM-305: The IBM 1.5 Java Runtime Environment is not supported for deployments that use the Assembler Java APIs. Deployments that rely on the IBM 1.5 JRE should instead use the Assembler Service API, and host the assembler service in a Web container that uses any of the supported JREs. * ASM-314: It is not possible to audit application content that is contained within an