Release notes for Red Hat Process Automation Manager 7.3

Red Hat Process Automation Manager 7.3

Red Hat Customer Content Services

Abstract

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

Preface

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

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.3 provides increased stability, several fixed issues, and new features.

Red Hat Process Automation Manager is fully supported on OpenShift 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.3.

2.1. Business Central

2.1.1. New development mode and project deployment enhancements for Process Server

You can now set Process Server to run in production mode, formerly the default setting, or in development mode, the new default setting. Development mode provides a flexible deployment policy that enables you to update existing deployment units (KIE containers) while maintaining active process instances for small changes, or to reset the deployment unit state before updating active process instances for bigger changes. Production mode is optimal for production environments, where each deployment creates a new deployment unit, as in previous releases.

Along with this improvement, Business Central also includes new Build & Install and Redeploy options for building and deploying projects. In either a development or production environment, you can select the Build & Install option to build the project and publish the KJAR file to the configured Maven repository without deploying to a Process Server. In a development environment, you can click Deploy to deploy the built KJAR file to a Process Server without stopping any running instances (if applicable), or click Redeploy to deploy the built KJAR file and stop any running instances. The next time you deploy or redeploy the built KJAR, the previous deployment unit (KIE container) is automatically updated in the same target Process Server. In a production environment, the Redeploy option is disabled and you can click Deploy only to deploy the built KJAR file to a new deployment unit (KIE container) on a Process Server.

To configure the Process Server environment mode, set the org.kie.server.mode system property to org.kie.server.mode=development or org.kie.server.mode=production. To configure the deployment behavior for a corresponding project in Business Central, go to project Settings → General Settings → Version and toggle the Development Mode option. By default, Process Server and all new projects in Business Central are in development mode. You cannot deploy a project with Development Mode turned on or with a manually added SNAPSHOT version suffix to a Process Server that is in production mode.

2.1.2. C3 Charts Library

The C3 Chart library replaces the Google Charts library as the default chart library in Business Central. With this improvement, supported chart types can be rendered in the Process & Task dashboard in an offline environment.

Along with this improvement, the following two new system properties are available:

  • org.dashbuilder.renderer.default: You can set which renderer you want to use as the default. The two possible values are c3 and gwtcharts. The current default is c3. If you select c3, the C3 Chart library is used for supported chart types. The missing map type will still use the Google Charts library. If you select gwtcharts, the Google Charts library is used for supported chart types.
  • org.dashbuilder.renderer.offline: This is a boolean property. When true, the property excludes all APIs that do not work offline and their supported chart types are not available for use. You can use this to hide the maps displayer when creating pages. Pages that already use the map displayer will show an error. === GIT hook execution handling

GIT hook execution handling now includes UI notifications to indicate if a script is executed successfully or with a warning or error.

2.1.3. Service task repository integrated with Business Central

The Red Hat Process Automation Manager service task repository (work item repository) is now integrated in Business Central so that you can add and manage service tasks across multiple business processes or across all projects in Business Central. Red Hat Process Automation Manager provides a set of service tasks within the service task repository in Business Central. You can enable or disable the default service tasks and upload custom service tasks into Business Central to implement the tasks in the relevant processes.

To configure service tasks and service task settings globally across Business Central, select the Admin icon in the top-right corner of the screen and select Service Tasks Administration.

To apply the enabled service tasks to processes in a project, navigate to a project in Business Central and go to project Settings → Service Tasks.

For more information about about managing service tasks in Business Central, see Managing and monitoring business processes in Business Central.

2.1.4. Process documentation accessible in process designer

The process designer in Business Central now provides a Documentation tab that summarizes the components, data, and visual flow of the process in a format (PDF) that you can print and share more easily.

2.1.5. Process instance administration

