What's New in the Rules Composer

This page gives you an overview of the new features and UI changes in the rules composer for this release.

In the Project Explorer view, you should see the Project Resources node instead of the Aliases node.
In the Project Explorer view, when you expand the ruleset or flow ruleset, you should see the if-then rules and decision tables in the respective folders.
In the Outline view, you should see a single icon that displays options to add if-then rules and decision tables.
In the Outline view, you should see new icons to sort rules and decision tables in the descending order and based on the rule priority.
In the Project Resources editor, you can add, reload and remove XSD elements and Java classes in a single editor called the aliases editor.

The list of new features in the rules composer are as follows:

In the text editors, you should see context menus. For example here is a snapshot of the rule editor:
The Preferences screen has options to:
- Set preferences for aliases and text editors
- Specify location for ruleset and test reports
- Configure smart aliases
You should see options such as Show References, Replace References and Rename Alias in the context menu of any alias or definition in any text editor across the DC.
Your rules get validated automatically and you should see the messages in the Problems view.
You now have trace configuration for rules composer.
1. In SAP NetWeaver Developer Studio, choose Window Preferences .
2. In the dialog box that appears, in the left hand side, choose Trace Configuration.
3. In the screen that appears, expand the All Locations node and you should see the Rules Composer node.
JDK 1.5 Support : You can write rules using JDK 1.5 generic features.
Example
You should be able to create following type of definitions:
- List <String> names = null
- List <String> names = newArrayList()<String>
- List<String> names = Class.getStudentNames() (Here return of this method should be List<String>)
- Java.util.Map<String.Customer>customerIDHolder = newHashMap <StingCustomer>()
End of the example.
Copy and paste if-then rules, decision tables, rule scripts and rule flows across DCs.

In case of XSDs , aliases or XPaths can be created for the subtypes also. This will allow you to work with hierarchical XSD models .

Example Example

Here is a sample XML schema which contains an abstract type and two concrete subtypes

This graphic is explained in the accompanying text.

Aliases that can be created for subtypes: <”PersonalVehicle"> and <”CompanyVehicle"> are:

End of the example.