Release notes for Red Hat Process Automation Manager 7.4

Red Hat Process Automation Manager 7.4

Red Hat Customer Content Services

Abstract

This document contains release notes for Red Hat Process Automation Manager 7.4.

Preface

These release notes list new features, features in technology preview, known issues, and issues fixed in Red Hat Process Automation Manager 7.4.

Chapter 1. Product overview

Red Hat Process Automation Manager is an open-source business automation platform that combines business process management (BPM), case management, business rules management, and resource planning. It enables business and IT users to create, manage, validate, and deploy business processes, cases, and business rules.

Red Hat Process Automation Manager uses a centralized repository where all resources are stored. This ensures consistency, transparency, and the ability to audit across the business. Business users can modify business logic and business processes without requiring assistance from IT personnel.

Red Hat Process Automation Manager 7.4 provides increased stability, several fixed issues, and new features.

Red Hat Process Automation Manager is fully supported on Red Hat OpenShift Container Platform and can be installed on various platforms.

Note

Red Hat Process Automation Manager requires Java 8 or later.

For information about the support policy for Red Hat Process Automation Manager, see the Release maintenance plan for Red Hat Decision Manager 7.x and Red Hat Process Automation Manager 7.x.

Chapter 2. New features

This section highlights new features in Red Hat Process Automation Manager 7.4.

2.1. Installation

2.1.1. Manifest of dependencies for an unconnected deployment

Red Hat Process Automation Manager now includes a manifest file with all of the Maven artifact dependencies required for operation, including development of services in Business Central. You can download the artifacts and provide them in a mirror repository in order to use Red Hat Process Automation Manager without an outgoing connection to the public Internet.

2.2. Business Central

2.2.1. Git branch cloning

Business Central now supports cloning specific branches from remote repositories.

2.2.2. Role-based access control

Business Central now supports role-based access control for branches. Users can restrict access for a target branch to a specified collaborator. For example, if a user has security permission to update a project and has write permission for that branch based on the specified contributor type, the user can create new assets.

2.2.3. Test Scenarios

You can complete the following tasks in the test scenarios designer:

  • Run a single test scenario. You can now run a single test scenario in the test scenarios table.
  • Run all test scenarios at the project level. In the project view, you can now concurrently run all of the available test scenarios defined inside a single project.
  • View coverage reports for DMN models. The test scenarios designer displays the test coverage statistics in the Coverage Report panel on the right side of the test scenarios designer.
  • Export and import test scenario spreadsheet data. You can now export and import test scenario spreadsheet data in CSV format.
  • View failed test results. If a test fails, the test scenarios designer now displays a pop-up window with a detailed error message and actual values of the test results.
  • Test a ruleflow group. You can set a specific ruleflow group or agenda group in the Settings panel on the right side of the designer.

2.2.4. Process designer

The following list provides a summary of process designer updates:

  • Business Central provides more detailed error messages, highlights errors in diagrams, and lists all validation errors that a user needs to know about in order to fix issues in the process model.
  • The new process designer in Business Central supports text wrapping inside of nodes. If you resize a node, the text automatically resizes and wraps inside the node.
  • You can now choose an execution mode in multi-instance human tasks and subprocesses and sequential and parallel execution of the instances.

  • There is added support for the following new advanced user task properties:

    • Notifications:

      • Type = Not Started, Not Completed
      • Expires At
      • From
      • To Users
      • To Groups
      • Reply To
      • Subject
      • Body

    • Reassignments:

      • Users
      • Groups
      • Expires At
      • Type = Not Started, Not Completed
  • You can now track a Service Level Agreement (SLA) based on the due date that is set either for the entire process instance or selected activities.
  • You can now import processes with childLaneSets, which are transformed to regular swim lanes during the import process.
  • You can now import processes with a collapsed subprocess. This ability enables users to import large process diagrams that contain collapsed subprocesses.
  • Zoom and panning capabilities in the new process designer are improved, including zooming (Ctrl) and panning (Alt) keyboard shortcuts.
Note

The legacy process designer in Business Central is deprecated with Red Hat Process Automation Manager 7.4.0. It will be removed in a future Red Hat Process Automation Manager release. The legacy process designer will not receive any new enhancements or features. If you intend to use the new process designer, start migrating your processes to the new designer. Create all new processes in the new process designer. For information about migrating to the new designer, see see Managing projects in Business Central.