Process instance administration supports operations relating to the process engine and individual process instances. Supported operations:

  • Retrieve process nodes using the process instance ID. Returns all nodes, including embedded subprocesses, that exist in a specific process instance.
  • Cancel a node instance using the process instance ID and node instance ID. Cancels a specific node instance within a process instance.
  • Re-trigger a node instance using the process instance ID and node instance ID. First cancel the active node instance and then create a new instance of the same type, which recreates the node instance.

  • Update the timer using the process instance ID and timer ID. Updates the timer expiration of an active timer. For example, a case timer was initially created with a delay of one hour. After 30 minutes, you want to update the delay to two hours. The case time will then expire in 1.5 hours from the time that it was updated. You can update the following times:

    • Delay - The duration after the timer expires.
    • Period - The interval between timer expiration. This applies only to cycle timers.
    • Repeat limit - Limits the expiration to a specific number. This applies only to cycle timers.
    • Update timer relative to current time using the process instance ID and timer ID. This option is similar to the update timer option, but the update is relative to the current time. For example, if a case timer was initially created with a delay of one hour and after 30 minutes you decide to update the delay to two hours, the delay will then expire two hours from the time that it was updated.
  • List timer instances using the process instance ID. Returns all active timers found for a specific process instance.
  • Trigger a node using the process instance ID and node ID. Enables you to trigger any node in a process instance at any time.

2.1.6. Enhanced task instance log view

The task instance log view now contains filtering capabilities that enable you to narrow down the timeline results according to your needs. There are now two new filter categories that enable you to filter process instances based on event types. These include either node entered, node completed, or process nodes such as human tasks, and start and end nodes.

2.1.7. Authoring collaboration

Authoring collaboration enables users to configure the contributors or a project or space and their role (owner, admin, or contributor) with associated privileges.

2.2. Red Hat Business Optimizer

2.2.1. Deployment of the Employee Rostering starter application on OpenShift

You can now use a template to deploy the Red Hat Business Optimizer Employee Rostering starter application on Red Hat OpenShift Container Platform with persistent data storage.

2.3. Java 11

2.3.1. Java 11 certification

Various distributions of Java 11, such as OpenJDK 11, have been certified as runtime platforms, on par with the pre-existing Java 8 certification. In addition, with this release we are including support for OpenJDK on Windows.

2.4. Red Hat Process Automation Manager on Red Hat OpenShift Container Platform

2.4.1. OpenShift startup strategy for freeform deployment

You can now use the new OpenShift startup strategy feature of the Process Server (KIE server) when you deploy Red Hat Process Automation Manager on Red Hat OpenShift Container Platform. With this feature, an OpenShift-enabled Business Central or Business Central Monitoring discovers Process Servers in the same namespace automatically. You do not need to configure controller settings. This feature provides a freeform deployment architecture, which enables you to easily deploy any number of Process Servers.

2.4.2. Ansible Playbook Bundle for Openshift

An Ansible Playbook Bundle (APB) for installing Red Hat Process Automation Manager on Red Hat OpenShift Container Platform using the OpenShift Automation Broker is now available. You can use this APB to deploy Red Hat Process Automation Manager on OpenShift interactively in the OpenShift Web Console by selecting the environment architecture and providing all settings as necessary.

2.5. Process designer

  • Infinite canvas: Infinite canvas provides the ability to extend the canvas as large as needed for process modeling.
  • Graphical constraint editor: A graphical constraint editor has been added to define constraints without coding and without knowledge of technical terminology.
  • Process designer DMN support: The business rules task has been extended to support invoking Decision Model and Notation (DMN) from a process.
  • Reusable sub-process: A few additional properties were added to the reusable sub-process node that are related to on-entry and on-exit scripts.
  • New process designer properties: The new process designer now supports the executable and globals properties.
  • Process Designer support for multi-instance sub-process and task: A multiple instance sub-process or task is a sub-process or task that enables you to execute a contained process segment or task multiple times, once for each element in a collection.
  • Process designer RuleFlow profile: A new profile was introduced in the new process designer so that the palette only contains elements that apply to rule flow use cases targeted in Red Hat Decision Manager. When you switch the configuration in Business Central administration to the rules and planning profile for Red Hat Decision Manager (rather than the full profile for Red Hat Process Automation Manager), the new process designer automatically use the RuleFlow profile.
  • New process designer support for the BPMN resolution attribute: BPMN files that are imported into the new process designer can use this attribute to scale the imported project.

