======================================================================
Endeca Discovery Framework

GENERAL (1.5)

  - Release Date: April 2011
  
  - 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.5)

  - Discovery Framework 1.5 continues to support IAP 6. In addition, 
    Discovery Framework 1.5 adds support for the Latitude 2 stack, featuring
    the MDEX Engine 7.1. These release notes refer to features and functionality 
    that may differ between the two versions.

    For details on the Discovery Framework for IAP 6. see the Discovery 
    Framework 1.5 documentation set. For details on the Discovery Framework for 
    Latitude 2, see the Latitude 2 documentation set. 

  - Discovery Framework has upgraded to Jackson 1.7.2.

  - Compare (new component): this component allows end users to view two or 
    more records side-by-side in order to analyze differences and similarities between
    them. The details are presented in a tabular format for easy comparison.

  - Tag Cloud (new component): this component provides a visualization that lists 
    textual attribute values (or "tags") and their significance in the current result set.  
    It can be configured to allow end users to filter results to only those containing a
    particular tag.

  - The Bookmarks component has been enhanced with the following new features:
       * Support for type-ahead filtering by bookmark name and description
       * Support for paging
       * Support for sharing bookmarks via link and email
       * Support for a variety of end-user view modes (showing controls only, 
         showing lists only, or showing both)

  - The Liferay code in use by Discovery Framework has been updated
    to Service Pack 5 (5.2.9). This carries a large number of stability,
    security, and performance fixes.

  - The Data Sources component now has an additional "Clear attribute cache"
    control that clears Discovery Framework's session cache of the known
    attributes and attribute groups in a 7-series MDEX Engine. If you make
    changes to attributes or groups in the MDEX Engine Tools, you must either 
    start a new session or clear the Discovery Framework cache in order to see
    those changes.

BEHAVIOR CHANGES (1.5)

  - BUG8934 In the Range Filter component, users are now prevented from setting more 
    than one range for an attribute. Once a range filter is applied for an attribute, 
    that item will now no longer appear in the component. To change the range for that 
    attribute, the user must remove the filter from the Breadcrumbs component, then 
    return to the Range Filter to set a new range for the attribute.
	
  - The manner in which you enter the Liferay license key in order to activate
    your portal has changed. For details on activating your portal, see the
    Discovery Framework Installation Guide (for IAP 6) or the Latitude Installation 
    Guide (for Latitude 2).
  
  - Presentation API (MDEX 6) data sources now, by default, ignore the
    Endeca.NumAssigns, Endeca.DataSize, and Endeca.NumWords properties. These
    properties are automatically generated by Dgidx during the indexing process,
    but they cause problems in some components, most notably in the Results
    Table component if an end user attempts to sort on one of these properties.
    If you had previously used these properties in a component, you may still
    see references to them.
	
  - The version of Apache Tomcat included in the default Discovery Framework
    bundle no longer ships the files required to install Discovery Framework as
    a Windows service. You must download these files separately from Apache.
    For more details, see the Discovery Framework Installation Guide (for IAP 6) 
    or the Latitude Installation Guide (for Latitude 2).
    
KNOWN ISSUES (1.5)

  - BUG7878 The Data Sources component displays an inaccurate index update date
    (Wed Dec 31 19:00:00 GMT 1969) whenever a user clicks an MDEX 7 data source
    in order to validate its connection.
  
  - BUG9743 When the Search Box component is bound to an MDEX 7 data source, it
    will not display ancestors for type-ahead search suggestions, even if the
    power user has enabled "Show intermediate values" for the search configuration.
  
  - BUG9780 When the Guided Navigation component is bound to an MDEX 7 data source, 
    attributes not enabled for value search erroneously display the type-ahead
    filter interface to the end user.

  - BUG10039 When a component is bound to MDEX 7 data sources that take longer 
    than 60 seconds to respond, the connection may time out, causing the component
    to fail to render its contents.  When this occurs, a "could not send message"
    error will appear in the logs, caused by a SocketTimeoutException that indicates 
    "read timed out."  To avoid this problem, ensure that your MDEX Engine is running
    on sufficient hardware to support the application's scale needs.
	
MIGRATION NOTES (1.5)

  - BUG9692 Persisting the bookmark state for a component would fail if the
    component's internal ID was longer than 75 characters due to a database
    column length limit. Notably, this would fail for the Results Table (BETA)
    component. The database column length is now increased for all new
    installations. Upgrades to existing installations need to change the column
    length manually. See the Discovery Framework Migration Guide (for IAP 6) for 
    more details.

