The decision engine is designed to offer better performance results but does not yet support some of the features of the classic rule engine.
The following tables show the features that are not supported in this release with the decision engine.
| Feature | Limitation |
|---|---|
| Testing | You cannot use Decision Validation Services with the decision engine. When you try to use the DVS feature on rulesets that are built with the decision engine, you get an incompatibility message. |
| Rule analysis | You cannot run an analysis of the rules on a rule project that is built with the decision engine. |
| Custom business rule language | You cannot define a custom business rule language
and translate custom business rules into IRL. The samples that are related to the customization of the rule language do not run with the decision engine. |
| Scorecard Modeler | Scorecard Modeler is not supported in rule projects that are built with the decision engine. |
| SCA archive generation | You cannot add decision engine archives when you generate an SCA archive for Rational Application Developer. |
| Feature | Limitation |
|---|---|
| Testing, simulation | You cannot use Decision Validation Services with the decision engine. |
| Rule analysis | In Decision Center, the option to check the ruleset archive at generation time is disabled. However, you can generate a rule analysis report to check the consistency of your rules. |
| Feature | Limitation |
|---|---|
| Event runtime | You cannot emit business events from a ruleset that is built with the decision engine. Conversely, you cannot invoke a decision engine ruleset by using the business rule data connection from the event runtime. |
| Business Rules Embedded | The APIs of Business Rules Embedded are not supported when you use rulesets that are built with the decision engine. |
| JSR-94 | The JSR-94 implementation is not supported when using rulesets that are built with the decision engine. |