© Copyright International Business Machines Corporation 2006. All rights reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
This release notes file contains late-breaking information about limitations and known problems and workarounds for the WebSphereR Integration Developer business rule group editor and the business rule set editor.
If a rule group is moved from one module to another, the brg and brgt files are both moved. However, the rule sets and tables referenced from the rule group are not moved. This will result in red x's on both the rule group and the rule sets or tables.
To resolve this problem, move the rule sets and tables into the same module as the rule group.
If you create a new rule group, selector, decision table, or rule set with a '-' character in the filename, code generation will fail.
To avoid this problem, do not use the '-' character in a file name for these file types.
In the selector or rule group editor, xpath can be used to specify the selection parameter. This readme entry applies to users who use this option.
The initial value of the xpath data contains hint text. If you click the hint text, you can replace it with a valid xpath. However, if you append one character to the hint text and save, you might not be able to reload the file. A special character, "<", is stored in the file which prevents reloading.
To work around this problem, open the file in a text editor and set the xpath string to "".
The expression validator will report an error on expressions that try to compare two strings (bo.a == bo.b) if "bo.b" is a restricted (for example, enumeration) string.
The workaround is to invert the expression (bo.b == bo.a). This problem will happen in the rule set, decision table, and activity editors.