FIXED IN THIS RELEASE (1.5)

  - BUG6319 In the Search Box component, the entire highlighted area for type ahead 
    suggestions is now clickable.

  - BUG6869 In the Range Filter component, expanded attributes now remain expanded 
    as the user acts on other components or changes pages and returns to the current 
    page.
    
  - BUG7739 In the Guided Navigation component, an error message is now displayed if 
    a request times out.
  
  - BUG7966 In the Bookmarks component, users are now restricted to 72-character bookmark 
    names. 

  - BUG7985 The Data Source Bindings component now shows the user-customized name for 
    each component instead of the default portlet name.
  
  - BUG7991 In the Breadcrumbs component, expanded groups of refinements will now remain  
    expanded until all refinements in the group are removed or the group is manually 
    collapsed. 
      
  - BUG8133 The Metrics Bar component will no longer cause components below it to have 
    rendering issues when a user transitions to a page that has a configured Metrics Bar 
    component.
  
  - BUG8390 In the Bookmarks component, cancelling entry of a new bookmark now clears the 
    input fields. The next time a user adds a new bookmark, he or she will be presented with 
    empty name and description fields, instead of seeing the previous (unsaved) entries.
  
  - BUG8693 In some instances, it was possible to persist multiple Framework Settings
    with the same key into the database. This did not affect functionality, since calling 
    code would ignore the duplicates. Now, we ensure only one setting for a given key can 
    exist. Note that if you currently have duplicate settings, those duplicates will remain, 
    but no more will be added.
  
  - BUG8906 Tab switching performance for the Results Table (BETA) component has been greatly 
    improved. 

  - BUG8976 The Breadcrumbs component no longer allows text overflow outside of the 
    component borders.

  - BUG9034 In the Guided Navigation component, non-navigable properties are no longer 
    displayed in the attribute group selector in preferences.

  - BUG9141 In the Results Table (BETA) component, the end user now has access to the "refresh 
    with default sort" button, even when paging is disabled.

  - BUG9142 In the Results Table (BETA) component, clicking the "Reset Preferences" button now 
    reloads the last saved preferences, instead of reverting to the component defaults.

  - BUG9195 In the Results Table (BETA) component, the checkboxes in the left hand column are 
    now aligned properly with the rest of the row.

  - BUG9272 In the Results Table (BETA) component, csv export now exports all columns, locked 
    and unlocked.

  - BUG9450 In Results Export, when performing a record export, the csv export now includes all 
    values for multi-assigned properties.

  - BUG9612 In the Guided Navigation component, selections from a parent data source now propagate 
    automatically to child data sources.

  - BUG9719 In the Metrics Bar component, the "Respect query state" checkbox in preferences mode 
    now remains checked when the user loads the analytics query.

  - BUG9326 In the Guided Navigation component, type-ahead now shows a "n of m results shown" message 
    when type-ahead returns more results than the threshold configured in preferences.

  - BUG9381 Previously, the Attribute Settings administrative component added attributes to a set 
    in the order the user selected those attributes. Now, it adds the attributes in the order they 
    exist in the "All Attributes" panel.

	
======================================================================
Endeca Discovery Framework

