====================================================================== Endeca Discovery Framework GENERAL (1.2) - Release Date: July 2010 - The release notes may have been updated since the release date. Access the Product Downloads section of the Endeca Developer Network (EDeN) at https://eden.endeca.com for the most recent version of the release notes. NEW FEATURES (1.2) - A new Endeca Attribute Settings component in the Control Panel allows you to change the end-user-visible names used by Discovery Framework for properties and dimensions in the MDEX Engine. These display names are used by the Guided Navigation, Breadcrumbs, Range Filters, Record Details, and Results Table components. - The Chart component added support for Analytics statements that use two metrics and one group-by, in addition to the previous support for statements with one metric and two group-bys or one metric and one group-by. - The default Discovery Framework bundle has been upgraded to use Apache Tomcat 6 and Java 6. - Discovery Framework has been upgraded to support (and require) Internet Explorer 8 and Firefox 3.6. - The Advanced Visualization component has been upgraded to support (and require) Xcelsius 3.1. KNOWN ISSUES (1.2) - BUG7144: Flash Player 10.1 problems with Advanced Visualization. When viewing the Advanced Visualization component in a browser with Flash 10.1, certain features do not work. Specifically, drilldown and mouseover labels in the DrillDownChartExample fail, and all sample movies may fail to load data when the movie first appears on the page, though they do load data once the data source has changed due to a refinement or removal of a breadcrumb. Custom visualizations you create in Xcelsius may encounter the same problems with Flash 10.1. To work around this issue, use Flash 10.0. - The default Tomcat 6/Java 6 bundle can log NullPointerExceptions on org.apache.tomcat.util.net.NioEndpoint setSocketOptions during startup. This is a known issue in Liferay (LPS-4021) that can be ignored, since it does not affect any functionality. - BUG7106, BUG7043: In the Chart and Results Table components, Analytics statements using the TRUNC or EXTRACT functions will fail. This is due to a specific interaction between these components and the Endeca Java Presentation API that triggers TT BUG10979 in the Presentation API. - BUG7147: Look and Feel menu causes "stop running this script" message in IE8. Some users report that when selecting the Look and Feel option in a component, they are prompted with an Internet Explorer dialog asking to stop a long-running script. Users should choose to allow the script to continue; if they do, the Look and Feel functionality will work. FIXED IN THIS RELEASE (1.2) - BUG6838: You could not set or test an Analytics statement in the Results Table preferences if the current view of the Results Table was sorted by a column. - BUG6927: When you changed the data source in the Record Details component, it did not clear its record spec and tried to display the previous data source's record. - BUG6974: Once you sorted the Results Table component, you could not unsort. - BUG6978: There was a JavaScript error when adding the Data Sources component to a page. - BUG6983, BUG7046: Results Table column sampling was incorrect. When adding the Results Table component to a page, it makes a best guess at which columns to display. This guess has been significantly improved. - BUG6986: After loading a bookmark, the Results Table would show the Bookmarks component's contents when clicking on "View Detail..." - BUG7010: There was an error in the Results Table when sorting on certain Analytics columns if the columns had been reordered in preferences. - BUG7011: There was no horizontal scrollbar on wide tables/tabs in the Results Table. - BUG7028: The Results Table did not empty its contents if the current refinement state returned zero records. - BUG7047: Guided Navigation mishandled non-dimension-grouped dimensions unless they appeared first. - BUG7070: CSV export limits were too high and not configurable. - BUG7077: The Results Table fired two identical queries to get records on first load. - BUG7079: The Bookmarks component failed if the Results Table component had concrete (non-default) preferences. - BUG7081: The SDK README incorrectly pointed to a separate shared lib package. - BUG7089: The Breadcrumbs "Delete All" button link target was too small. - BUG7102: the Breadcrumbs Delete button for searches was subscripted when the component was in a narrow column. - BUG7180: Page transition parameters were not being properly cleared and set. - BUG7182: Paging math was incorrect when "records per page" was changed. ====================================================================== Endeca Discovery Framework GENERAL (1.1) - Release Date: May 2010 - The release notes may have been updated since the release date. Access the Product Downloads section of the Endeca Developer Network (EDeN) at https://eden.endeca.com for the most recent version of the release notes. NEW FEATURES (1.1) - The overall look and feel of the Discovery Framework has been improved through changes to the portal theme and to individual components. - The Results Table, Guided Navigation, and Breadcrumbs components have been significantly rewritten to improve functionality and user experience. - The Range Filter component is new in this release. - Switching a component into edit mode now happens asynchronously and does not reload the entire page. KNOWN ISSUES (1.1) - BUG6841: Internet Explorer 7 performance is poor. The runtime performance of IE, expecially when you have a Results Table component on your page, is suboptimal. You may encounter a warning message from IE stating "A script on this page is causing Internet Explorer to run slowly." Performance in Firefox is good. - BUG6834: The Results Table component does not support the same property in multiple columns. If you add the same property to multiple columns, only the last column for that property will render. Additionally, Internet Explorer may throw a JavaScript error when attempting to switch column sets. - BUG6838: The Results Table component does not allow you to test or save an analytics statement if the table is 1) currently showing base (non-analytics) records, and 2) currently sorted. - BUG6831: There are issues around the handling of inert dimension values in the Guided Navigation and Breadcrumbs components. When your breadcrumb contains inert (non-navigable) dimension values and you remove certain parts of that breadcrumb, the Guided Navigation component may not show its in-context breadcrumbs and exposed dimension state properly. - BUG6868: The Range Filter component's slider does not prevent its minimum value from being greater than its maximum value. It is possible to set this either via the portlet preferences or by dragging the min/max slider handles past each other. If you do this, you create an invalid query by setting the range's lower bound above its higher bound. - BUG6853: Date-based range filters do not display properly in breadcrumbs after they are loaded via a bookmark. These range filters do display properly when they are directly applied from the Range Filter component. - Date-based range filters only support epoch time values in the MDEX Engine. To use a date-based range filter, the target property in the MDEX Engine must be formatted as an epoch time. Other data formats are not currently supported. FIXED IN THIS RELEASE (1.1) - BUG6158: You cannot reorder the tabs from the configuration screen of the Tabbed Component Container. - BUG6294, BUG6326: The Results Grid (Advanced) component may output corrupted visual artifacts when it does not have enough horizontal space or when an individual column does not have enough horizontal space. ====================================================================== Endeca Discovery Framework GENERAL (1.0) - Release Date: March 2010 - The release notes may have been updated since the release date. Access the Product Downloads section of the Endeca Developer Network (EDeN) at https://eden.endeca.com for the most recent version of the release notes. KNOWN ISSUES (1.0) - BUG6255: There is no validation for data source identifiers. If you create a data source with a space in its identifier (either its JSON filename or its "id" attribute), it will appear in the data source chooser and the Data Sources component; however, you will get errors when attempting to select the data source in the chooser or when a component tries to query the data source. Validation should be added for data source initialization to check for a valid data source identifier. - BUG6158: You cannot reorder the tabs from the configuration screen of the Tabbed Component Container. It will appear as if the tabs can be reordered, but the new order will not be preserved. To reorder tabs, delete and then re-create tabs in the desired order. - BUG6294, BUG6326: The Results Grid (Advanced) component may output corrupted visual artifacts when it does not have enough horizontal space or when an individual column does not have enough horizontal space. To work around this issue, ensure that screen resolutions are large enough, that the component is placed in a wide enough column, and that you specify an explicit width in the component preferences for any column that displays incorrectly. - BUG6325: You cannot drag any components into the Component Container immediately after adding the Component Container to a page. After adding the Component Container to a page, reload the page in order to drag components into it. Similarly, you cannot add components to the Component Container or the Tabbed Component Container immediately after changing their layouts; you must reload the page after changing a layout in order to add a component. - BUG6015: You cannot drag any components to or from the Tabbed Component Container into or out of a free spot in the same column as the Tabbed Component Container. Instead, you can drag and drop a component into a free spot in a different column on the page, and then drag the component from that temporary position to its desired position. - BUG6368: You cannot drag any components from the Add Component menu into the Tabbed Component Container when using Internet Explorer. Instead, you can drag and drop a component into a free spot in a different column on the page, and then drag the component from that temporary position into the Tabbed Component Container.