2.2.5. Default filter selection

You can use the Saved Filter option on the following pages to set a task filter as the default filter:

  • Process Instances
  • Execution Errors
  • Jobs
  • Tasks
  • Task Inbox

The default filter is then applied each time you open the page.

2.2.6. Prometheus metrics monitoring in Red Hat Process Automation Manager

Process Server now supports Prometheus metrics monitoring for your business assets in Red Hat Process Automation Manager. Prometheus is an open-source systems monitoring toolkit that you can use with Red Hat Process Automation Manager to collect and store metrics related to the execution of business rules, processes, solvers, Decision Model and Notation (DMN) models, and other assets in Red Hat Process Automation Manager. You can access the stored metrics through a REST API call to the Process Server, through the Prometheus expression browser, or using a data-graphing tool such as Grafana.

You can configure Prometheus metrics monitoring for an on-premise Process Server instance, for Process Server on Spring Boot, or for a Process Server deployment on Red Hat OpenShift Container Platform.

For information about enabling and using Prometheus metrics monitoring with Red Hat Process Automation Manager, see Managing and monitoring Process Server.

2.2.7. DMN included models

The Decision Model and Notation (DMN) designer contains a new Included Models tab that you can use to include other DMN models from your project in a specified DMN file. When you include a DMN model within another DMN file, you can reuse the DRD nodes and logic of the included model in that DMN file. This enhancement helps you more efficiently integrate DMN logic between different DMN models in your project.

For more information about DMN support in Red Hat Process Automation Manager 7.4, see the following resources:

2.3. Red Hat OpenShift Container Platform

2.3.1. JMS capabilities for Process Server

JMS capabilities for Process Server are now available. With JMS capabilities you can interact with the server through the JMS API using an external AMQ message broker.

2.3.2. Business Central extensions for OpenShift and OpenShift Startup Strategy for Process Server

All deployments of Red Hat Process Automation Manager on Red Hat OpenShift Container Platform, except the fixed managed template (rhpam74-prod.yaml), now use OpenShift Startup Strategy for all Process Servers by default (the KIE_SERVER_STARTUP_STRATEGY environment variable) and also have the Business Central extension for OpenShift enabled (the KIE_WORKBENCH_CONTROLLER_OPENSHIFT_ENABLED environment variable). These features enable Business Central and Business Central Monitoring to discover all Process Servers in the same name space automatically. They eliminate the need to configure a controller.

2.3.3. Full support for Red Hat OpenShift Container Platform 4.x in OpenShift Operator

The OpenShift Operator supplied with Red Hat Process Automation Manager 7.4 fully supports OpenShift 4.x.

2.3.4. Red Hat OpenShift Container Platform images use Red Hat Entreprise Linux 8 and OpenJDK 11

Red Hat Process Automation Manager container images for Red Hat OpenShift Container Platform now use a Red Hat Enterprise Linux 8 base layer and OpenJDK 11.

2.4. Red Hat Business Optimizer

2.4.1. Enhancement to Java API

The Red Hat Business Optimizer Java API supports a more fluent form because of new with* methods: 

solverFactory.getSolverConfig().withTerminationConfig(
new TerminationConfig().withMinutesSpentLimit(userInput));

2.4.2. Contracts supported in Employee Rostering application

In the Employee Rostering starter application for Red Hat Business Optimizer, you can set the work time limitations stipulated by employee contracts to a day, a week, a month, and a year.

Chapter 3. Support and compatibility

This section lists supported version updates. For a complete list of supported configurations, see Red Hat Process Automation Manager 7 Supported Configurations.

3.1. Updated supported component versions

The following component versions have been updated in this release:

  • Red Hat JBoss Web Server 5.1.0
  • Apache Tomcat 9.0
  • Red Hat Single Sign-On 7.3

3.2. Deprecated components

The components listed in this section have been deprecated in this release or in a recent release.

3.2.1. Supported languages

Starting with the 7.5 release, the Red Hat Process Automation Manager user interface will be localized in English and Japanese only. Support for other languages that exist in the product will be deprecated.

3.2.2. Legacy process designer

The legacy process designer in Business Central is deprecated in Red Hat Process Automation Manager 7.4.0. It will be removed in a future Red Hat Process Automation Manager release. The legacy process designer will not receive any new enhancements or features. If you intend to use the new process designer, start migrating your processes to the new designer. Create all new processes in the new process designer. For information about migrating to the new designer, see Managing projects in Business Central.