GENERAL (1.4)

  - Release Date: January 2011
  
  - 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.4)

  - The endeca-async JavaScript library and some of the JavaScript within
    components have been optimized and upgraded so as to avoid the occurrence
    of "stop running this script" errors. These errors appeared almost
    exclusively in Internet Explorer.

  - The Guided Navigation component's end user interface has been optimized 
    to improve JavaScript performance, including "stop running this script" 
    errors that could occur in Internet Explorer.

  - The Guided Navigation component has integrated the use of globally 
    maintained attribute sets, which were introduced in Discovery Framework 1.3. 
    Power users can now configure and maintain meaningful sets of properties 
    and dimensions in the Control Panel, and select the appropriate groups to 
    display in the Guided Navigation component. To support an easy upgrade 
    path for Discovery Framework users accustomed to using dimension groups 
    for previous releases of the Guided Navigation component, the Attribute 
    Settings administrative component can automatically create attribute sets 
    for dimension groups configured in the MDEX Engine.

  - jQuery 1.4.4 is now available for use by custom component developers in 
    the "jq14" variable. The "jQuery" variable still points to jQuery 1.2.6.

  - The default security manager has been updated to recognize the roles a 
    user belongs to by merit of the user's group memberships as well as the 
    roles to which the user is directly assigned.

  - The Discovery Framework now supports deep linking, allowing users and 
    external systems to access a specific page, tab, and query state within 
    their Discovery Framework application by specifying the relevant 
    information on the URL.

  - Switching tabs within the Tabbed Component Container occurs asynchronously,
    rather than requiring a full page refresh.	

  - The user interface of the Performance Metrics administrative component has 
    been improved.

  - The Data Source Bindings component is no longer in Beta.

  - The Record Details component has been enhanced with the following features:
       * Users can export the data for the displayed record.
       * Users can print the displayed details of the record.
       * Power users can configure attribute sets to display, and the ordering 
         of attributes and attribute sets.
       * Power users can configure the header field to display.
       * Power users can configure display of the Actions menu and the actions
         to include in the menu.

  - Significant revisions and enhancements are available for early use in
    a Beta release of the Results Table component. Included in this early
    release are the following new features:
       * Power users can configure attribute sets to display, and the ordering 
         of attributes and attribute sets.
       * Power users can configure a link for each record to an external system.
       * Power users have enhanced configuration options for creating custom
         action columns and binding action links to attribute columns.
       * Power users can configure a default sort order for records.
       * Power users can configure a default number of records per page, as well
         as the end user options for page sizes.
       * Power users can enable or disable display of end user paging and sorting
         controls. This can be used to display a summary table in a dashboard view.
       * End users can refine results by clicking dimension values in table cells.
       * End users can view a totals/summary row for an Analytics-enabled table.
       * Power users can configure a threshold for the maximum number of records
         over which Analytics queries will be performed.
       * End users can print the contents of the Results Table.
      
    Since this component is in Beta, Endeca will not issue hotfixes for it on the 
    1.4.0 product line. Ongoing work will target usability improvements, 
    performance enhancements, and overall polish. 
       
    This release also includes the previously-available version of the Results 
    Table component, to allow application owners the choice of adopting the Beta 
    enhancements or continuing to use the previously-released version. If you have 
    feedback on either component, please post it to the Discovery Framework forum 
    on EDeN.
       
  - The Discovery Framework documentation set now includes a Migration Guide, 
    where you can find information about upgrading from a previous version of 
    the Discovery Framework.

BEHAVIOR CHANGES (1.4)

  - Endeca has disabled notification of Liferay's out-of-the-box plugin updates. 
    This notification could cause delays and misleading errors at startup for
    deployments where the application server did not have direct access to the
    internet. Additionally, Endeca does not ship any of these plugins, so the 
    check was extraneous for most deployments. To re-enable this check, simply
    comment out the three properties under the "Plugin" section of your
    portal-ext.properties file.

  - The default security manager no longer responds to changes to a user's role
    memberships during the user's session. Instead, the user must log out and
    log back in for the user's new roles to be recognized. See the Migration 
    Guide for details.

  - Bugs 7106 and 7043 have been resolved by fixes in the Endeca IAP Solution
    6.1.4 Java Presentation API. In Analytics-enabled components (e.g. Chart and 
    Results Table), Analytics statements using the TRUNC or EXTRACT functions 
    would fail. This was caused by a specific interaction between these components 
    and the Endeca Java Presentation API that triggered BUG10979 in the 
    Presentation API. This bug has been fixed in Endeca IAP Solution 6.1.4 
    Presentation API. The 6.1.4 version of endeca_navigation.jar can be used to
    resolve this issue for all Discovery Framework applications deployed with 
    MDEX 6.1.4 data sources or Endeca Latitude 7.x data sources.
    
  - The default theme shipped with the Discovery Framework includes a directive
    that requires Internet Explorer 8 to operate in Standards Mode, even if
    the browser is configured for Compatibility Mode.
    
  - The Chart component no longer tests that the Corda server is active prior
    to rendering a chart. In previous releases, each Chart request required the
    component to ping the Corda server. While this ensured more graceful error
    handling for development environments where the Corda server might not be
    deployed consistently or correctly, it also introduced unnecessary overhead
    for stable production environments.
    
  - The Discovery Framework's event namespace has been changed from 
    "http://endeca.com/discovery" to "http://endeca/discovery". Custom component
    developers will need to update event handler method annotations and the 
    custom component's portlet.xml (supported-processing-event, 
    supported-publishing-event, and event-definition elements) to reference the
    updated namespace.

