OpenText™ AppWorks Platform CE 22.

Release Notes

Product Released: 2022-10-14

AppWorks Platform 22.4 Release Notes 1

1 Introduction
These Release Notes provide an overview of AppWorks Platform 22.4, including new features,
delivery information, and supported platforms.

OpenText recommends that you read these Release Notes in conjunction with the documentation
included with the software package. If any conflicts exist, the Release Notes supersede the other
documentation.

We also recommend that you check OpenText My Support for any patches or documentation updates
that may have been posted after the initial release of this product.

1.1 Release Notes revision history

Revision date Sections revised Description of revisions

2022-10-14 First release. All new content.

2 About AppWorks Platform 22.4

This section provides an overview of AppWorks Platform 22.4.

AppWorks Platform enables users to design, build, test, deploy, and monitor business applications.
AppWorks Platform provides low-code development capabilities that enable users to quickly model
business objects using a compositional approach to application development instead of a traditional
way of programming a functionality.

2.1 New features

AppWorks Platform 22.4 includes the following new features.

2.1.1 Dynamic workflow – GA version

Dynamic workflow is a new feature in AppWorks Platform, which is fully configurable to create and
build dynamic workflows in the runtime. Now, business users can create case workflows during
runtime. Following are the main highlights of the dynamic runtime workflows:

2.1.1.1 Create multiple workflows

Users can create multiple workflows for each entity and entity instance. If a user is associated with a
different workflow instance, in the dynamic workflow summary page, the user can switch between the
different workflows without moving away from the page. The progress and summary of the selected
workflow can be seen on the page.

2.1.1.2 Create static workflow templates

Users can create static workflow templates, which have all tasks as static and they cannot be edited
or removed. Users can perform task actions on released tasks.

AppWorks Platform 22.4 Release Notes 2

2.1.1.3 Initiate or create a new dynamic workflow

Users can do the following:

• Select the dynamic workflow template; update or modify steps and tasks; and then start the
workflow.
• Create a new workflow and then start it.
• Save the new workflow as a template to use it multiple times.

2.1.1.4 Add steps and tasks to the dynamic workflow

In a template or released workflow, users can add steps and tasks to the workflow.

2.1.1.5 Categorize tasks with task types

Users can create task types using the Task type building block in design time, which is added by
default to the task list by adding the Dynamic workflow building block.

2.1.1.6 Add additional attributes to runtime tasks using task configurations

For the available task types, map the different layouts so that in runtime, based on the task type,
additional properties are shown with fixed properties.

2.1.1.7 Add task actions based on task types using task configurations

For the available task types, map the different actions, such as autocomplete, approve, and complete
so that in runtime, based on the task type, additional actions are available.

2.1.1.8 Dynamically change the workflow route by adding steps and tasks in a running case
workflow instance

In a running workflow, add and remove steps and tasks. Only inactive steps and tasks can be
removed.

2.1.1.9 Track progress

Track progress of the dynamic workflow and tasks by adding the dynamic workflow progress bar to
the layout.

2.1.1.10 Automate task routing

Automate task routing with conditional attributes, such as autocomplete, on complete, and on
approval.

2.1.1.11 Use TypedRest APIs

TypedRest APIs were introduced for the dynamic workflow and task actions.

2.1.1.12 Use new task actions

Following are the new task actions that were introduced:

• Approve

AppWorks Platform 22.4 Release Notes 3

 • Reject: With this action, users have various options, such as Assign to Case Initiator
(Workflow Initiator) or Specific User. The ‘Assign to’ selection is optional; if not selected, the
task is rejected but will not be assigned to any user.
• Acknowledge: This action is introduced for an autocomplete task. When a task is
autocompleted, it is released with the completed status. The task, which is released as
autocompleted does not have any task actions. Only one new action is provided, which is
Acknowledge. With this action, users can provide confirmation of having seen the task details,
specifically, this addresses the business requirement of having "information tasks" where
users need to read the information and do not have to perform any business operation.
• Inquire: With this action, users can create inquiries against a task and make multiple inquiries.

2.1.2 Low-code EIS connector – GA version

The AppWorks Platform EIS Connector now comes with enhanced features to import external
business objects by configuring an external system URL. With the low-code EIS connector, low-code
developers can connect to the external systems, import their business objects as entities, and use
them to build their applications just like a native entity created in AppWorks Platform. It is like a
generic connector, capable of importing from any RESTful service described in a supported
specification language. The builder can select what operations to import and fine-tune the mapping to
entities.