2.6. Spring Boot

2.6.1. Spring Boot 2.1.x

Red Hat Process Automation Manager support for Spring Boot has been updated from Spring Boot 1.5.x to Spring Boot 2.1.x.

2.7. Components moved from technology preview to fully supported

2.7.1. Decision Model and Notation (DMN) designer

The Decision Model and Notation (DMN) designer in Business Central is now fully supported in Red Hat Process Automation Manager 7.3. You can use the new DMN designer in Business Central to design DMN decision requirements diagrams (DRDs) and define decision logic for a complete DMN decision model. Red Hat Process Automation Manager 7.3 provides both design and runtime support for DMN 1.2 models at conformance level 3, and includes enhancements and fixes to FEEL and DMN model components to optimize the experience of implementing DMN decision services with Red Hat Process Automation Manager.

The improved DMN designer also includes the following notable enhancements:

  • New support for decision service nodes in DRDs
  • Automatic layout for imported DRDs
  • Improved DMN data types and constraints
  • Improved DRD validation when assets are saved or built

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

2.7.2. Test Scenarios designer

The Test Scenarios designer in Business Central is now fully supported in Red Hat Process Automation Manager 7.3.

  • Data object list support: The Test Scenarios designer in Business Central now supports data object lists in Red Hat Process Automation Manager 7.3. You can now define and test scenarios that include Java collections as inputs (given values) or outputs (expected values). A concrete collection can now be defined as a value of a particular cell. The collections can be created, modified, and removed at any time during the development of a test scenario.
  • DMN support: The Test Scenarios designer in Business Central now supports DMN-based test scenario assets in Red Hat Process Automation Manager 7.3. You can now create test scenario assets that are rule-based, to test all rules inside all DRL files within the project, or DMN-based, to test all decisions defined inside one particular DMN file.
  • Visual test results: The Test Scenarios designer in Business Central now provides visual test results in Red Hat Process Automation Manager 7.3.

2.8. Other enhancements

  • Ability to set the drools.trimCellsInDTable system property to false in a Red Hat Process Automation Manager distribution to retain intentional white space before or after values in decision table cells.
  • New domain specific language (DSL) and fact type search filter when adding conditions or actions to guided rules and guided rule templates.
  • Ability to include slashes in Git branch names.
  • jBPM Audit mode (none, JPA, JMS) improved to simplify setup and configuration. In addition, jBPM Audit mode now includes all of the audit logs that span across processes, user tasks, and cases.

Chapter 3. Deprecated components

The components listed in this section have been deprecated.

3.1. Legacy Test Scenarios tool

The legacy Test Scenarios tool is deprecated with Red Hat Process Automation Manager 7.3.0. It will be removed in a future Red Hat Process Automation Manager release.

3.2. Internet Explorer 11

Internet Explorer 11 is deprecated with Red Hat Process Automation Manager 7.3.0.

Chapter 4. Technology preview

This section lists features that are in technology preview in Red Hat Process Automation Manager 7.3. Business Central includes an experimental features administration page which 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 OpenShift)

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. Red Hat Process Automation Manager may choose to replace that technology in the future while preserving the capability offered.

4.2. Case modeler

Case modeler now 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.3 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.

Chapter 5. Known issues

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

5.1. Business Central

You cannot upload a spreadsheet that contains a large decision table [RHDM-488]

Issue: If you try to upload a spreadsheet that contains a large decision table into Business Central, an out-of-memory error appears in the error.log file.