MIGRATION NOTES (1.4)

  - Custom components need to be rebuilt against the new SDK, in order to update
    the SDK-provided common files.

  - Custom components are now required to have their own web.xml, rather than 
    pulling it in from the endeca-common-resources shared library.

  - Custom components must rewrite any JavaScript postRender overrides. See the 
    Migration Guide for more information.  

  - QueryFunction.init(JSONObject) now only throws a JSONException. Custom
    query functions may need to update their method signature.

  - Previously, Liferay's default portlets were disabled via the
    liferay-display.xml file. Now they are disabled via the
    liferay-portlet-ext.xml file. This change means that disabled portlets
    do not appear in the Control Panel, as they did previously.

  - When using attribute sets in the Guided Navigation or Results Table 
    components, there are some conditions where the "Other" set will appear to 
    have nothing in it. In this case, go to the Attribute Settings component in 
    the Control Panel, select the affected data source, and expand the "Other"
    set.

  - Discovery Framework 1.4 includes a Liferay-supplied hotfix dealing with LAR
    files. Pre- and post-hotfix LAR files are not compatible. In other words,
    it is not possible to import a pre-Discovery Framework 1.4 LAR file into 
    Discovery Framework 1.4, and it is not possible to import a 1.4 LAR file 
    into a previous Discovery Framework release. Note that Liferay's LAR files 
    are, in general, not compatible across Liferay releases, and the Liferay 
    hotfix in question is treated as a separate release.

  - The default security manager now assumes that all security filters
    are record filters. If it encounters a non-record-filter security filter,
    it ignores that filter and logs a warning. Users who want to override this
    behavior can do so by writing their own security manager and overriding
    the applySecurity method.


FIXED IN THIS RELEASE (1.4)

  - BUG7023 Components now display appropriate messages when no data sources are
    configured or when the data source to which they were bound no longer
    exists.

  - BUG7130 Deploying Discovery Framework into a firewalled environment that
    does not have internet access no longer results in errors on startup. Please
    see the Known Issues list above for more information on this change to
    Liferay's out-of-box plugin updates.

  - BUG7171 The Attribute Settings administrative component no longer allows you 
    to select a data source if that data source does not support attribute sets
    or display names.

  - BUG7400 In the Framework Settings administrative component, the df.container
    is no longer displayed, since that setting is not supported.

  - BUG7640 The default security manager has been updated to recognize the roles
    a user belongs to by merit of the user's group memberships as well as the
    roles to which the user is directly assigned.

  - BUG7740 The core Liferay portal now shuts down/restarts gracefully in
    Websphere Application Server.

  - BUG7862 In the Attribute Settings administrative component, clicking on an
    attribute set's title no longer shows that set. Instead, the expand/contract
    icon should be used to show or hide the set.

  - BUG7918 The Attribute Settings administrative component no longer loads an 
    invalid data source on startup, even if that data source is the first one in 
    the data source list.

  - BUG7921 In the Attribute Settings administrative component, hitting the Enter
    key while editing an attribute's display name no longer checks off the next
    attribute in the list.

  - BUG7934 In the Attribute Settings administrative component, deleting an
    attribute from a set no longer causes problems with the alternating row
    colors in that set's user interface.

  - BUG7938 In the Attribute Settings administrative component, renaming an
    attribute set now properly updates the "All Attributes" panel title.

  - BUG7950 In the Attribute Settings administrative component, the New Attribute
    Set form field now properly clears after the set is created.

  - BUG7951, BUG8060 The Data Source Binding administrative component no longer
    styles certain non-hyperlinked elements with an underline, since underlines
    typically connote hyperlinks.

  - BUG7952 The Data Sources administrative component no longer throws a
    JavaScript error when a user clicks in the 5-pixel whitespace between the 
    data source's icon and its name.

  - BUG8033 The Attribute Settings administrative component now properly
    updates the "Add selected attributes to set" dropdown list when you rename
    an attribute set.

  - BUG8068 The Framework Settings administrative component now validates input
    values for certain settings. Most importantly, it validates the security
    manager and state manager inputs, since invalid values for these would
    prevent the portal from starting up.

  - BUG8085 The Data Source Bindings administrative component no longer logs a
    stack trace whenever the Tabbed Component Container exists on a page. Note
    that the stack trace was benign and did not impact functionality, but was
    still distracting.

  - BUG8092 All out-of-the-box QueryFunctions now provide no-arg constructors,
    and the SDK has been updated with comments about the requirement for a
    no-arg constructor. These missing constructors caused exceptions when
    deserializing a list of functions.

  - BUG8103 The Endeca Theme has a much improved visual display of child pages.

  - BUG8119 The default security manager now assumes that all security filters
    are record filters. If it encounters a non-record-filter security filter,
    it ignores that filter and logs a warning. Users who want to override this
    behavior can do so by writing their own security manager and overriding
    the applySecurity method.

  - BUG8138 Discovery Framework now incorporates a Liferay-supplied hotfix
    that addresses missing pages when importing a LAR, if those pages used
    different layouts and the pages and layouts were ordered under certain
    conditions.

  - BUG8373 The user is no longer forcibly logged out of Discovery Framework
    if the user has not performed a full-page refresh within the last 30
    minutes. Now, each component refresh (such as when selecting refinements
    from the Guided Navigation component and automatically refreshing the 
    Breadcrumbs component) extends the user's session.

  - BUG8474 The updated Corda servlet provided in DF 1.3.1 no longer
    causes JVM JIT crashes when used on certain versions of the Sun JVM.

  - BUG8513 The NegativeRefinementFilter now properly escapes reserved
    characters in its values. This fixes a problem where Guided Navigation
    negative refinements caused query problems if the refinement contained
    one of the following characters: (:,\) 

  - BUG8965 Discovery Framework now includes the appropriate html meta tag
    to tell IE8 to operate in Standards Mode. Previously, the user had the
    choice to switch to Compatibility Mode, even though the Discovery 
    Framework does not work in Compatibility Mode.