Low-code developers can now import the data objects from external systems by using the low code
EIS connectors in three different ways using:

• Custom EIS connectors

• Predefined EIS connectors
• Low-code EIS connectors

Users can create a new EIS connector with additional configurations as follows:

1. Provide the specification type as OpenAPI while creating an EIS connector.

2. Generate an API using the provided list of the required JARs and save.
3. Create and configure EIS Repository by providing the URL with the domain and port number.
4. Create an EIS repository reference and import entities. Perform the following steps.

a. Load entities.
b. Retrieve objects from the entities.
c. Set up primary key values.
d. Set up the GET, PUT, and POST operations.
e. Select and set up methods from the available methods.
f. Synchronize the data objects.

A ready entity is created with the identity and imported properties. All the default building
blocks are added to the entity.

The following building blocks are supported by the low-code EIS connector:

• Activity Flow
• History
• Email

AppWorks Platform 22.4 Release Notes 4

 • Email template
• Security
• Relationship
• Title
• Rule

2.1.3 Open documents and emails on a new tab

Users can open documents from the Content panel and emails on a new browser tab by pressing the
Ctrl key when clicking the document or email.

2.1.4 GIT supported as a Source Control Management option

In AppWorks Platform 22.3, GIT was introduced as one of the source control management options,
but as a preview feature. This feature is now made general available in the AppWorks Platform 22.4
release. Application developers can use GIT as one of the source control management options for
application development as a team. They can configure GIT for team development during the creation
of a new workspace and start working as a team and continue their application development.

2.1.5 Email connector to use OAuth authentication for the classic mail
protocols
In previous releases, the email connector used basic username password authentication to send and
poll emails. With this release, the email connector uses the OAuth mode of authentication to send and
poll emails. The OAuth mode uses user based authorization where the application users who want to
send emails need to authorize an email provider to send emails on their behalf. This can be done
from the user profile. Administrators can generate a refresh token and configure in the poller to
automatically poll the emails.

2.1.6 Configuration for Email Connector to move processed emails to a

separate folder
Currently, all processed mails are deleted automatically, which might cause some data loss in case of
unexpected failures. The email connector now provides a configuration for the administrator who
wants to persist the processed emails. They can configure a target folder, which will be used to move
the processed emails into the respective folder. This feature enables application administrators to
verify the details in case of any events of failure. The target folder must exist and can be configured in
the YAML configuration file.

Note: The POP3 protocol does not support accessing other folders. Therefore, the target folder
setting is not applicable in its configuration.

2.1.7 Hide layout panels using rules

Layout panels can be shown or hidden based on the current context by linking the panels to rule
categories and designing rules to associate the categories.

2.1.8 Reorder Home page Layouts that appear in the hamburger menu
Application users can now reorder the home page layouts or the tabbed Home pages that appear in
the hamburger menu according to their usage and the updated preferences are stored and respected
for the user's next sign in session.

AppWorks Platform 22.4 Release Notes 5

2.1.9 Configure the discussion panel to show actual dates instead of
elapsed time
In previous releases, the discussion panel showed the date of the discussion creation as the time
elapsed. Now, a developer can configure to show the actual dates in the discussion panel
configurations.

2.1.10 Results list enhancements

Following are the enhancements for the results list:

2.1.10.1 Open items of results list in a new window

Now, items from the results list can be opened in a new window using CTRL click to enable users to
work on multiple items.

2.1.10.2 Persist results list scroll position when navigating between items

Application users can configure to persist the results list scroll position when navigating between
items and avoid scrolling again back to the previous position to open the next item. This setting can
be enabled in user preferences and disabled by default.

2.1.10.3 Open a linked related item directly from the results list

Now, a developer can configure a list to open the related item directly in runtime and the configured
layout in the design time will be used when opening the item.

2.1.11 Client error messaging enhancements

Error messages can now be clicked to locate the invalid property within the form or on any other tab
for users to complete the form more efficiently. Previously, the users needed to scroll through the form
or tabs to find the missing information or incorrect data. Now, they can simply click the error message
to locate the problem and fix.

2.1.12 Improved business history panel

The history panel is enhanced to support filtering of audit data to find the relevant information more
easily. Users can enter the keywords to filter the audit records automatically. If the history panel is
configured to show a cumulative audit, users can also filter the current item audit records more easily
using a quick filter. Now the business history panel also shows the task comments separately to easily
understand the progress made on the task.