Steps to reproduce:

  1. Create a spreadsheet that contains a large decision table.
  2. Create a new project in Business Central.
  3. Click Add Asset and then select Spreadsheet Decision Table.
  4. Attach the spreadsheet that contains the large decision table.
  5. Review the server error.log file.

Actual result: An out-of-memory error appears in the error.log file.

Workaround: None.

An unexpected error occurs if you delete a project that contains a business process [RHPAM-1943]

Issue: If you delete a project that contains a business process, an unexpected error occurs.

Steps to reproduce:

  1. Create a project in Business Central.
  2. Add a business process asset to the project.
  3. Save the business process asset.
  4. Delete the business process asset.

Expected result: The business process asset is deleted.

Actual result: An error occurs.

Workaround: None.

The palette of an existing process is not in sync with project settings changes [RHPAM-1925]

Issue: If you enable or disable a service task in the Administration page or install or uninstall a service task in the project’s settings Service tasks section, when you open the process the palette displays the original state of the service task. If you install a service task, the service task is not shown in the palette. If you uninstall a service task, the service task is still shown in the palette.

Steps to reproduce:

  1. Create a project.
  2. Create a process called P1.
  3. In the project’s settings, install a new service task.
  4. Create a process called P2.
  5. Verify that the service task is present in the palette of process P2.
  6. Create a process using the newly added task.
  7. Go to process P1.
  8. Examine the palette and observe that the service task is not available.
  9. Go to the project’s settings and uninstall the service task.
  10. Go to process P2.
  11. Examine the palette and observe that the service task is still present in the diagram and available in the palette.

Expected result: The palette reflects the state of the process.

Actual result: The palette is out of sync with the state of the process.

Workaround: After you install or uninstall an item in the service repository, close and reopen the process designer editor.

5.2. Installer

The controller URL is not updated in the standalone.xml file if only Process Server is installed [RHPAM-1781]

Issue: When you run the Red Hat Process Automation Manager installer and you specify a URL for the controller, the URL is not updated in the Red Hat JBoss EAP standalone.xml and standalone-full.xml files.

Steps to reproduce:

  1. Run the Red Hat Process Automation Manager installer.
  2. Specify an Red Hat JBoss EAP installation for container.
  3. Select only Process Server to install.
  4. Select Advanced Configuration and update controller URL.
  5. Complete the installation.
  6. Open the Red Hat JBoss EAP standalone.xml or standalone-full.xml file and find the controller URL.

Expected result: The value of the controller URL property is the URL that you entered during installation.

Actual result: The value of the controller URL property is the default value.

Workaround: Manually update the value of the controller URL property in the Red Hat JBoss EAP standalone.xml and standalone-full.xml file.

5.3. Process Server

You cannot deploy a KJAR with a PMML asset to a Process Server Spring Boot starter on Windows [RHDM-852]

Issue: If a KJAR contains a PMML asset, you cannot deploy it as a container on a Process Server that is running in the kie-server-spring-boot-starter Spring Boot starter on Microsoft Windows.

Steps to reproduce:

  1. Create a KJAR that contains a PMML asset.
  2. Start kie-server-spring-boot-starter on Windows.
  3. Deploy the KJAR to a Process Server that is running the kie-server-spring-boot-starter Spring Boot starter on Microsoft Windows.

Expected result: The KJAR is deployed successfully.

Actual result: The KJAR cannot be deployed.

Workaround: None.

5.4. OpenShift

User password is displayed in the Readiness and Liveness probes [RHPAM-1829]

Issue: If you deploy Red Hat Process Automation Manager on OpenShift, the user password is displayed in both the Readiness and Liveness probes.

Workaround: None.

5.5. Red Hat Business Optimizer

ScoreCalculationCountLimit termination does not work with multi-threaded solving [RHDM-740]

Issue: Red Hat Business Optimizer configured with the score calculation count termination (ScoreCalculationCountLimit) does not terminate. The score calculation count termination is primarily used for testing.