3.2.3. Legacy Test Scenarios tool

The legacy Test Scenarios tool was deprecated with Red Hat Process Automation Manager 7.3.0. It will be removed in a future Red Hat Process Automation Manager release. Use the new Test Scenarios designer instead.

3.2.4. Google Charts

In Red Hat Process Automation Manager 7.3.0, the C3 chart library replaced the Google Charts library as the default chart library in Business Central. With Red Hat Process Automation Manager 7.4.0, Google Charts is no longer available in Business Central.

Chapter 4. Technology preview

This section lists features that are in Technology Preview in Red Hat Process Automation Manager 7.4. Business Central includes an experimental features administration page that is disabled by default. To enable this page, set the value of the appformer.experimental.features property to true.

Important

These features are for Technology Preview only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs), might not be functionally complete, and Red Hat does not recommend to use them for production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.

For more information on Red Hat Technology Preview features, see Technology Preview Features Scope.

4.1. High-availability authoring on Red Hat JBoss EAP (on premise and with Red Hat OpenShift Container Platform)

Configuration of Business Central for high availability is currently Technology Preview. Search and messaging technology used to enable search feature is considered an implementation detail. That technology may be replaced in Red Hat Process Automation Manager in the future while the capability offered may be preserved.

4.2. Case modeler

Case modeler in Business Central now includes the new process designer. It provides the option to model a case as a sequence of stages so it is simple to define a case model at high-level. Case modeling supports three types of tasks: human tasks, sub-processes, and sub-cases.

Note

The case modeler in Red Hat Process Automation Manager 7.4 is a Technology Preview feature and is disabled by default in Business Central. To enable the case modeler preview in Business Central, in the upper-right corner of the window click Settings → Roles, select a role from the left panel, click Editors → (New) Case Modeler → Read, and then click Save to save the changes.

4.3. Process instance migration as a standalone service

Process instance migration is now available as a standalone service containing a user interface and a back end, and packaged as a Thorntail uber JAR. The process instance migration service enables a user to define the migration between two different process definitions, known as a migration plan. The user can apply the migration plan to the running process instances in a specific Process Server.

For more information about the process instance migration standalone service, see Process Instance Migration Service page in GitHub.

4.4. OpenShift operator installer wizard

An installer wizard is provided in the OpenShift Operator for Red Hat Process Automation Manager. You can use the wizard to deploy a Red Hat Process Automation Manager environment on Red Hat OpenShift Container Platform with the Operator.

4.5. Red Hat JBoss Data Grid replaces Elasticsearch

Red Hat JBoss Data Grid replaces Elasticsearch as the distributed highly scaleable full-text search and analytics engine for Red Hat Process Automation Manager 7.4.0.

Red Hat Data Grid is built from the Infinispan open-source software project and contains indexing capabilities that enable you to store, search, and analyze high volumes of data quickly and in near-real time. In a Red Hat Process Automation Manager clustered environment, it enables you to perform complex and efficient searches across cluster nodes.

Chapter 5. Known issues

This section lists known issues with Red Hat Process Automation Manager 7.4.

5.1. Business Central

Guided rules expose parentheses outside of an expression [RHDM-1046]

Issue: When you create a guided rule, if you select the field for multiple values and each value is enclosed in parenthesis, for example (red), (blue), an invalid rule is generated.

Steps to reproduce:

  1. Open Business Central.
  2. Open any project.
  3. Create the data object Car with the field color:String.
  4. Create a new guided decision table.

  5. Define a new Condition column:

    Pattern: $c : Car

    Calculation Type: Literal value

    Field: color

    Operator: is contained in the (comma separated) list

    Header: Car color is

  6. Select the Model tab and enter (red), (blue) in the corresponding cell.

Expected result: The $c : Car(color in ("(red)", "(blue)")) rule is generated.

Actual result: The $c : Car( color in ("red)", "(blue") ) rule is generated.

Workaround: In the Model tab, enter the values as shown in the following example: 

((red), (blue))

A guided scorecard cannot be tested with the Test Scenario (Legacy) asset [RHPAM-2307]

Issue: If a guided scorecard name begins with a lowercase letter, you cannot test the scorecard with the Test Scenario (Legacy) asset.

