6.0.2 Release Notes

Red Hat JBoss BPM Suite 6.0

Release Notes for Red Hat JBoss BPM Suite

Eva Kopalova

Red Hat Content Services

Abstract

Release notes for Red Hat JBoss BPM Suite 6.0.2

Chapter 1. Introduction

1.1. About Red Hat JBoss BPM Suite

Red Hat JBoss BPM Suite is an open source business process management suite that combines Business Process Management and Business Rules Management and enables business and IT users to create, manage, validate, and deploy Business Processes and Rules.
Red Hat JBoss BRMS and Red Hat JBoss BPM Suite use 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.
To accommodate Business Rules component, Red Hat JBoss BPM Suite includes integrated Red Hat JBoss BRMS.
Business Resource Planner is included as a technical preview with this release.
Report a bug

1.2. What's new in Red Hat JBoss BPM Suite 6.0.2

Red Hat JBoss BPM Suite 6.0.2 is an incremental bug fix release over the 6.0.1 version. Over 250+ bug fixes in all areas of the product since the 6.0.1 version makes this the most stable version of Red Hat JBoss BPM Suite.
The following features are new in this release:
  • Support for Websphere: BPMS is now supported on IBM Websphere 8.5. For detailed installation instructions please refer to the BPM Suite IBM Websphere Installation and Configuration Guide.
  • RHEL 7.0 Certification: BPMS 6.0.2 is certified to run on RHEL 7.
  • Quickstarts: Multiple quickstarts are provided in this version of BPMS to demonstrate how to use BRMS and BPMS to manage and deploy business process and rules. These quickstarts provide small, specific, working examples that can be used as a reference for your own project.
Report a bug

1.3. Use Case: Process­-based solutions in the loan industry

Red Hat JBoss BPM Suite (BPMS) can be deployed to automate business processes, such as automating the loan approval process at a retail bank. This is a typical 'Specific Process-Based' deployment that might be the first step in a wider adoption of BPM throughout an enterprise. It leverages both the BPM and business rules features of BPMS.
A retail bank offers several types of loan products each with varying terms and eligibility requirements. Customers requiring a loan must file a loan application with the bank, which then processes the application in several steps, verifying eligibility, determining terms, checking for fraudulent activity, and determining the most appropriate loan product. Once approved, the bank creates and funds a loan account for the applicant, who can then access funds. The bank must be sure to comply with all relevant banking regulations at each step of the process, and needs to manage its loan portfolio to maximize profitability. Policies are in place to aid in decision making at each step, and those policies are actively managed to optimize outcomes for the bank.
Business analysts at the bank model the loan application processes using the BPMN2 authoring tools (Process Designer) in BPM Suite:
High-level loan application process flow

Figure 1.1. High-level loan application process flow

Business rules are developed with the rule authoring tools in BPM Suite to enforce policies and make decisions. Rules are linked with the process models to enforce the correct policies at each process step.
The bank's IT organization deploys the BPM Suite so that the entire loan application process can be automated.
Loan Application Process Automation

Figure 1.2. Loan Application Process Automation

The entire loan process and rules can be modified at any time by the bank's business analysts. The bank is able to maintain constant compliance with changing regulations, and is able to quickly introduce new loan products and improve loan policies in order to compete effectively and drive profitability.
Report a bug

Chapter 2. Technical Preview

Warning

Business Resource Planner is included with this release as a technical preview. Technical previews are included as a preview of the software only. They are not supported in production by Red Hat, may not be functionally complete, and are not intended to be deployed in a production environment.

Note

These features are included to provide customers with early access to upcoming product innovations, enabling them to test functionality and provide feedback during the development process.
Report a bug

Chapter 3. Fixed issues

The 6.0.2 release of Red Hat JBoss BPM Suite has over 250+ bug fixes over the 6.0.1 version. These bug fixes span across the various components like jBPM Core, jBPM Designer, Data and Form Modeler, Eclipse Tooling and BAM. The majority of the fixes have been done to the Business Central component making it robust and stable.
The following issues are some of the high priority bugs that were fixed in this release of Red Hat JBoss BPM Suite.

BAM

1074448 - Dashboard filter auto-refresh causes Unexpected error (CSRF Token missing)
While Dashboard Filter's auto-refresh feature was enabled, errors would occur whenever auto-refresh was started, stopped, or edited. An unexpected error would display even if the user did not interact with the application. This issue has been resolved and no more exception errors are thrown for the auto-refresh feature.

Business Central

