Upgrading to this version
In apps created with earlier versions of Fusion App Studio, you can Upgrade Appkit in Existing Apps.Upgrade Appkit in Existing Apps
Upgrade Appkit in Existing Apps
When you create an Appkit webapp, it uses a specific version of Appkit. Appkit releases occur independently of App Studio releases.You can upgrade web apps to use the latest version of Appkit.How to upgrade
- Stop the app.
-
In the
package.jsonfile at the root of your project, update theappkit-uidependency to the latest Appkit version, for example: -
In the
pom.xmlfile at the root of your project, update the value of theparent.versionproperty to the latest Appkit version, for example: - Upgrade the Appkit Social module, if required.
- Perform any additional upgrade steps that are required for a specific Appkit upgrade. See the Appkit Release Notes for more information.
- Start the app.
Additional upgrade steps
If you have previously specifiedrequestHandler: / in the platform suggestions configuration files of your apps, you can now remove this parameter.
In earlier versions, requestHandler: / was used to allow search term suggestions for apps using a query profile, but this parameter is no longer needed.
For example:
Upgrading from Appkit versions prior to 4.4
If you are upgrading from a version of Appkit prior to 4.4 then you may need to follow additional steps described in previous Release Notes.New features
No new features are included in this release.Improvements
Easier key navigation in result lists
To support easier keyboard navigation in result lists, for example by using the down arrow to move from result to result, Appkit result titles now use HTML heading tags. Specifically,<search:field styling="title"> tags now use <h3> tags instead of <p>.
Bug Fixes
- Fusion 5 authentication. Apps created using Appkit 4 and App Studio 4 can now authenticate against Fusion 5.0.
- Fusion sessions. Existing Fusion sessions are now correctly utilized when authorizing users against a service account.
-
Term suggestions. Search term suggestions no longer fail when using a Fusion query profile.
If you previously usedrequestHandler: /as a workaround for this functionality, carry out the upgrade step described in Additional upgrade steps above. -
Click tracking table results. The
<track:clicks>tag now works correctly with<table:result-list>. -
Click tracking fields. In some conditions, additional fields were incorrectly tracked by the
<track:clicks>tag. They are now tracked correctly.