Steps to reproduce:

  1. Create a guided scorecard with a name that begins with a lowercase letter.
  2. Import the guided scorecard into Business Central.
  3. Click Test.

Expected result: The test completes successfully.

Actual result: The test fails.

Workaround: Make sure that guided scorecard names do not begin with lowercase letters.

You cannot add a new group in Business Central integrated with RH-SSO [RHPAM-2036]

Issue: The following exception occurs when you try to add a new group in Business Central if Business Central is integrated with RH-SSO 7.3.0: 

java.lang.NoSuchMethodError:org.keycloak.representations.idm.RoleRepresentation.setScopeParamRequired(Ljava/lang/Boolean;)

Steps to reproduce:

  1. Open Business Central.
  2. Open the Admin page.
  3. Open Groups.
  4. Try to create a new group.

Expected result: The new group is created.

Actual result: A dialog box with the listed exception appears.

Workaround: Add the group in RH-SSO instead of adding it in Business Central.

When you create an asset, the package drop-down button does not appear immediately [RHPAM-2133]

Issue: When you create an asset, the package drop-down button is invisible and an error about package selection appears.

Steps to reproduce:

  1. Create a project in Business Central.
  2. Try to create a business process.

Expected result: The package drop-down button is visible and you can create the business process.

Actual result: The package drop-down button is initially invisible and it appears after several seconds.

Workaround: Wait until the package drop-down button is visible or reopen the dialog window for asset creation.

5.2. Process designer

Human task comments are not retained when a process instance is finished [RHPAM-2258]

Issue: Human task comments are retained and visible only while the respective process instance is running. When the process instance is completed or aborted, comments from human tasks disappear even though the tasks are still visible in Business Central.

Steps to reproduce:

  1. Start a process instance with two consecutive human tasks.
  2. Comment on the first human task.
  3. Claim, start, and complete the first task.
  4. Check the Comments tab of the human task to confirm that the comments are retained for the completed task.
  5. Abort the process instance or complete the task preventing the instance from finishing.
  6. Navigate to the log file for the first task again.

Expected result: Data about the first task is available in the Comments tab of the human task .

Actual result: The first task is still available in Business Central but no data is available in the log file.

Workaround: None.

Greater than (>) and less than (<) symbols in data types break a process [RHPAM-2193]

Issue: If you place greater than (>) and less than (<) symbols in a data type for a process variable, you cannot reopen the process. The XML editor appears instead.

Steps to reproduce:

  1. Create a process and add the list1:java.util.List<String> process variable.
  2. Save and reopen the process.

Expected result: The process opens.

Actual result: The process does not open.

Workaround: None.

If a case task actor is invalid, the resulting BPMN file is also invalid [RHPAM-2240]

Issue: The new process designer sometimes generates an invalid XML file. A user task with an actor assigned is generated as a a potentialOwner element in the XSD file. 

<bpmn2:potentialOwner id="5058b718-8866-4ccd-b793-d5ebf48de5a2">
<bpmn2:resourceAssignmentExpression id="_gN_feI4_Eem2-an8Fwu06w">
<bpmn2:formalExpression id="_gN_feY4_Eem2-an8Fwu06w">manager</bpmn2:formalExpression>
</bpmn2:resourceAssignmentExpression>
</bpmn2:potentialOwner>

The id of the potentialOwner element is missing an underscore at the beginning, which means that if the first element is a number, this is now an invalid ID.

Tasks that have ioSpecification should always define an inputSet and outputSet, even if those are empty.

Steps to reproduce:

Create a user task with no output mapping. This will generate the following output: 

<bpmn2:ioSpecification id="_rEnOQY5AEem2-an8Fwu06w">
<bpmn2:dataInput id="38B29C0C-6BD8-4275-ACCE-D5D97DEBB2CB_TaskNameInputX" drools:dtype="Object" itemSubjectRef="_38B29C0C-6BD8-4275-ACCE-D5D97DEBB2CB_TaskNameInputXItem" name="TaskName"/>
<bpmn2:dataInput id="38B29C0C-6BD8-4275-ACCE-D5D97DEBB2CB_SkippableInputX" drools:dtype="Object" itemSubjectRef="_38B29C0C-6BD8-4275-ACCE-D5D97DEBB2CB_SkippableInputXItem" name="Skippable"/>
<bpmn2:inputSet id="_rEnOQo5AEem2-an8Fwu06w">
<bpmn2:dataInputRefs>_38B29C0C-6BD8-4275-ACCE-D5D97DEBB2CB_TaskNameInputX</bpmn2:dataInputRefs>
<bpmn2:dataInputRefs>_38B29C0C-6BD8-4275-ACCE-D5D97DEBB2CB_SkippableInputX</bpmn2:dataInputRefs>
</bpmn2:inputSet>
</bpmn2:ioSpecification>