1079905 - Only 1 process shown for 2 versions of deployment even with different process version.
When a project with different versions was deployed multiple times the process definition list only showed one version of the process definition. This caused an issue deploying different versions of a project. This issue has now been fixed.
1069747 - Save button does not work with FreeMarkers forms.
A process with a FreeMarker form (*.FTL) didn't save its data on clicking the save button. Instead, an error message would be generated in the log files with the message "User '[UserImpl:'***']' was unable to execution operation 'Start' on task id 4 due to a no 'current status' match". This issue has now been fixed.
1084044 - Properties file can't be load in LDAPUserGroupCallbackImpl.
The two options available for loading property files in the LDAPUserGroupCallbackIml were not functional and buggy.
The files were not loaded when their location was specified by a system property and neither were they loaded when they were dropped under business-central.war/WEB-INF/classes folder. The only workaround was to add the property files directly in the org.jbpm module.
This has now been fixed by allowing any valid URL to specify location of the UserGroupCallback property file. In addition to URL protocols (file, http, etc) you can now use classpath. If no protocol is available (no valid URL) the classpath based location is assumed. From classpath the system will try to load first from local class loader (class that requires the reading) and if not found fall back to thread context class loader.
1082032 - NPE displayed in the output of rest query which tries to retrieve information about work item which not exists.
A NullPointerException was displayed to the user when a query was made via a REST command for a WorkItem that didn't exist. Instead of informing the user that the WorkItem didn't exist anymore, the exception was displayed.
This has now been fixed by displaying a user friendly message on execution of such a query: 'RestOperationException thrown with message 'WorkItem 1 does not exist.'
1076615 - Business-central gives notification about file upload being successful, however, file is not uploaded.
Uploading a file via Authoring → Artifact Repository in Business Central resulted in a “Uploaded Successfully” message, but no file was actually uploaded. The workaround was to restart BPMS. However, in the latest version of BPMS, this issue has been fixed.
1080329 - Process changes are not reflected after redeploying unit with same GAV and process version.
Process changes were not being reflected when a project was re-deployed with the same GAV (Group, Artifact and Version) and the same BPMN version. The only known workaround was to change any of the GAV for that project.
This issue has now been fixed by ensuring that on undeploy of runtime manager the releaseId of the project was removed from the local KIE repo. The repo used to keep a local cache of deployed artifacts and this was causing the older version of the project to be used on runtime.
1072840 - JAXB exception due to serialization of task parameters.
Sending an object as a parameter to the execute task for a REST service resulted in a SerializationException error. This error only occurred when calling the complete method of TaskService. If CompleteTaskCommand was used and the execute method of KieSession was invoked with this command as a parameter there was no error and the task status was changed to completed. This applied to both REST and JMS. This issue has now been fixed.
1065314 - Unable to retrieve a JSON formatted Task instance via the REST API.
REST operations that retrieved Task instances would fail when forced to use the JSON format (ACCEPT header). There was a server side error thrown when the server instance tried to convert the (JAXB) Task instance to JSON. The workaround for this issue was to use XML instead of JSON (by setting it in the ACCEPT header).
This issue has now been fixed in the latest version of the product and the workaround is no longer required.
1088312 - Race Condition in REST deployment operations causes NPE to be thrown when requesting a list of deployments.
Requesting a list of current deployments using the REST API while a deploy or undeploy request is pending caused a race condition terminating in a NullPointerException. This issue has now been fixed by modifying the code to prevent the race condition from happening.
1077332 - Unable to make a copy of a rule if the name of the copy contains spaces.
Trying to copy a rule in Business Central caused errors if the new rule name contained spaces. A workaround was to give the new rule a name without spaces while copying and then once the copy was done successfully, to rename it with spaces. This issue has now been fixed in the latest release and copy operations complete successfully with spaces in the name.
1078337 - Unfinished support for Custom Work Item Handlers in business-central.
It was not possible to register Custom Work Item Handlers via Business Central, even though it was possible to add them via Business Central. This has now been fixed by using reflection to register the work item beans.
1067772 - Cannot get group task list through JMS client
Task operations using JMS did not correctly look up the groups the user was a part of. As a result, a user would not be allowed to perform operations on tasks if those operations required the user to be part of a specific group (for example, claiming a group task). This has been resolved by extending the UserGroupCallback mechanism in human-tasks for JMS call support.
1042789 - Inform a user that a kjar cannot be uploaded due to missing dependencies instead of throwing IllegalArgumentException: number of transferred bytes cannot be negative
The system used to throw an IllegalArgumentException when a kjar with missing dependencies was uploaded. This message was not very clear about the actual error and it was often misleading. The system now informs the user with a more helpful error message when a kjar with missing dependencies is uploaded.
1076593 - A task is still present though the process instance was aborted in JBoss EWS 2.0
While running Business Central through JBoss EWS 2.0, users would still receive task information even after a process instance was aborted. This was caused by a missing TransactionSynchronizationRegistry in tomcat configuration. This has been resolved by adding the TransactionSynchronizationRegistry into the context.xml file.

