Naming considerations
The default name for nested beans has changed. In previous versions, the child's display name concatenated to the parent's for the bean name of the child bean. Since the child is now a resource independent of the parent, the naming convention will no longer involve the parent and will be simply the child's display name.
When regenerating V4 resources with this new generation scheme, there may be an impact on rules or JSPs that rely on the bean name of the child. To simplify migration and to avoid changing any other code, you can open the wizard on that hrf and change the bean name on the finish page to what it was previously, before you regenerated the resource. This change only affects the default naming, so if you had previously assigned a bean name to the child on the finish page, that name is preserved.
Since the bean name has changed, after regenerating you may want to delete the old nested beans that are no longer referenced. As always, it is strongly recommended that you back up your java resource and .hrf files before regenerating using the new version.
Related concepts
Management of Nested Resources
Related tasks
Feedback