Chapter 3. Known issues

General

Deployment on Red Hat JBoss Fuse Service Works 6.0.0 and Red Hat JBoss Data Virtualization 6.0.0 fails.

Trying to deploy Red Hat JBoss BRMS 6.0.0 on either Red Hat JBoss Fuse Service Works (FSW) 6.0.0 or Red Hat JBoss Data Virtualization (DV) platforms will fail and therefore installation on those platforms is not currently supported.

Business Rules Engine

1051585 - Kie-spring cannot create KieModule in container on Windows.

When trying to deploy a Maven project with a WAR file on EAP6 in a Windows environment (2012 Server and Windows 8.1), the kie-spring throws a NullPointerException when trying to load KieModule. The deployment doesn't seem to raise any errors, but the server log shows the error and the WAR file is not actually deployed.

1047911 - DecisionTableConfigurationImpl throws NPE in toProperties().

User is unable to programmatically configure DecisionTableInputType of a Decision Table resource while not configuring a non-null worksheetName.

Business Central

1042512 - Guided Editor - DSL values used in consequence not editable after save.

When using the Guided Rule Editor, a Domain Specific Language (DSL) enum value used in a consequence rule does not persist when saved. The only known workaround for this at the moment is to delete the DSL and recreate it.

1051105 - Auto deployment to runtime engine fails with non-default user defined kbase and ksession.

A BRMS project that contains a user defined kbase and ksession will fail auto deployment to the runtime engine unless these are marked as default. This is expected behavior and is not likely to be changed in the future. The runtime engine expects kbase and ksession names in order to be deployed but these are not available for user defined artifacts.

1052313 - Restrictions on Number that is result of 'accumulate' CE are not shown in GRE when the rule is reopened.

When a Guided Rule file containing restrictions on the result of accumulate conditional element is opened in a Guided Rule editor, these restrictions are not displayed. This is caused by the Guided Rule editor not being able to recognize certain rule language features.

To workaround this issue change the Guided Rule type to DRL by changing its file extension from 'rdrl' to 'drl'. The rule will open in text editor which displays the rule source correctly. You should change the file name extension outside Business Central, using GIT.

1007894 - Not much friendly maven error message appears when there is some problem with project.

A simple error with a Project (for example, missing dependencies) can cause an unfriendly Maven error message being provided to the user, with no details of the actual error.

1011482 - REST API: Inconsistent response type for error message on IBM JDK.

When deploying projects via the REST API on BRMS/BPM Suite running on IBM JDK, any actions that cause an exception to occur will trigger the REST responses to be received in an invalid XML format. Error messages should be instead received in the JSON format.

1039916 - Editor for project.imports file is incomplete, Restore button saves instead of restoring.

While importing external classes and making them available for assets in projects using the projects.import file, there is no way to save or restore the state of this file as the button for restore or save is missing. To work around this issue, the Project Editor should be used instead.

1034734 - Guvnor asks to save possible changes on each 'Build & Deploy' even though nothing was changed.

Everytime 'Build & Deploy' is pressed in Business Central, the system prompts the user to save changes even though nothing has been changed since the last time changes were saved. There are no workarounds at this stage.

1021406 - Unnecessary commits are made when a Project is saved.

Unnecessary commits are made in the underlying GIT repo each time pom.xml is saved, that is, when the user clicks File->Save in the Project Explorer screen. This causes several messages in the GIT log to appear which are not required but also causes system degradation.

1009385 - Invalid Guided Rule reopens with a different definition.

If you close and save the Guided Rule Editor with an unfinished or invalid change, you will not be able to work on the incomplete rule when you reopen it because the Guided Rule Editor opens the rule with a different definition.

1048950 - Invalid Enumeration not detected.

The Enum Editor fails to detect invalid enumeration and marks them as valid. The Guided Rule Editor then fails to open due to the invalid enumeration entered via the Enum Editor.

1012553 - GRE doesn't handle multirestrictions when reopening rule.

If you save a Guided Rule with multiple restrictions on a single fact field, it is not possible to reopen the rule. The user is presented with an error message. This affects all kinds of operators (==, <, <==, etc.), contains, excludes, matches, soundslike etc.

