Export Newly Created Requirements Table Column for Reports

[jallen34@peraton.com]

Hello,

I am attempting to generate a requirements document using the "Requirements Report" template that exist in Report Wizard (simply made changes to fit company template). In order to show a "Rationale" column in the model's Requirement Table, I created a "Rationale" stereotype and made it a "string" type. This extra column allows me to nicely export my requirements into an Excel file. My issue is that now I want to put the Rationale information into a Word "Requirements Report" and I do not know how to grab that column the same way the template naturally grabs a "Verify Method" or "Derived" column.

What should I do to the Requirement Report template code in order for it to allow me the ability to pull information from newly created columns?

I have attached a few screenshots showing how my new column fits into my table and the specifications and location of my "Rationale" element.

I appreciate your time and please let me know if you require more information to resolve this issue.

~J.A.

[matt.systemize]

I may not be answering your exact question but this may get you what you need without any customization.

The Requirement Report displays Rationale when you anchor a <<Rationale>> element to a Requirement. Rationale already exists in the tool pallet.

See pics with reqs diagram and related existing report.

Thks

[sarawut_w]

Hello,

For getting stereotype property value, you would rather need $report.getStereotypePropertyString(element,stereotypeName,propertyName).
https://docs.nomagic.com/display/MD190SP4/Report+tool#Reporttool-$report.getStereotypePropertyString(element,stereotypeName,propertyName).

Code: Select all

#foreach($r in $Requirement)
Requirement: $r.id $r.name
Text: $r.text
Rationale: $report.getStereotypePropertyString($r, “Rationale”, “Rationale”)
#end


Best regards,
Sarawut W.
Support Engineer

[jallen34@peraton.com]

Thanks Sarawut!
The

Code: Select all

$report.getStereotypePropertyString($r, “Rationale”, “Rationale”)

line of code was exactly what I needed!

matt.systemize,
I appreciate your help as well. What you provided is very useful so I appreciate you taking the time to help. Currently, my team and I have been adding new columns (not just Rationale) to most of our model's tables. So, understanding how to generate reports that included all the data from our new columns was essential for my team's work and not just my personal Rationale work.

Have a great day and be safe!
J.A.