We will now use debug facilities of the RulesComposer to analyze the flow of the generation:

The debug hierarchy shows up in an editor. A debug hierarchy is a tree of nodes, each node representing an evaluated element (template, rule or script):

We will now find the script that generated a part of the file Order.java:

The debug hierarchy focus is moved to the node main\JavaSource\declaration\declaration.
This is the script defined on rhapsody.Argument whose evaluation produced the text
"RhpString productName".
The debug hierarchy is very useful in two situations:
Next Section: Include a Javadoc template
Prev Section: Add operation body