Within RM/DNG text based artifacts, we frequently insert requirements into the rich text and link the inserted requirement.  This provides a nice way to organize a set of requirements and supporting text.  When we want to generate deliverable documents including these artifacts, we have relied on RPE using the reportable REST API to extract the requirement text and as of RM 5.0.2 and RPE 1.2.1.1 the inserted requirements showed up with links in the generated Word document.

I have been testing our upgrade to RM 6.0.2 and I discovered that the RPE template that worked fine with 5.0.2 does not include the inserted requirement in 6.0.2.  I even took the REST URI and pasted it in a browser connected to both our 5.0.2 system and the upgraded 6.0.2 test system and found that the inserted requirement is just not returned in 6.0.2. 

Does anyone know what change is needed in the URI to make this continue to work in 6.0.2?  Below is an example URI:  https://<server>:9443/rm/publish/text?resourceURI=_1ZQHkmgfEeO1O9hMYtpYTw .  This is a link to a "Documentation" type object with Format of "Text".   It has a couple of tables with inserted requirements.  The results include the inserted requirements from the 5.0.2 server but the table cells are empty for the 6.0.2 server.

We have not enabled Configuration Management in the project area for 6.0.2 although some basic features do appear (context shows up and offers a basic stream that coincides with the original creation date of the project area - several years ago...).

Thank you,
Jamie.