Expected result: The output includes an empty outputSet attribute.

Actual result: The output does not include an outputSet attribute.

Workaround: None.

Nodes and distribution lines do not fully align horizontally [RHPAM-2241]

Issue: It is difficult to precisely align some nodes horizontally.

Steps to reproduce:

  1. Create a process.
  2. Try to align a node and connector horizontally.

Expected result: The node and connector are aligned.

Actual result: The node and connector are not aligned.

Workaround: None.

The multiple instance properties of a multiple instance subprocess are not visible for nodes inside of a multiple instance subprocess [RHPAM-2257]

Issue: If you model a process with a multiple instance subprocess as a multiple instance node, the multiple instance Data Input and multiple instance Data Output variables are not visible for nodes inside of the multiple instance subprocess.

Steps to reproduce:

  1. Create a multiple instance subprocess for execution by selecting the multiple instance collection input/output from an existing process level list and setting new variables for multiple instance data input and output.
  2. Add a user task inside of the multiple instance subprocess.
  3. Try to configure a user task so that is uses multiple instance data input/output.

Expected result: The new variables for multiple instance data input and output are listed in the data I/O editor Source and Target fields and you can use the new variables for multiple instance data input and output.

Actual result: The new variables for multiple instance data input and output are not listed in the data I/O editor Source and Target fields.

Workaround: To use variables for multiple instance data input and output, define them in Process Data → Process Variables before creating the multiple instance subprocess for execution.

Data output associations do not work correctly when they are declared twice [RHPAM-2242]

Issue: If the data output variable associated with a user task is declared twice, it is not stored in the resulting XML file.

Steps to reproduce:

  1. In Business Central, create a user task.
  2. Open the Properties panel.
  3. Expand the Implementation/Execution section.
  4. Click Assignments.
  5. In the Data Outputs and Assignment area, add a data output variable twice by using the same variable name.

Expected result: Two variables with the same name are stored in the BPMN XML file.

Actual result: The variables are not stored in the resulting BPMN XML file (XML) so when the process runs or loads, the data output assignments are missing.

Workaround: None.

5.3. Process engine

Task operations are slow [RHPAM-2259]

Issue: Task operations such as Start, Complete, or Claim are noticeably slower when the Process Server API or UserTaskService is used. This issue appeared when a join was added to the getTaskInstanceById query. The performance of these operations will be restored to the previous state in a future patch release.

5.4. Process Server

Query-related operations return errors when Process Server runs on either Red Hat JBoss Web Server or SpringBoot with DB2 [RHPAM-2292]

Issue: Query-related operations return errors when Process Server runs on either Red Hat JBoss Web Server or SpringBoot with DB2.

Steps to reproduce:

  1. Create a query-definitions.json file that contains content similar to the following example and add it to Process Server on Red Hat JBoss Web Server: 

    [
  {
    "query-name" : "first-query",
    "query-source" : "${org.kie.server.persistence.ds}",
    "query-expression" : "select * from ProcessInstanceLog",
    "query-target" : "PROCESS"

  }
]
  2. Start Process Server. Process Server tries to register the new default query.

Expected result: The default query is successfully registered.

Actual result: An error code is returned, for example: 

com.ibm.db2.jcc.am.XaException: [jcc][t4][10401][12066][4.24.92]
XA exception: XAER_OUTSIDE ERRORCODE=-4228, SQLSTATE=null

Workaround: For Red Hat JBoss Web Server, set defaultAutoCommit=false in the XADataSource. For SpringBoot, set spring.datasource.defaultAutoCommit=false in application properties. This property must be added to the Narayana data source.

5.5. Red Hat OpenShift Container Platform

Validation sub-element is missing for data sources [RHPAM-2226]

Issue: If you create a custom template for deploying Process Server on Red Hat OpenShift Container Platform and the server uses a MySQL or PostgreSQL database, Process Server data sources do not contain the validation sub-element where connection checkers and exception sorters are defined.