1011548 - M2 Repo: artifact version from property causes badly named artifact.

Uploading a Maven project jar with the version defined by a property results in a malformed artifact name and wrong artifact version.

1052939 - GDT Audit log: admin is not everything.

A user with 'admin' role cannot delete log entries in Guided Decision Table (GDT) Audit log, though users with role 'analyst' or 'developer' can. This is because a user with the 'admin' role is not shown the 'trash icon' button for deleting log entries. A user with the 'admin' role should have universal access and therefore this button should be available. There are no workaround available at the moment.

1048962 - GRE: input for field used with dependent enumeration not updated.

Value fields using dependent enumerations for constraints in a Guided Rule are not updated when the user switches the value it depends on. The only workaround at this point is to remove the last input element of the problematic constraint and re-add it, after switching the value depended upon.

1045117 - Creating a project floods git with 22 uncommented commits.

When a new project is created and new files are added along with some content, it results in 22 commits to the underlying GIT repo, each without a comment. This causes the GIT repo to be messy and harder to work with.

1052269 - Guided rule editor: rule with incomplete String constraint reopens with different definition and elements missing.

While creating a rule in the GRE, if you leave a constraint element on a String field incomplete, save and reopen, the definition for this element will change and all conditions elements that were below it will disappear.

996480 - Moving hidden columns in Guided Decision Table visually corrupts the table.

It is possible to change the order of columns in a Guided DT. If you do that while a column is hidden, a ghost column appears in the data part of the editor. The effect is only visual.

996485 - Guided Decision Table: until you add a row, only one column is visible.

When creating the Guided Decision Table and before you add any rows, only the first (as ordered in the table) column added is visible. All columns appear after you add a row.

1051552 - Rule template which modifies facts on RHS is invalid and fails project build.

A project will fail to build if a fact field in the 'THEN' section of the Guided Rule Template is modified. The template file itself will fail to load once saved or closed.

1059166 - Guided rule editor fails to open a valid rule.

The Guided Rule Editor fails to open a valid rule correctly even though the rule has passed validation and is valid in the GIT repository. The Editor may incorrectly remove some of the rule definitions or modify rule constructs incorrectly.

1036759 - Guided decision table cannot be created without clicking on a package in a project explorer first.

Trying to open Guided Decision Table editor for creating a new GDT causes a white screen without any obvious errors or messages. To workaround this issue, close the editor and open it again (three times). ONce the editor has opened successfully, this error does not happen again.

Eclipse Tooling

1048717 - Opening audit log from BRMS5 throws internal error.

Trying to open audit logs generated by BRMS 5 runtime does not work in BRMS 6. There are no visible errors or messages. This issue is caused by renaming of packages in BRMS 6 which causes several ClassCastException errors. there are no workarounds at this stage.

1029040 - Content assist does not offer types declared in DRL file.

The Guided Rule editor does not offer fact types declared in DRL to the user and the user is unable to use content assit for these declared types. The only workaround at this stage is to use fact types declared as POJOs.

1051541 - Split log files can't be loaded into Audit view.

When you try to open an audit log that has been automatically split by the Rules engine, the Audit view will not open it. This issue happens intermittently and is likely caused by before and after events being in separate files. The workaround at this time is to use a single file audit log.

Migration Tool

1052886 - jcr2vfs: test scenario migration ends with XML parsing exception.

Trying to use the migartion tool to migrate a test scenario from a JCR repo fails on JDK7. Use JDK6 to workaround this issue.

1059441 - jcr2vfs migration tool generates incorrect WorkItemDefinitions.

The jcr2vfs migration tool generates workitemdefinition files with invalid import statements. The import statements refer to package names that are not valid and therefore the resultant files cannnot be used.

1059478 - jcr2Vfs migration tool does not correctly transform tech and biz rules.

Trying to migrate a BRMS5 rule into BRMS6 using the migration tool causes an error due to incorrect scanning of the rdrl file. This creates an invalid file for import which fails compilation in BRMS6. The issue is seen on rules from BRMS5 which contain an import statement.