jBPM Core

1082091 - ClassCastException for ConnectTimeout REST WorkItem/Service Task input parameter.
A REST service task added to a process would cause errors on deployment with a ClassCastException error with an assignemnt set for the URL property. The error was caused due to incorrect typing of DataInputSet properties for the URL like ConnectTimeout and ReadTimeout. This issue has now been fixed.
1070878 - It is not possible to query tasks with status InProgress using REST API.
Using the REST API, it was not possible to execute any queries that had the status of InProgress. The server would return a BAD_REQUEST flag in response to the query with a message saying that the status “Inprogress is not a valid status type for a task”. This issue was caused due to the lack of a method that didn't transform the string input to the correct corresponding value of enum and has now been fixed by the addition of this method.
1072774 - NPE when I register a workitem handler
While registering a work-item handler through a ksession and work-item manager, users would sometimes experience a method fail with a NullPointerException. This error occurred with the drools.session.conf and the CustomWorkItemHandlers in the home directory. The configuration files were poorly loaded which caused the error. This issue has been resolved by ensuring that class path resources will only override values from the home directory when such values exist.

jBPM Designer

1073654 - Process can not be reopened in Designer if it is imported containing missing data types.
The Process Designer was unable to open processes containing user tasks that had been written externally if they contained missing data types. While trying to open such processes, an exception was thrown and nothing was displayed. The runtime for BPMS could execute these processes, but the Process Designer GUI had trouble displaying them. In addition, a process that contained "." in process variable names also caused issues when they were displayed in the Process Designer.
Both these issues have now been fixed with this release.
Report a bug

Chapter 4. Known issues

The following issues are known to exist in this release of Red Hat JBoss BPM Suite. To see a list of known issues for BRMS 6 please see Release Notes for BRMS 6.0.

BAM

1026516 - Tomcat 7 - Invalid credentials - throws a NullPointer exception
When using the Tomcat 7 Dashbuilder Distribution, users logging in with invalid credentials receive an error page with a nullpointer exception. The expected result should be an "Invalid Credentials" error message. A possible workaround from encountering the error page with a nullpointer exception is to use basic authentication instead of form based authentication when logging in.

Business Central

1020922 - Details button in Process Definitions not working.
Within the Process Definitions perspective, the details button (magnifying glass icon) does nothing if there are so many processes in the process definitions list that they cannot be shown on a single page. The details button should bring up the details of a process in a side panel; however, nothing occurs. A current work around is to click on a corresponding row, other than the actions column, and bring up any other details page. The buttons should start working again.
1080441 - Classes from dependencies are not recognized when using remote API
When using custom Java classes (created using the data modeler or by uploading existing jars) through the remote interfaces (REST, JMS), the user must put these classes in the project itself or in a direct kjar dependency of that project to be picked up for correct (de)serialization. Classes defined in normal (non kjar) dependencies or second level dependencies are currently not picked up by the remote API and will result in (de)serialization errors.
1050894 - A deployment unit in JaxbDeploymentJobResult is wrongly marshalled into JSON
Using the REST API to create a new deployment unit causes the response to be incorrectly marshalled into a JSON object. The response cannot be unmarshalled but the deployment process will eventually happen. As a workaround, it is possible to require "application/xml" format in the Accept part of the request message header.
1026807 - Integrity constraint violation in table OrganizationalEntity using roles and users of the same name
A constraint violation occurs when a task is created for a user with the same login name as the name of one of the roles. The task and corresponding process cannot be completed. The workaround is to not use the same user name as the name of a role.
1007986 - Escalate task that has actor or group that does not exist
When creating a user task in Designer, actors and groups should be provided. However, there is no validation of these actors and groups. They just appear as a String. If the group or actor does not exist, such a task cannot be claimed and completed properly. Assigned rules can be used to configure auto-escalation as a workaround.
1007549 - View Process Instances in Definition Details shows all instances
While viewing process instances, users are able to view instances of similar names to those of the process definition currently being viewed. For example, processes named "process1" and "process1x" are both visible even if the user clicked Options → View Process Instances for "process1" only.
1043514 - Remote REST kie client may occasionally throw NPE under high load
Remote REST KIE client may occasionally throw NullPointerException. It is a cookie problem and happens only under a high load of requests. This issue does not have an impact on BPMS functionality.
1100655 - Inter-Process communication via signals fails when current kie.policy file is enabled
Inter-process communication fails when signals and human tasks are used in Business Central. The problem stems from the kie.policy file not containing appropriate permissions. Adding the "write" permission to 
permission java.util.PropertyPermission "*","read";
results in a successful task completion. If a "java.security.AccessControlException: access denied" warning occurs, then add the following permission to the policy file: 
"java.lang.reflect.ReflectPermission" "suppressAccessChecks"
988810 - BPMS should not allow to build & deploy a project, which has multiple process definitions with the same ID
Business Central currently allows users to build & deploy a project where multiple process definitions share the same process ID. However, only one of the process definitions is visible in the process definitions screen. This leads to an inconsistency as you cannot determine which process will be started. In addition, users are unable to start other processes of the same name. A proposed workaround to this issue is to provide a warning to the user to issue different process IDs for each process definition.
1020987 - Unexpected pagination behaviour
Items listed in Business Central appear on multiple pages. For example, if an item belongs on page 1, it may be on page 2 as well. So if there are 14 items in the chosen list and 10 items per page, items 1-10 will be displayed on page 1 and items 5-14 will be displayed on page 2. This is a standard behaviour of the GWT Data Grid Pager component where the user always views a whole page. This issue may be a slight inconvenience to the user, but it does not affect functionality.