Steps to reproduce:

  1. Create a custom template for deploying Process Server on Red Hat OpenShift Container Platform with a MySQL or PostgreSQL database.
  2. View the contents of the template file.

Expected result: The template contains the expected data sources.

Actual result: The template does not contain the expected data sources.

Work around:

Add the following environment variables and values to your templates:

  • For MySQL: 

    name: RHPAM_CONNECTION_CHECKER
value: "org.jboss.jca.adapters.jdbc.extensions.mysql.MySQLValidConnectionChecker"
name: RHPAM_EXCEPTION_SORTER
value: "org.jboss.jca.adapters.jdbc.extensions.mysql.MySQLExceptionSorter"

  • For PostgreSQL: 

    name: RHPAM_CONNECTION_CHECKER
value: "org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLValidConnectionChecker"
name: RHPAM_EXCEPTION_SORTER
value: "org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLExceptionSorter"

5.6. Test scenarios

Test scenarios designer can not access the parent data object fields [RHDM-1014]

Issue: Test scenarios designer cannot access a parent data object field, even if the field has public getter and setter attributes.

Steps to reproduce:

  1. Create a scenario with a field that is declared in the parent class.
  2. Run the scenario.
  3. Click View Alerts and review any alerts.

Expected result: The scenario runs successfully.

Actual result: The scenario fails because it cannot access the data object in the parent class.

Workaround: Include the data object in the child class.

Rule-based test scenarios that contain maps of simple types fail [RHDM-1015]

Issue: All rule-based test scenarios that contain a map of simple types as a cell value, for example Map<String or String, fail.

Steps to reproduce:

  1. Create a scenario.
  2. Create a map with a simple type value, for example Map<String, String>.
  3. Run the scenario.

Expected result: The scenario runs successfully.

Actual result: The scenario fails.

Workaround: None.

Chapter 6. Fixed issues in Red Hat Process Automation Manager 7.4.0

Red Hat Process Automation Manager 7.4.0 provides increased stability and fixed issues listed in this section.

Note

Red Hat Decision Manager fixed issues apply to Red Hat Process Automation Manager as well. For a list of Red Hat Decision Manager 7.4.0 fixed issues, see the Release Notes for Red Hat Decision Manager 7.4

6.1. Business Central

  • Ability to set the Smart Router location to an external URL [RHPAM-1387]
  • Asset search does not find assets with an extension when using ElasticSearch/Infinispan indexing [RHPAM-1249]
  • Assets created on freshly forked branches appear in their parent branches in a Business Central cluster [RHPAM-1821]
  • Business Central is unable to connect to a co-located controller when deployed at the same time [RHPAM-1910]
  • Business Central Monitoring fails to start a new process in an unmanaged immutable Process Server [RHPAM-2101]
  • The spaces breadcrumb is hidden [RHPAM-2091]
  • Drop-downs in the Security perspective can not be controlled by the keyboard [RHPAM-2085]
  • Error for process diagram containing multiple instance user tasks [RHPAM-2020]
  • Guided decision table is not getting updated [RHPAM-2007]
  • HTTP 503 error is shown in the Monitoring console when Process Server is scaled to 0 [RHPAM-2008]
  • Installing a service task from a project Settings tab only updates the master branch [RHPAM-2026]
  • Missing translations in the UI [RHPAM-1549]
  • Not able to build a project that has a guided scorecard [RHPAM-2055]
  • Problem expanding or dragging the right-most column in the data table of a guided rule template [RHPAM-1559]
  • Running a test scenario locally does not work for guided decision tables [RHPAM-2089]
  • Unable to open projects in Business Central because of the LockObtainFailedException error on Windows [RHPAM-2084]
  • Unexpected error when deleting a project with business processes [RHPAM-1943]
  • User password is exposed in the Readiness probe and Liveness probe [RHPAM-1829]
  • Users with the rest-all role only are not able to communicate with Business Central REST endpoints [RHPAM-2081]
  • Using the same template key with different objects and attributes causes an exception when switching to the Data tab in a guided rule template [RHPAM-1551]
  • The Task Inbox column sort order cannot be switched for certain columns [RHPAM-2032]
  • The Task List saved filter presents different expressions than what was defined in the filter [RHPAM-1957]
  • Provide a mechanism to run webtooling completely offline even without a Maven Central proxy or mirror [RHPAM-1524]
  • Removed call to the jgit deprecated class [RHPAM-2023]
  • Not able to create a project in an offline environment [RHPAM-1282]

