Appkit SDK Release Notes

Subscribe

Latest Release: 4.11.0 (21 July 2020)

Fusion comes bundled with everything you need to get started.

Improvements

  • Ability to limit the results displayed by the result-list to a subset of the array

    • For example, the following: <result-list response="response" first="2" last="5"> will display the 3rd, 4th and 5th results in the response.

  • ES7 platform can now be configured whether or not to track total hits.

    • In the ES7 platform config (for example, resources/conf/platforms/elastic/elastic.conf) you can now add this config to track total hits: track-total-hits: true

    • By default, this will be false and will max out at 10000 as stated in the ES docs.

  • It is now possible to specify whether to include or exclude the range filter boundaries by specifying the fromExcluded and toExcluded attributes to the <query:filter> tag.

    • For example:

<search:query parameters="*" var="query">
<query:filter field="age" from="25" to="50" display="25 to 50" fromExcluded="true" toExcluded="true"> </query:filter>
</search:query>
  • Appkit no longer adds the apollo path prefix to Fusion API URLs. If still required, the path prefix may be set via configuration.

Bug Fixes

  • Fixed a bug where <search:response-statistics> are only updated when its specified response object is updated, not on any others

  • Added support for Angular expressions as a value for the Bookmark-list collection parameter

  • HighlightingUtils adds highlighting terms support when closing braces are absent

  • Fusion pre-authentication filter now uses the JWT token subject field for the user name.

  • In collaborate:saved-query-list, the show-more user click option now specifies the number of additional list items to display

Previous releases

4.10.0 (27 September 2019)

  • The FusionProxy endpoint /twigkit/api/fusion/* now accepts nested URI paths as expected. For example:

    /insights/twigkit/api/fusion/collections/<collection_name>
    /insights/twigkit/api/fusion/apps/<app_name>/experiments

    Previously, an HTTP 400 error occurred.

  • Removing filters using the <query:filter action="remove"> tag will no longer remove filters added with the <query:filter value="bar"> tag. For example, the following will leave the filter on value="bar" intact:

    <search:query var="query">
         <query:filter field="foo" value="bar">
         <query:filter field="foo" action="remove">
    </search:query>
  • Previously, using the Solr platform in compatibility mode forced exclusive boundaries on date range filters to become inclusive. This affected date range filters in the Fusion platform.

    This behavior is fixed. Exclusive boundaries on range filters now remain exclusive in compatibility mode.

  • Toggle events now fire as expected when using toggle controls.

4.9.0 (27 September 2019)

  • The FusionProxy endpoint /twigkit/api/fusion/* now accepts nested URI paths as expected. For example:

    /insights/twigkit/api/fusion/collections/<collection_name>
    /insights/twigkit/api/fusion/apps/<app_name>/experiments

    Previously, an HTTP 400 error occurred.

  • Removing filters using the <query:filter action="remove"> tag will no longer remove filters added with the <query:filter value="bar"> tag. For example, the following will leave the filter on value="bar" intact:

    <search:query var="query">
         <query:filter field="foo" value="bar">
         <query:filter field="foo" action="remove">
    </search:query>
  • Previously, using the Solr platform in compatibility mode forced exclusive boundaries on date range filters to become inclusive. This affected date range filters in the Fusion platform.

    This behavior is fixed. Exclusive boundaries on range filters now remain exclusive in compatibility mode.

  • Toggle events now fire as expected when using toggle controls.

4.8.0 (10 January 2020)

  • It is now possible to map a user’s LDAP roles to the application user’s group. This differs from the previous implementation to the AD pre-authorisation filter, in that it reads the groups directly from the user object instead of querying for AD groups that the user belongs to.

    To enable this filter, add a configuration file under conf/security/ldap/provider.conf with the following parameters:

    enabled: true
    user: #Service account used to connect to LDAP.
    password: #Password for the service account. This can be encrypted using the twigcrypt binary.
    url: #Full URL to the LDAP server.
    user-search-base: #LDAP search base to restricted the search to.
    user-search-filter: #LDAP search filter to restrict the LDAP search.
  • It is now possible to use basic authentication against a Solr cloud platform using the parameters userName and password in the platform configuration.

  • The value of a highlighted field is now stored as the "display" field value, rather than replacing the original "actual" field value.

4.7.0 (22 November 2019)

  • Appkit 4.7.0 adds support for Elastic 7.4.

  • A new filter, find, is added which searches the scope hierarchy to find a specified variable. For example: {{ 'myVariable' | find:this }}.

  • The twigkit.http.filter.DevelopmentErrorFilter is replaced by the twigkit.http.filter.ErrorFilter. If you are using the twigkit.http.filter.ErrorFilter parameter in your web.xml file and an AJAX request fails, a JSON response is received identifying the status code of the REST call and any underlying causes. Previously, an HTML response was received.

    Example configuration:

    <filter>
        <filter-name>ErrorFilter</filter-name>
        <filter-class>twigkit.http.filter.ErrorFilter</filter-class>
        <init-param>
            <param-name>responseCode</param-name>
            <param-value>400,405,406,500,501,503</param-value>
        </init-param>
        <init-param>
            <param-name>excludedPaths</param-name>
            <param-value>/,/login,/login/</param-value>
        </init-param>
    </filter>
  • Accessibility improvements are made to the search breadcrumbs. The text, x, that removed the breadcrumb is replaced by an icon with the alt-text "Remove this term from the query" for use by screen readers.

    Remove this term from the query