2.1.13 Configurable user interfaces for creating items for a ToOne

relationship in a form
Application developers can now configure the user interface used in the ToOne relationship Create
option. They can configure any form or layout present in the entity and use it as a user interface in
the Create operation. Multiple Create user interfaces can also be configured to provide options, such
as 'Quick create' and 'Create with details' as a menu in the client, using a combination of forms and
layouts present in the entity. Labels provided for the form and layout will be used in the Create menu.

Note: In the runtime Create dialog box, there is support of forms configured to create but not layouts.

AppWorks Platform 22.4 Release Notes 6

2.1.14 Build and deploy application image in Kubernetes using the init
container
Applications or solutions developed using AppWorks Platform can be built as a separate init
container. Administrators can build application images and configurations related to the application as
a separate image independent of the AppWorks Platform image. Administrators can deploy the
AppWorks Platform image in any Kubernetes environment, which will also deploy all configured init
containers, which in turn will deploy the applications or solutions. Since the application image contains
only application specific packages and configurations, the init container size will be small compared to
the AppWorks Platform image.

Building an application image by extending the AppWorks Platform image continues to be supported.

2.1.15 Deploy AppWorks Platform in case insensitive mode for Oracle

AppWorks Platform can be deployed to an Oracle database configured with case insensitive collation,
for example, BINARY_CI. In this scenario, all functionalities of AppWorks Platform, such as filtering,
searching, and sorting will follow case insensitive behavior.

2.1.16 Support for renaming documents in Content Server

Users can now rename a document stored in Content Server from AppWorks Platform. The Content
or File building block provides a new action, Rename document, which allows users to change the
name of the document both in AppWorks Platform and Content Server. The Content Panel now shows
the new action, Rename document instead of the existing Rename action when AppWorks Platform is
configured with Content Server, and it changes the display name and actual name of the document.

2.1.17 Java 17 support

AppWorks Platform added support for Java 17 and continues to support Java 11.

2.2 Discontinued and deprecated features

There are no discontinued or deprecated features in this release.

For a comprehensive list of discontinued and deprecated features in AppWorks Platform from
previous releases, see AppWorks Platform Known Issues, Deprecated Features, Discontinued
Features, and Product Incompatibilities on My Support.

3 Downloads
Downloads for AppWorks Platform are available on My Support.

3.1 Packaging and delivery information

The software for AppWorks Platform is available for Windows and Linux environments.

AppWorks Platform 22.4 Release Notes 7

 Caution
Since rollback is not possible during the AppWorks Platform upgrade, OpenText
recommends taking a backup of your data. Follow the instructions provided at:
http://support.opentext.com/csm?id=kb_article_view&sysparm_article=KB0719197.

To begin installing AppWorks Platform, extract the contents of OpenText AppWorks Platform 22.4.zip
to your computer. You can use the OpenText CARS 2.7 Installation and Administration Guide and
OpenText AppWorks Platform 22.4 Installation Guide for Windows or OpenText AppWorks Platform
22.4 Installation Guide for Linux to install or upgrade to AppWorks Platform 22.4.

The OpenText AppWorks Platform 22.4.zip file includes the following executables, files, or folders:

• OpenText_CARS_2.7.exe/.bin: Executable file to install or migrate to OpenText CARS 2.7.

You must install OpenText CARS before installing AppWorks Platform 22.4.
• OpenText_AppWorks_Platform _22.4.exe/.bin: Executable file to install or migrate to
AppWorks Platform 22.4.
• Captemplates: Templates for application package installation.
• Certificates: Public keys (.CER files) of certificates for signing the applications available with
AppWorks Platform 22.4. Add to this folder the certificates of the custom applications to load
in AppWorks Platform 22.4. For details, see OpenText AppWorks Platform 22.4 Installation
Guide for Windows or OpenText AppWorks Platform 22.4 Installation Guide for Linux.
• packagesigner: JAR files and a batch file to sign custom applications before loading them in
AppWorks Platform 22.4.
• packages: Application packages in the .CAP format.
• cap-silent-install.properties: Input file for AppWorks Platform application package installation.
• cars.installer.properties: Input file for OpenText CARS command-line installer.
• cars.upgrade.properties: Input file for OpenText CARS command-line upgrade.
• cordys.installer.properties: Input file for AppWorks Platform 22.4 command-line baseline
installer.
• cordys.uninstaller.properties: Input file for AppWorks Platform 22.4 command-line baseline
uninstaller.
• cordys.upgrade.properties: Input file for AppWorks Platform 22.4 command-line baseline
upgrade.
• multipledso.xml: Input file for providing database details to create the database configuration.
• Third party licenses.txt: Copyright notices and licensing conditions of all the third party
software used in AppWorks Platform 22.4.
• Third party licenses CARS.txt: Copyright notices and licensing conditions of all the third party
software used in OpenText CARS 2.7.
• Copyright.txt: Copyright information of AppWorks Platform.