======================================================================
Endeca Discovery Framework

GENERAL (1.3.1)

  - Release Date: November 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.3.1)

  - A new Cross Tab component provides a table that allows end users to 
    perform comparisons and identify trends across several cross sections
    of data. A cross tab consists of a specific configuration of rows, 
    columns, and summary cells that together make up the table body. The 
    values displayed in the header rows and columns represent every possible
    grouping value of the specified data fields. Summary cells exist at the
    intersection of rows and columns. The value of a given summary cell is a
    metric corresponding to the intersection of those two groupings. 

  - The Results Table, Record Details, and Find Similar components now allow
    users to interact with representative aggregated records when bound to 
    a data source that has a Record Aggregator function configured. Similarly,
    the Guided Navigation component will display refinement counts for the
    representative records, rather than the underlying base records. For 
    information on how to configure a data source using a Record Aggregator
    function, see the DF Install Guide.

  - The Chart component contains the following enhancements:

       * Users can now export the Analytics results that are powering the chart.

       * Users can now print a page containing the chart with context information 
         (breadcrumbs).

       * Power users can now enable a "Top-N Sort" control, which allows users to 
         toggle the sort applied on the Analytics statement powering the chart. 
         Users can view the "top N" or "bottom N" results for a given metric, 
         where "N" is a number configured by the power user.

       * Power users can now set a threshold for the maximum number of records the 
         Analytics statement should return. When exceeded, a message is displayed 
         indicating that the user should further refine the result set in order to 
         see the chart.

       * Power users can now configure a chart title that will display variable content, 
         such as the user-selected metric or group-by.

       * Power users can now configure multiple charts within a single instance of the 
         component. When more than one chart has been configured, the user can switch 
         between them dynamically by selecting a given chart from a drop-down list.

       * Chart now makes use of the Corda Redirector for chart generation and 
         rendering. The Corda Redirector acts as a proxy to the Corda Server or Corda 
         Server servlet which is responsible for generating the chart images. The new 
         approach provides a greater level of control over where Corda fits into the 
         network supporting the Discovery Framework.

KNOWN ISSUES (1.3.1)

  - The Chart Metrics Selector, which is where the power user sets which metrics will
    be visible in the rendering of the chart, only appears after the Save Preferences 
    button has been clicked. In addition, whenever the power user adds or removes a 
    metric in the Analytics statement, Save Preferences button must be clicked again 
    to update the Metrics Selector. The default behavior is that all metrics are
    visible in the chart.

  - When an invalid metric name is entered into the Chart's Metric Options, the
    power user is not warned. If the invalid metric is selected by the end user, 
    the result will be an empty chart. To fix this problem, the power user can 
    update Metric Options with a valid metric returned by the statement.

  - New-line characters in the Chart's list of Metric Options do not render 
    properly in Internet Explorer after preferences are saved, making all metrics 
    appear on one line. This does not impact the user's ability to toggle metrics,
    but may be confusing for the power user who edits the Chart's preferences
    using Internet Explorer.

  - When testing an Analytics statement in the preferences editor for an Analytics-
    powered component, the Save button will remain disabled even when a warning
    condition occurs. Once the power user addresses the issue in the statement and
    clicks the test button again, the Save button is re-enabled upon successful
    validation of the statement.

  - Please read the known issues for previous versions as well.

