Posted May 06 by Alex Jewell.
Updated Jan 06 by Werner De Jong.

The latest patch release for AppWorks Gateway has been published and fixes a number of outstanding issues from 1.1.5.

6807 views. 0 comments.


AppWorks 1.1.6 fixes the following issues:

Incompatibility with OTDS 10.5 patch 2 - It was discovered that OpenText Directory Services (used by AppWorks for identity management) had modified an API used during the initial AppWorks set up. The bug resulted in AppWorks failing to set up properly if connected to an OTDS instance with patch 2 applied. As of AppWorks 1.1.6, this is no longer a problem and set up will be successful on any OTDS 10.5 system.

Apps can open URLs in secure container - Previously, apps had no way to open URLs in the AppWorks controlled container. URLs can now be added to a whitelist by the app developer allowing these URLs to be opened in the current view.

Minor improvements to Web Access

  1. Tab names can be customized.
  2. Tabs can be ordered.
  3. Installation of an app can automatically configure the tab.
  4. Sublinks using hash tags now resolve properly.

Apps can be launched while a user is offline - By including the flag “isAvailableOffline=true” in an app's file, an app which has previously been opened by the user will be available the next time the user goes offline. This mechanism simply allows the app to launch and it is up to the app developer to ensure that it functions properly with no server access.

Android client profile names must be unique - There is now a check to ensure that profile names on Android are unique to prevent confusion.

Components can register for specific mimetypes to handle when opened from Content Server file browse - For components handling documents, that are opened from the Content Server file browse, an optional parameter in the file will allow them to handle documents of a particular mimetype. E.g. if “view=144” and “mimeTypes=text/html,text/plain” is specified, only html and plain text documents will use the component.

Apps can now be opened from notifications - Formerly, only components could be opened by tapping notifications in the mobile clients. Now, apps follow the same pattern and can include the same keys to handle a notification. See the Notification Tutorial for details.

User can stay logged in on an AppWorks client - The Remember Me functionality which was not correctly maintaining the user's session has been fixed. The mechanism now includes a toggle on the AppWorks Gateway admin settings so that an administrator can disable this functionality and force users to enter their credentials when their session times out. If users choose to have the client remember their password, they will have to manually log out of the client to end their session.

Audience selection caching - Audience selection caching has been fixed and will no longer cause all apps access to become accidently restricted.

Notification times - Notification timestamps are now updated when new notifications arrive.

App updating - Apps updated, enabled/disabled, or which have an audience change on the server will now update live in all scenarios.

Profile switching wait time - The time taken to switch between profiles has been decreased and a loading indicator has been added.

Notification channel reestablished - The notification channel was failing to reinitialize on session timeout. Now if the user has enabled session keep-alive, the channel will be reestablished. Otherwise, they will be asked to reenter their password.

Reporting service resource consumption - The resource consumption of the reporting service has been improved, allowing other system functions to continue while it parses log data.

Audience error on upgrade - Audiencing for apps now defaults to “Available on all runtimes” upon upgrading AppWorks if no setting existed previously.

Poor notification performance - An incorrect index on the notification table was hurting performance on user notification lookups.

Update procedure

To upgrade the OpenText AppWorks Gateway from v1.1.5 to v1.1.6

  1. Download the AppWorks Gateway core installation package
  2. Stop the Apache Tomcat service.
  3. Navigate to the TOMCAT_HOME/webapps folder and delete the existing gateway.war file and gateway folder.
  4. Extract the contents of the file into the root of the Apache Tomcat folder. For example, C:\Program Files\Apache Software Foundation\Tomcat 7.0.
  5. Start the Apache Tomcat service.
  6. In a browser, type http://Tomcat_Host:port/gateway to finish installation (instruction).

Known issues

Unable to click on help link for Tempo Social - When the Tempo Social browser app is installed in the browser app launcher (Web Access) the help link does not work. Help links work for apps with help hosted in AppWorks but not when help is hosted on another domain.

Unable to edit browser link URLs after app install - When installing a browser based app which uses the app launcher bar in the header, the app configures a URL to be used for its tab in the header. For AppWorks apps this URL is to the app hosted locally on AppWorks. When using this mechanism to display proxied UIs in the browser, the URL is set by installing a proxied app and its URL can only be modified by updating in the app bundle and reinstalling the app through the UI.

Table of Contents

Your comment

To leave a comment, please sign in.