4 Documentation
Documentation for AppWorks Platform is available on My Support.

AppWorks Platform 22.4 Release Notes 8

4.1 Packaging and delivery information
The documentation for AppWorks Platform includes:

• OpenText CARS 2.7 Installation and Administration Guide

• OpenText AppWorks Platform 22.4 Installation Guide for Windows
• OpenText AppWorks Platform 22.4 Installation Guide for Linux
• OpenText AppWorks Platform 22.4 Low-Code Design Guide
• OpenText AppWorks Platform 22.4 Advanced Development Guide
• OpenText AppWorks Platform 22.4 Administration Guide
• OpenText AppWorks Platform 22.4 Upgrade Guide
• OpenText AppWorks Platform 22.4 Troubleshooting Guide
• OpenText AppWorks Platform 22.4 High Availability Deployment Guide
• OpenText AppWorks Platform 22.4 Performance and Tuning Guide
• OpenText AppWorks Platform 22.4 API Reference Guide
• OpenText AppWorks Platform 22.4 Cloud Deployment Guide
• OpenText AppWorks Platform 22.4 Entity REST API Developer Guide

4.2 Related videos

For additional video content, see the AppWorks Platform Videos page on My Support.

5 Supported environments and compatibility

This section provides details about supported platforms, systems, and versions.

5.1 Supported systems

In AppWorks Platform 22.4, support has been added for the following:

• Java 17
• Content Server 22.3
• OpenText Directory Services 22.3
• Magellan BI & Reporting 22.3
• OpenText Intelligent Viewing 22.3

For details on supported platforms, see OpenText AppWorks Platform Supported Environments on My
Support.

5.2 OpenText product compatibility

This section provides details about which versions of other OpenText products are compatible with
this release of AppWorks Platform 22.4.

Note
For the latest compatibility information for AppWorks Platform, see OpenText
AppWorks Platform Supported Environments on My Support.

AppWorks Platform 22.4 Release Notes 9

 Product name Version Notes

Archive Center 16, 16.2

20.2
21.2

Brava Enterprise 16 EP7 Update 6

Content Server 16, 16.2

20.2, 20.3, 20.4
21.1, 21.2, 21.3, 21.4
22.1, 22.2, 22.3

Documentum 7.2, 7.3

16.4, 16.7
20.2, 20.3, 20.4
21.1, 21.2, 21.3, 21.4
22.1, 22.2

AppEnhancer 20.3, 20.4, 22.2 Previously known as

ApplicationXtender (AX)

OpenText Directory Services 16.4 (minimal

version), 16.6
20.1, 20.2, 20.3, 20.4
21.1, 21.2, 21.3, 21.4
22.1, 22.2, 22.3

Magellan BI & Reporting 21.4.1, 22.3 Previously known as

Information Hub (iHub)

AppWorks Gateway 21.1, 21.3, 22.1, 22.3

OpenText Intelligent Viewing (IV) 21.1, 21.2, 21.3

22.1, 22.2, 22.3

5.2.1 OpenText Brava! Support

Apply the Brava license file (IGCKey.lic file) bundled with AppWorks Platform in the supported version
of OpenText Brava! Enterprise server. Follow the instructions provided at:
http://support.opentext.com/csm?id=kb_article_view&sysparm_article=KB0593832.

5.3 Language support

AppWorks Platform is currently localized in the following languages. Additional languages may be
available in future releases.

UI = user interface only

B = both user interface and online help

AppWorks Platform 22.4 Release Notes 10

 Component EN SV DE JA FR NL ZH ES AR CS KO PT CA IT
AppWorks B UI UI UI UI UI UI UI UI* UI* UI* UI* UI* UI*
Platform

6 Fixed issues
This section provides information about past issues that have been fixed in this release.

Issue name Issue description

BOP-120980 Some email providers, such as Gmail and Microsoft Office 365 have stopped
supporting basic authentication. With this fix, the email connector has been
enhanced to support OAuth authentication and therefore, not impact
customers.