jBPM Core

1036866 - session-migration: updating a process instance results in ID constraint violation.
A ConstraintViolationException error occurs when attempting to update the state of a process instance. For example, a BPM Suite 5 process executed with a safe point that is resumed in BPM Suite 6 will issue a "duplicate key value violates unique constraint" error message. This issue affects the Oracle and PostgreSQL databases.

Procedure 4.1. PostgreSQL

  1. To workaround this issue for PostgreSQL, find the ID with the biggest value in the "NodeInstanceLog" table: 
    SELECT MAX(id) FROM nodeinstancelog;
  2. Restart sequence NODE_INST_LOG_ID_SEQ using the result from the biggest value in the "NodeInstanceLog" increased by 1. For example, if the biggest value in the "NodeInstanceLog" is 10, you will use the following: 
    ALTER SEQUENCE node_inst_log_id_seq RESTART WITH 11;

Procedure 4.2. Oracle

  1. To workaround this issue for Oracle, find the ID with the biggest value in the "NodeInstanceLog" table: 
    SELECT MAX(id) FROM nodeinstancelog;
  2. Re-create the sequence by first dropping it and then creating a new one: 
    DROP SEQUENCE NODE_INST_LOG_ID_SEQ;
    CREATE SEQUENCE NODE_INST_LOG_ID_SEQ START WITH 11 INCREMENT BY 1 NOCYCLE;
  3. Increase the sequence (the result must be greater than the biggest value in the "NodeInstanceLog" table): 
    ALTER SEQUENCE NODE_INST_LOG_ID_SEQ INCREMENT BY 100;

jBPM Designer

