Welcome to the Jazz Community Forum
No artifact export in RRC 3.0 Beta 2?

I need to export a text artifact to Word format. I know this feature existed in RRC 2.0. Has it just not been implemented in the beta yet, or am I not looking in the right place? Exporting from the list view just creates a CSV file of the artifact info. There doesn't appear to be a way to export the content.
Thanks,
Brett King
Thanks,
Brett King
3 answers

I believe the simple "export to word" was not enabled in RRC Beta 2a (December 2010) though I haven't checked myself. In this beta release I count four ways to get a text artifact out of RRC, in approximate order of effort required:
1. Open the artifact and print the page using File / Print in your browser; use a PDF printer driver.
2. Copy the text to the clipboard and paste it into word. It's html text. Note that the html may be slightly different depending whether the artifact is in edit or read-only mode.
3. Export to CSV when your view includes the "primary text" field (which is the main content of the requirement). There are limits to the amount of data and text formatting included in CSV files.
4. Use a Rational Publishing Engine document template to generate a doc in Word / PDF / html / XSL-FO. as described in the Beta 2a blog post and new & noteworthy for Beta 2a.
** this post was edited to fix a couple of spelling mistakes
1. Open the artifact and print the page using File / Print in your browser; use a PDF printer driver.
2. Copy the text to the clipboard and paste it into word. It's html text. Note that the html may be slightly different depending whether the artifact is in edit or read-only mode.
3. Export to CSV when your view includes the "primary text" field (which is the main content of the requirement). There are limits to the amount of data and text formatting included in CSV files.
4. Use a Rational Publishing Engine document template to generate a doc in Word / PDF / html / XSL-FO. as described in the Beta 2a blog post and new & noteworthy for Beta 2a.
** this post was edited to fix a couple of spelling mistakes

We are having a similar issue (though in v2.0.0.4), where we want to export our requirements to CSV, but when we do, we just get a list of the Req Names and not the "Primary Text" as you said here:
"3. Export to CSV when your view includes the "primary text" field (which is the main content of the requirement). There are limits to the amount of data and text formatting included in CSV files. "
From what I can see (V.2.0.0.4), there is no option to add "Primary Text" or anything similar to the table view of our requirement list and no way to export a batch of requirements with the text of the requirement to a CSV file.
"3. Export to CSV when your view includes the "primary text" field (which is the main content of the requirement). There are limits to the amount of data and text formatting included in CSV files. "
From what I can see (V.2.0.0.4), there is no option to add "Primary Text" or anything similar to the table view of our requirement list and no way to export a batch of requirements with the text of the requirement to a CSV file.

From what I can see (V.2.0.0.4), there is no option to add "Primary Text" or anything similar to the table view of our requirement list and no way to export a batch of requirements with the text of the requirement to a CSV file.
I believe you are correct. For RRC V2 I imagine you could create your own CSV file by using the Rational Publishing Engine to create a corresponding report template. The main challenge might be figuring out how in RPE to escape quotation marks as specified in RFC 4180.
As you mentioned, there are significant improvements in the CSV export (and import) in V3.