Workaround: Use another type of termination.

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

Red Hat Process Automation Manager 7.3.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. See the Release Notes for Red Hat Decision Manager 7.3 for a list of Red Hat Decision Manager 7.3.0 fixed issues.

6.1. Business Central

  • If a rule has a name that contains "%", the URLDecoder: Illegal hex characters in escape (%) pattern error occurs [RHPAM-1184]
  • The contents of a Business Central page do not automatically adjust when you resize the browser window. [RHPAM-1583]
  • The data set remains broken after incorrect filter values have been fixed [RHPAM-1572]
  • Cannot build and deploy a project in Business Central when connected to a snapshot Maven repo [RHPAM-1544]
  • With standalone Business Central, the actor configuration in Human Tasks does not work [RHPAM-1647]
  • Using the settings of a project in an existing KIE base and KIE session causes the UI to hang [RHPAM-1929]
  • When accessing the Instance Details page, an unexpected error occurs [RHPAM-1901]
  • The process instance diagram alert is not visible [RHPAM-1908]
  • When a process task fails at the beginning of the process, the process fails with two consecutive error dialogs [RHPAM-1903]
  • Process Instance diagram node count badges are misplaced [RHPAM-1902]
  • The index is always recreated after Business Central reboots [RHPAM-1856]
  • It is not possible to set resolver (mvel, spring, reflection) while adding a new configuration entry to a deployment descriptor [RHPAM-1322]
  • Unable to disable weak CBC ciphers and HMAC [RHPAM-1789]
  • All assets are indexed four times when aproject is created through the UI [RHPAM-1455]
  • The kie-soup-dataset-elasticsearch pom.xml file is not XSD-valid [RHPAM-1743]
  • Bulk abort throws an exception when called on several subprocess instances [RHPAM-1761]
  • Horizontal scroll bars are missing in the Task inbox [RHPAM-1859]
  • Process Server loses connection to Business Central [RHPAM-1354]
  • The Loading application…​ pop-up message is garbled in the Japanese locale (locale=ja) [RHPAM-1205]
  • Business Central clustering does not work with Red Hat Data Grid [RHPAM-1661]

6.2. Decision engine

  • Problem with calculating the property reactivity mask of a from node [RHPAM-1899]
  • An out-of-memory error occurs when creating a KieSession [RHPAM-1885]
  • A livelock occurs in PseudoClockScheduler [RHPAM-1852]

6.3. Form modeler

  • An error appears when you click New Instance in the MultipleSubForm properties window [RHPAM-1027]

6.4. Fuse integration

  • Running the createContainer method using the kie-camel component returns null [RHPAM-1725]
  • Missing producers for Process Server clients in the kie-camel component [RHPAM-1770]
  • It is not possible to call most of the methods of a remote client in the kie-camel component [RHPAM-1699]

6.5. Installer

  • The installer QuitDialog displays incomplete text [RHPAM-1857]
  • If you use the installer to install only Process Server, the standalone-secure.sh and standalone-secure.conf files are not installed [RHPAM-1255]
  • If you installed Red Hat JBoss EAP 7.2 using the Red Hat JBoss EAP installer, the Red Hat Process Automation Manager 7.2.1 installer fails [RHPAM-1913]
  • The installer path validation is not working as expected [RHPAM-1958]
  • The Null validation error displays when the wrong installation path installation path is entered [RHPAM-1955]

6.6. Maven repository

  • Some tests are not part of the Maven build [RHPAM-1904]
  • Some Uberfire libraries are missing from the Red Hat Maven repository [RHPAM-1802]