BOP-126190 AppWorks Platform now supports GIT as one of the source control
management options for application development as a team. With this, you
can configure GIT for team development during the creation of new workspace
and start working as a team and continue your application development.

BOP-136172 A fix has been made to display the timeout value provided as part of the HTTP
connector container configuration. Otherwise, the default value is displayed.

BOP-143026 On click of a global error on a tab that is not active, focusing on the error field
was not possible previously. Now, users can navigate to the respective error
tab even when the tab is inactive.

BOP-149149 Fixed an issue that occurs when security is set on service groups.

BOP-151288 When a page of results in a list requires scrolling to find a result, the scroll
position must be persisted so that when a user opens an entity and goes back
using the breadcrumb, the same scroll position in the list remains.
The user must be able to choose themselves if they want this behavior with a
setting in their user profile.

BOP-151506 In the AppWorks Client, using Ctrl + click on a document opens the document
on a new tab.

BOP-152210 Emails are sent to the recipient properly. If there is any issue while sending
emails, a corresponding error is logged.

BOP-152264 The Email connector is now enhanced with the feature of moving the
processed emails to a configurable folder.

BOP-153275 Previously, the items per page button in the pagination container was too
small to fit text from all languages. Now, the button size has been increased to
fit text of all languages.

BOP-153953 Previously, the category could not be saved from the form editor when
language packs, such ja-JP, zn-CH, or ko-KR were used. Now, categories can
be saved from the form editor irrespective of the language selected by the
user.

AppWorks Platform 22.4 Release Notes 11

 BOP-154099 Previously, context ID and panel ID were not checked while creating a
personalization item. Now, these values are checked, which omits creation of
personalization IDs with incorrect values.

BOP-154249 The client used to throw a script error when multiple relations were consumed
in an expression. Now, the client does not throw errors and evaluates the
expressions.

BOP-154819 Previously, all the tabs on the navigation bar were visible when a nested layout
was used in a Home page layout. Now, only active tabs are shown. On click of
active tabs, the panel containing the tab in the layout opens.

BOP-155173 Previously, in AppWorks Platform 21.4, child relationship grids did not show
errors for required fields for ToOne relationships until the row or controls had
focus. Now, if a user adds ToOne relationships with the required fields in
design time, an error is displayed in runtime when creating a new item in a grid
and repeating group container.

BOP-155581 While trying to view documents in Brava in an upgraded AppWorks Platform

instance, users were facing a NullPointerException that is resolved with this
change.

BOP-155596 The UDDI connector with SAML/basic authentication is broken with the
AppWorks Platform 21.4 HttpUrlConnection migration. The issue has been
fixed now.

BOP-155690 The HTTP connector could not convert the JSON properly if the enable-
schema-validation tag was set to true and the schema complex type was
'Mixed'.

BOP-155771 The Password field is now masked.

BOP-156419 Previously the 'hour' string in the date time property was not being translated
into the Japanese language. With this fix, added the translation string for 'hour'
in the Japanese language.

BOP-156464 Mobile apps created in AppWorks Platform 21.3 had an issue, causing mobile
aps to not load on an iOS device. The issue is now resolved and now, mobile
apps can be seen on an iOS device.

BOP-156902 Incoming emails, which contain images without disposition information will be
processed.

AppWorks Platform 22.4 Release Notes 12

7 Known issues
The following known issues exist in this release.

Issue name Issue description

Issue with linked The Rename document action works only with normal documents in the
documents Content building block. There are some issues for linked documents.
Workaround: None

Issue with In AppWorks Administration, while configuring content for Documentum, when
making a field the property for any document type is made as read only and then later
read only in cleared, it continues to appear as read only in the document properties in the
Documentum runtime (AppWorks Client) though the field can be updated.
Workaround: Restart the Document Store service container to clear the cache
and enable the field to appear as editable.

AppWorks Platform 22.4 Release Notes 13

8 Contact information
OpenText Corporation
275 Frank Tompa Drive
Waterloo, Ontario
Canada, N2L 0A1

For more information, visit the OpenText or My Support websites.

Copyright © 2022 Open Text. All Rights Reserved.

Trademarks owned by Open Text. One or more patents may cover this product. For more information, please visit OpenText Patents Information.
Disclaimer
No Warranties and Limitation of Liability
Every effort has been made to ensure the accuracy of the features and techniques presented in this publication. However, Open Text Corporation and its affiliates accept
no responsibility and offer no warranty whether expressed or implied, for the accuracy of this publication.

14