6.2. Decision engine

  • Not able to execute scorecard through Process Server remote Java APIs [RHPAM-2107]

6.3. Form modeler

  • Incorrect storing behavior of dates in forms [RHPAM-2000]
  • Multiple selector throws an error on edit [RHPAM-1823]
  • Unable to display task with task input equal to constant [RHPAM-1763]
  • Security exceptions in localhost log when running Process Server on JWS [RHPAM-1787]

6.4. Red Hat OpenShift Container Platform

  • Controller OpenShift Integration properties are not set in APB image [RHPAM-2117]
  • H2 data file is locked during rollout deployment strategy in authoring templates [RHPAM-2125]
  • Use cekit and the supported way to build extension images to provide third party JDBC drivers [RHPAM-1558]
  • Use default hostnames for SSO clients in Red Hat Process Automation Manager OpenShift templates [RHPAM-1307]

6.5. Process engine

  • Cannot configure CXF client connectionTimeout/receiveTimeout for WebServiceWorkItemHandler [RHPAM-2077]
  • OutOfMemoryError occurs when starting a high number of process instances with timers [RHPAM-2106]

6.6. Process designer

  • Business Central process designer prints errors to the server log for the simplest process [RHPAM-1782]
  • Sequence flows from events and gateways are losing endpoint positions [RHPAM-1977]
  • An exception occurs when setting the ruleflow group to a business rule task [RHPAM-445]
  • Labels for events and gateways override the element [RHPAM-1887]

6.7. Process Server

  • A 404 error occurs after an OPTIONS request on Smart Router [RHPAM-2013]
  • PostgreSQL XA datasources do not have a URL method [RHPAM-1997]
  • Process diagram images are hard coded to large sizes [RHPAM-1919]

6.8. Upgrade tool

  • License information is not updated when applying a patch [RHPAM-1388]

Chapter 7. Fixed issues in Red Hat Process Automation Manager 7.4.1

Red Hat Process Automation Manager 7.4.1 provides increased stability and fixed issues listed in this section.

Note

Red Hat Decision Manager fixed issues apply to Red Hat Process Automation Manager as well. For a list of Red Hat Decision Manager 7.4.1 fixed issues, see the Release Notes for Red Hat Decision Manager 7.4

7.1. Business Central

  • Guided scorecard rules are not executed through the test scenario [RHPAM-2064]
  • If you configure Process Server and navigate to the Execution Servers perspective without deploying a project, an error occurs [RHPAM-2031]
  • An error occurs if you copy a guided rule that has a BigDecimal field [RHPAM-2233]
  • The BigDecimal field value is reset to zero (0.0B/0.0) in the guided rule [RHPAM-2262]
  • If you edit the initiator process instance variable an error occurs [RHPAM-2202]

7.2. Decision engine

  • When repositories are read from the settings.xml file and an active proxy is defined, the created repositories do not contain proxy settings [RHPAM-2192]

7.3. Red Hat OpenShift Container Platform

  • The Prometheus server extension disabled property is not set in the APB image [RHPAM-2264]
  • Fix the start-up strategy description in the APB image [RHPAM-2265]

7.4. Process designer

  • If you use the keyboard shortcuts Ctrl-C and Ctrl-V to copy a service task in the new process designer, an error occurs and the model is invalidated [RHPAM-2178]
  • If you use less-than and greater-than symbols in data types, the process breaks [RHPAM-2193]
  • You cannot use a cron expresssion to set the cycle timer [RHPAM-2087]

7.5. Process engine

  • A NullPointerException error occurs in org.drools.core.marshalling.impl.ProtobufOutputMarshaller.writeTimers in a multi-node setup [RHPAM-2198]
  • The addDynamicUserTask method argument should be changed from Description to Subject [RHPAM-2100]

7.6. PMML

  • Applying the PMML model on Process Server fails [RHPAM-2235]

Appendix A. Versioning information

Documentation last updated on Monday, August 12, 2019.

Legal Notice

Copyright © 2020 Red Hat, Inc.
The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version.
Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the United States and other countries.
Java® is a registered trademark of Oracle and/or its affiliates.
XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
Node.js® is an official trademark of Joyent. Red Hat is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
The OpenStack® Word Mark and OpenStack logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community.
All other trademarks are the property of their respective owners.