6.7. OpenShift

  • The rhpam73-authoring-ha.yaml template does not configure AMQ for high availability [RHPAM-1180]
  • Incorrect Process Server location for OpenShift deployments created with the APB image [RHPAM-1663]
  • Add a check for the APB Image Managed Environment plan when it is used in an external DB [RHPAM-1634]
  • Missing the controller user and Maven user in the APB configuration [RHPAM-1629]
  • Several images fail content set testing [RHPAM-1832]
  • A database exception occurs when you use the rhpam70-kieserver-externaldb.yaml to connect to PostgreSQL [RHPAM-904]
  • EAP users are not created if LDAP or SSO authentication is used [RHPAM-1430]
  • Wrong value of controller protocol for Smart Router in the rhpam72-prod-immutable-monitor template [RHPAM-1850]
  • Cannot use an external DB2 database with the externaldb template [RHPAM-1445]
  • Support the use of database connection URL for EJB timers [RHPAM-1179]

6.8. Process designer

  • Cannot set a sub-process process from a different project as reusable [RHPAM-699]
  • A BPMN2 process causes the new process designer to crash with an EMF error [RHPAM-856]

6.9. Process engine

  • An error occurs while canceling command [RHPAM-1691]
  • A recurring command is not executed after temporary database unavailability [RHPAM-1687]
  • Variables in the task description are no longer resolved after migration [RHPAM-1659]
  • A performance issue occurs when using the getProcessInstancesByVariableNameAndValue query [RHPAM-1735]
  • A KJAR added as a dependency of a Spring Boot application is not properly found when a creating a class path KIE container [RHPAM-1839]
  • Incorrect syntax in Sybase DDL scripts [RHPAM-1836]
  • Process status is STATUS_COMPLETED in ProcessEventListener.beforeProcessCompleted [RHPAM-1805]

6.10. Process Server

  • NoSuchAlgorithmException occurs when starting Smart Router with HTTPS [RHPAM-1576]

6.11. Scenario simulation

  • Cannot create Scenario Junit activator in sample projects [RHPAM-1923]

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

Red Hat Process Automation Manager 7.3.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. See the Release Notes for Red Hat Decision Manager 7.3 for a list of Red Hat Decision Manager 7.3.1 fixed issues.

7.1. Business Central

  • The NoClassDefFoundError appears in the server log file when a service task is installed in a project [RHPAM-1947]
  • Business Central cannot connect to a co-located controller when deployed at the same time [RHPAM-1920]
  • The package name white list should contain the project’s default package [RHPAM-1890]
  • Column sorting is not retained after filters are applied in the Task Inbox [RHPAM-1700]

7.2. Form modeler

  • When you start a process instance in Business Central the modal window contains the previously rendered form until the new form renders [RHPAM-1951]
  • The multiple selector throws an error when edited [RHPAM-1861]

7.3. Installer

  • The default placeholder for the controller URL should contain business-central when installing Process Server and Business Central [RHPAM-1774]
  • The controller URL is not updated in XML files when only Process Server is being installed [RHPAM-1781]
  • You cannot use the installer to install Red Hat Process Automation Manager on JWS 5.1 [RHPAM-2038]

7.4. OpenShift

  • Setting the Maven mirror URL does not exclude Business Central [RHPAM-1994]
  • The KIE server image does not run correctly when EJB is initialized first [RHPAM-1970]
  • Business Central throws an exception when the user clicks a deployment unit [RHPAM-1952]
  • ServerTemplateConverter breaks with KieServerMode mixed-case [RHPAM-1975]

7.5. Process designer

  • You cannot open a callable process that contains spaces and extended characters [RHPAM-2006]

7.6. Process engine

  • Process Server is not removed from the controller view if the server is killed or crashes [RHPAM-1654]
  • The newly added org.jbpm.correlationkey.length system property does not truncate the Value column in the CorrelationPropertyInfo table [RHPAM-1961]
  • The Process Server client does not reuse the marshaller for JMS [RHPAM-1988]
  • An EJB timer error occurs in development mode for an existing process during deploy [RHPAM-1985]

Appendix A. Versioning information

Documentation last updated on Wednesday, May 8, 2019.

Legal Notice

Copyright © 2019 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.