Sorry, that is a strange description, but here is what I'm doing and here is what I see. If I create a content rule - for the purposes of filling in some default/required RM property/metadata fields - on an RM site, a strange (GUID) folder is created/shown in the Share documentlibrary Navigation Tree (left-hand pane). This happens when the Content Rule is created and is not even run on anything. See below for what it looks like. This makes browsing to that folder problematic, and does not display any RM documents (or anything) below that. It also makes impossible to "move" RM content from 1 structure to another. Happy to post any tomcat error messages if that would help.
This only happens when the content rule is placed at the Series or Category level. If you create the content rule to apply at the folder level, this does not occur.