FIXED IN THIS RELEASE (1.3.1)

  - BUG7825 A Cross-site Scripting (XSS) vulnerability was addressed in the 
    Corda Server servlet. Note that as a result of this fix, the URL that 
    verifies that the servlet is running (http://server.example.com:8080/
    corda/server) now produces an empty white box instead of the Corda logo.

  - BUG6259 The Breadcrumbs "clear all" button now only removes query 
    functions that are displayed and supported by the Breadcrumbs component 
    from the backing data source. It no longer removes record filters
    that have been configured in the data source's list of base functions.

  - BUG8076 The dimension configuration editor used in preferences for the
    Guided Navigation and Search Box components now presents the list of
    available dimensions along with a paging toolbar, displaying only 100
    dimensions at a time. This alleviates performance issues with data sets
    containing large numbers of dimensions.

  - BUG8128 The Attribute Settings component in the Control Panel now
    presents all attributes and the attributes within sets along with a 
    paging toolbar, displaying only 60 attributes at a time. This alleviates
    performance issues with data sets containing large numbers of dimensions.

  - BUG8091 If an invalid metric is added to the Metric Options list in the
    Chart component's preferences editor, a warning message is displayed 
    when the Analytics statement is tested, indicating that an unknown key
    was referenced. Previously, an invalid metric resulted in an indefinite
    "loading" state.

  - BUG8159 Dimension names containing percent symbols and other special
    characters now display properly in the Guided Navigation component.

======================================================================
Endeca Discovery Framework

GENERAL (1.3)

  - Release Date: October 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.3)

  - Discovery Framework now supports WebSphere Application Server 6.1,
    running on IBM JDK 1.5.
    
  - The Liferay code in use by Discovery Framework has been updated
    to Service Pack 4 (5.2.8). This carries a large number of stability,
    security, and performance fixes.

  - View transitions now allow you to specify a target tab of the
    Tabbed Component Container as well as a target page. View transitions
    are now available in the Results Table, Guided Navigation, Record Details,
    Find Similar, and Search Box components.
    
  - The Guided Navigation and Breadcrumbs components now support
    negative refinements.
  
  - The Guided Navigation component now lets you specify which dimensions
    should be exposed by default when the component loads.
  
  - The Guided Navigation component now has a preference for the maximum
    number of dimension values to show in a single dimension (the default
    is 500). Use this preference to control your user experience on very
    large dimensions.
  
  - The Search Box component now supports multiple search configurations,
    each specifying a data source, MDEX Engine search interface, matchmode,
    and a display name for breadcrumbs. The end user can choose between
    these search configurations at runtime.
    
  - The Search Box component now lets you choose which dimensions should be
    included for type-ahead suggestions.
    
  - The Range Filter component now supports histograms.

  - The Control Panel has been reorganized to have a "Discovery Framework"
    category containing all Discovery Framework-specific administrative
    controls.

  - The Data Source Bindings control panel is new in this release. This is
    a beta component and is therefore unsupported. This component allows
    you to change the data source binding for multiple components at the
    same time, without needing to edit the preferences of each component.
  
  - The Discovery Framework core APIs now support aggregate records. You
    can use these APIs for your custom components; aggregate record support
    for the standard Discovery Framework components will be added in future
    releases.

  - The Discovery Framework core APIs, the Attribute Settings control panel,
    and the Record Details component now support attribute sets. Attribute
    sets allow you to organize your properties and dimensions into named
    groups.  You can use these APIs for your custom components; support
    for the standard Discovery Framework components will be added in future
    releases.
  
  - Discovery Framework 1.3 contains multiple enhancements around integration
    with the upcoming MDEX 7 platform. Please contact your Endeca
    representative for more information about MDEX 7 integration.