1105264 - Business Central gets progressively slower opening BPM diagrams
The GIT repository underlying Business Central has issues with garbage collection. Only a few git commands call 
gc --auto
by default. Therefore, the repository's object database continues to grow significantly every time the business processes are opened. This affects the performance of Business Central.
1104582 - WAS: Services from service repository are not imported
A "Failed to connect to Service Repository" error message occurs when attempting to import via http protocol from the WAS service repository. The issue stems from a lack of index.html available in the root of the repository. To work around this issue, an empty index.html file needs to be created within the root of the WAS service repository.
1083259 - Designer should prepare Content and ContentType fields for data input and prefill required assignments of a REST task
Designer does not provide default values for Content and ContentType data assignments when creating a new REST task. Currently, the following data inputs and data assignments are available by default: Password, Method, Username, ReadTimeout, ConnectionTimeout, and URL. Designer is also missing all assignments for the data inputs. The user will need to add the data inputs and assignments manually if they are to be used.
1062233 - Relative vs absolute coordinates for nested nodes
Nested nodes (inside a embedded subprocess or swimlane) use coordinates relative to the top left corner of its parent (instead of the top left corner of the canvas). As a result, if you import this process in Eclipse BPMN2 Modeler, it will fail to correctly locate these nodes.
1047891 - Simulation results: Nodes in event subprocess are not marked as visited
When you run a simulation, the Simulation engine does not mark elements which run in event subprocess. This state is displayed by the path results and the Simulation results for such elements exist in the tree of graphs. A user is likely to assume that the elements in event subprocess were ignored by simulation engine when they have actually been run.
1045346 - Cannot attach boundary event to Ad-Hoc Subprocess
It is not possible to add a boundary event to an ad-hoc subprocess. An embedded subprocess can be used instead of an ad-hoc subprocess to simulate the expected behaviour.
1044613 - Connection rendering issue of Designer in IE11
While users design processes in the Business Process Designer, previous connections are still being incorrectly rendered on the canvas whenever the end docker of a sequence flow is dragged to another task. This is only an issue with Internet Explorer 11. The current work around is to use an alternative browser. In addition, incorrectly rendered connections will disappear when you switch tabs (for example, switch to the metadata tab or Simulation Results tab) or reopen designer.
1040910 - Unable to open WID editor for custom task which was imported from Service Repository
An error occurs when attempting to open a custom task from the global folder which was previously imported from a service repository. The error "unable to complete your request. The following exception occurred: null" appears within an empty WID editor.
1026965 - Designer falsely detects midair collision when only one user is working in a process
Process modeler incorrectly detects multiple users working on a process. It doesn't prevent the user from working with the process but just displays a message. This error occurs intermittently.
991374 - Unable to open BPMN2 definition which contains DataObject without name
When creating a new BPMN2 process, if the user doesn't assign a name to a DataObject unit, the project will not reopen after saving. The Designer will attempt to open the project but will never load.
1048281 - Missing file bpmn2.0jbpm.json causes that new process ends with exception
While loading new processes in Designer, an exception error occasionally occurs with the following message: "java.io.FileNotFoundException: .../bpmn2.0jbpm.json". The new process cannot be opened whenever this exception happens. A workaround for this issues is to delete the process from the Project Explorer and create it again. If the problem persists, try refreshing the website (F5).
1049506 - IE 10: Simulation graphs tree does not react to any mouse event
When using the IE10 browser, the tree of simulation results does not handle a click event. Only general simulation results are seen and the detailed ones are not available. There is no known workaround at this point in time.
1049489 - IE 10: Collapsed Object Library or Properties bar grows when the user resizes Designer panel
While using IE 10, the collapsed Object Library Panel and Properties Bar Panel grow whenever the user drags a splitter or resizes a panel within Designer. Currently there is no workaround, but the initial size can be restored whenever you reopen a process.
1049372 - IE: Missing arrow for connecting object
While using IE 10, Designer does not show pointer arrows to indicate the direction for connecting objects. The source "start point" and target "end point" become somewhat confusing within the sequence flow as no arrow indicates direction.
1039012 - Instance diagram shows outdated instance state
If an instance state changes while the process instance model/diagram is open in Designer, the model/diagram is not updated. If the instance diagram is opened from an out-of-date Instance Details panel, the model/diagram is also not updated. Therefore, the process instance model/diagram is outdated and does not reflect the updates to the current instance state. A current workaround is to close and reopen the process instance model/diagram from an up-to-date Instance Details panel.
1034730 - Changing snapshot time causes snapshots being created event though no modification was made.
Changing snapshot time in Designer creates a snapshot event even if no modifications were made. After a snapshot time is set and changes are made in Designer, additional modifications to the snapshot timer are still necessary and the snapshots are not being created automatically.
1019883 - Properties bar does not show which element contains these properties.
The header properties bar contains a similar title of "None" for different elements. For example, a Start Event displays the header "Properties[None]" instead of a more accurate header. The user is unable to determine which element contains these properties based on such a vague identifier.
1006953 - After editing a property, clicking properties header discards changes.
If you happen to click a header in the properties tab that makes the list collapse or expand, the editor line will disappear, and any property changes made in Designer will no longer be present.
1003908 - Non-Interrupting boundary event has invalid graphical semantics
Designer is not changing the graphical semantic of a boundary event if the attribute "CancelActivity" is changed. Changing the property "CancelActivity" in the properties bar for the boundary event should update the graphical semantics based on BPMN2 specifications; however, the graphical semantics remain the same.
1003815 - Designer fails to import a process with Data Object
Failure to import a process or importing the incorrect DataObject issues occurred while attempting to import a DataObject into Designer. This DataObject feature has been disabled since the user will not lose any functionality as they can specify process variables in a non-visual way using properties.
1002168 - Importing a BPMN2 definition without attribute "drools:packageName" has different effect than importing a BPMN2 definition with incorrect package
The property "Package" while importing BPMN2 definitions experiences different results. If importing a definition which does not contain attribute drools:packageName, then the property "Package" is not changed. If importing a definition which contains an incorrect package, then the property "Package" is changed to PROJECTNAME.src.main,resources.PACKAGE. The property "Package" should not be able to change in both instances.
994225 - jBPM Designer generates error boundary event as non-interrupting
By default, Designer generates an error boundary event as non-interrupting. However, this type of event should always be interrupting and the user should not be given an option to change this behavior. To work around this issue, save and reopen the process definition to enable Designer to calculate the boundary events.
982981 - The task, which is connecting to subprocess but does not lie inside the subprocess task, is not attached to BPMN2 code of subprocess
While working with BPMN2 Processes, the position of the mouseUp event determines if a task is in the subprocess. However, the task's position in the subprocess should depend on the incoming sequence flow, not on the position of the mouseUp event. If the source of incoming sequence flow is in the subprocess, then the task which was moved should be part of the subprocess. For now, the node has to be dropped or moved into the subprocess fully in order to be considered a part of it.
982776 - Task owner in Swimlanes in JBoss web-designer
Currently in Designer, names assigned to swimlanes are depicted as nothing more than display names. A current proposal is for swimlanes to have an actual group function associated with them. That is, all the human tasks that are dropped into that swimlane should automatically be associated with that swimlane group. With this function, the user would have the option to move the human task from one swimlane to another.
979927 - Invalid XSD definition of BPSIM standard
BRMS and BPM Suite distribution uses jbpm-bpmn2-emfextmodel/src/main/resources/model/bpsim.xsd, which has been changed. The original specification uses type xs:QName for attribute elementRef but specification in the product uses type xs:ID for attribute elementRef. This causes validation of the BPMN2 definition with bpsim.xsd to fail. However, validation of BPMN2 definition with the original bpsim.xsd is a success.
976486 - Operation "Undo" does not cooperate with workflow patterns
While using the Undo functionality in Designer, users are unable to remove work flow patterns from the process, even if the Undo operation reaches an empty process. There is currently no workaround to this issue using the Undo function.
969324 - None Task contains some properties in Properties Bar which has no effect to BPMN2 code
Within Designer, the element None Task is the default type of tasks but it is not supported by runtime or simulation. The None Task contains all properties for all task types, but these properties do not transfer into BPMN2 code. A current workaround is for the user to select a particular element type if they want to use various properties in runtime.
969300 - Quick Shape Menu is not updated
Designer presents two options for how a user can change a task's type. The first one uses the properties bar and the second one uses Quick Shape Menu. If a user activates Quick Shape Menu and changes the property through the properties bar, then the selection in Quick Shape Menu is not updated. If a user changes task type through Quick Shape Menu, then "Task type" property in the properties bar is changed immediately. A workaround to this issue is to show the properties for the process and select the element again.
955366 - Decrease canvas size button is never shown up
In a Designer canvas window, if the user has a process open, the buttons to decrease the size of the canvas in the top and left sides of the screen never show up. The buttons to decrease the size of the canvas in the bottom and right sides do show up.
1007879 - Simulation charts cannot be seen on display with lower resolution because Simulation info panel overlaps it
Within Designer, the "Simulation Info" panel has a fixed size and it cannot be hidden. On screens with a lower resolution, the chart panel can hardly be seen. A quick workaround to this issue is to close the "Properties" and "Object library" panels as they are not typically needed when working with simulation.
1049444 - IE: Wrong Process name if you create second process
While running Designer in IE, the user must clear their cache from their previous instance or all processes will display the same process name. A simple clearing of the browser's cache fixes the process name inconsistency.
Report a bug

Appendix A. Revision History

Revision History
Revision 1.0.0-9Mon Jun 30 2014Vikram Goyal
Built from Content Specification: 22687, Revision: 674465 by vigoyal

Legal Notice

Copyright © 2014 Red Hat, Inc.
This document is licensed by Red Hat under the Creative Commons Attribution-ShareAlike 3.0 Unported License. If you distribute this document, or a modified version of it, you must provide attribution to Red Hat, Inc. and provide a link to the original. If the document is modified, all Red Hat trademarks must be removed.
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, 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 Software Collections 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.