KNOWN ISSUES (1.3)

  - JavaScript performance in Internet Explorer remains significantly
    poorer than in Firefox. From time to time, you may receive a warning
    from Internet Explorer about a long-running script. We continue to tackle
    this issue, but recommend switching to Firefox if you encounter problems
    in Internet Explorer.

  - Discovery Framework requires the Endeca Theme in order to start up and
    allow you to enter a license key. Even if you do not intend to use the
    Endeca Theme in production, please install the Endeca Theme from the
    components-1.3.zip file, start and configure Discovery Framework, then
    switch to your custom theme once Discovery Framework is functioning
    correctly.
    
  - You must install Discovery Framework to the root web context - "/" - for
    full functionality. If you install to another context, some images,
    JavaScript, and other necessary resources will not load properly. This
    limitation will be removed in a future release.
    
  - The method signatures for view transitions have changed. If you have custom
    components that use view transitions, please contact your Endeca
    representative for details on upgrading your component.
    
  - The Component SDK's build scripts do not function out of the box if you are
    using the standalone WAR package to install into your application server (as
    opposed to using the Discovery Framework bundle). You will need to modify
    paths within the SDK build scripts in order for them to work.

  - When configuring a child data source (i.e. a data source that specifies
    a "parentDataSource" property), you must explicitly set "securityEnabled"
    to true if you desire that feature. The "securityEnabled" property defaults
    to false if it is not specified.
    
  - The Freeform layout has been removed from this release because it was
    unstable when used with Endeca components. If you were using the Freeform
    layout, you will need to rebuild your pages.

  - Please read the known issues for previous versions as well.

FIXED IN THIS RELEASE (1.3)

  - BUG7152 Portlets would sometimes stick in Edit mode. This problem, which
    was persistent across sessions, has been fixed.

  - BUG7193 Chart component drilldown on a bar with a space in its name no 
    longer causes an exception in Internet Explorer.

  - BUG7267 In the Results Table component, sorting on a column with a period 
    in its name has been fixed.

  - BUG7329 The "+" character is no longer stripped from dimension display in 
    the Chart component.

  - BUG7342 Portlet and Security Manager SDK Eclipse projects no longer reference 
    xmlbeans.

  - BUG7401 Search Box type-ahead results now work when special characters are
    present.

  - BUG7480 Calling resetQueryState() on parent/child datasources, such as the
    Reset link in the sample portlet or the Delete All button in Breadcrumbs,
    would reset to the wrong state. This has been fixed.

  - BUG7526 Search Box type-ahead preferences no longer require a full page
    reload to take effect.
    
  - BUG7549 The Range Filter component could fail when using less-than filters
    against a property configured as a Date filter, if that property contained
    invalid date values. This has been fixed.

  - BUG7649 WebSphere: enabling Java 2 Security no longer prevents the server 
    from starting up correctly.

  
======================================================================
Endeca Discovery Framework

GENERAL (1.2.1)

  - 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.1)

  - A new Find Similar component provides end users with the opportunity
    to find other records that share common attributes with a specific 
    record of interest. Users can view specific records of interest in 
    the Record Details component and then click Find Similar to search 
    for records with similar attributes.

  - The Record Details component has been enhanced to support the "find
    similar" functionality offered by the new Find Similar component.
    A new button has been added that directs users to the Find Similar
    component so that they may attempt to find other records with similar
    attributes to the one being viewed.

  - A new Metrics Bar component allows users to quickly view metrics that 
    summarize various aspects of the underlying data.  The metrics
    displayed are based on Analytics statements written by the power user
    in the component's preferences editor, where the display formats of the 
    metrics can also be configured.  Power users can also set threshold
    violation indicators to alert the end users when a metric has reached
    a certain value or range of values.

KNOWN ISSUES (1.2.1)

  - BUG7441: The Metrics Bar component's preferences editor intentionally
    does not provide a Save Preferences button, but this means there is
    no way to toggle the "Respect data source query state" option on/off
    without re-testing the Analytics query and re-loading the metrics.

  - BUG7429: The Find Similar component logs an ERROR about being unable
    to store a com.endeca.navigation.PropertyMap object into session, as
    this object is not serializable. The error may indicate a possible 
    issue with the component during session deserialization, but this 
    generally should not limit an end user's ability to use the component.

FIXED IN THIS RELEASE (1.2.1)

  - BUG7401: The Search Box component's type-ahead results now work 
    properly when they contain punctuation such as an apostrophes
    or other special UTF-8 characters (for example, 'ü').

======================================================================
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.

