It's all about the answers!

Ask a question

[closed] How to add section in JRS


KT PD (59310) | asked Aug 01 '23, 8:45 a.m.
closed Aug 03 '23, 4:58 a.m. by David Honey (1.8k17)

 Hi team,


I am using DNG 7.0.2 SR1. We have requirements created in DNG and those are having "section" column in display in DNG.
We need to create JRS report for DNG project area and we need to add section attribute.
We are not able to get that attribute directly to add into the JRS report.
Do we have any other attribute instead? 

Thanks

The question has been closed for the following reason: "The question is answered, right answer was accepted" by davidhoney Aug 03 '23, 4:58 a.m.

Accepted answer


permanent link
Ian Barnard (2.3k613) | answered Aug 02 '23, 5:26 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
edited Aug 02 '23, 5:27 a.m.

 DOORS Next doesn't provide the section property to LQE, so it can't be reported in RS. Not sure why but probably because it would change on all artifacts in the module as module structure is edited, causing very high update rate to LQE.

David Honey selected this answer as the correct answer

Comments
Ian Barnard commented Aug 02 '23, 12:26 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

You can get section through the Reportable REST API - e.g. using RPE.


KT PD commented Aug 03 '23, 6:17 a.m.

Hi team,


I have checked by hitting OSLC API for particular requirement , but in GET method still I am not able to  get "Section" attribute data.
Methos: GET
Headers: OSLC-Core-Version:2.0
Accept: application/rdf+xml

Thanks,
Ketaki 


Ian Barnard commented Aug 03 '23, 8:37 a.m. | edited Aug 03 '23, 8:37 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

AFAIK section isn't exposed in the OSLC API you're trying. Bear in mind a core artifact can be reused in a module more than once so doesn't have a single section value; each reuse has its own section value and it's own resource URI.


However I'm pretty sure it is shown in the Reportable REST API when you ask for information from a module (which is the only context where section makes any sense)

One other answer



permanent link
David Honey (1.8k17) | answered Aug 01 '23, 1:25 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
edited Aug 01 '23, 1:26 p.m.
Insufficient information provided in your question to answer.

What do you mean by "section attribute".
Is this a custom artifact attribute (see Manage Component Properties or Manage Project Properties)?

The attributes of requirements seen in JRS for the Lifecycle Query Engine or Lifecycle Query Engine scoped to a configuration data source is almost entirely driven by the resource shapes that DN publishes in its TRS. So if you are writing a report against those data sources, then the attributes you can include or add conditions for is determined by those resource shapes. If you are writing a report against the Data Warehouse data provider, the tables are fixed and will not include custom properties you have added to the DN type system. Your question provides no details of which data source you are trying to use for reporting.

Comments
KT PD commented Aug 02 '23, 2:43 a.m. | edited Aug 02 '23, 2:44 a.m.

 Hi,


Thanks for the reply.
We are trying option "LQE by configuration" as this is GC enabled project area. We are able to display sections in DNG but when trying to add in JRS it is not showing.
Please find below image 

Thanks 


David Honey commented Aug 02 '23, 4:36 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

Please show a screenshot of the Artifact Attribute in the DN type system that corresponds to this "section" property. If there is no such Artifact Attribute then it's unlikely this is represented in in the OSLC Resource Shapes that DN publishes to its TRS (Tracked Resource Set) and hence Report Builder will not know about it.

I suggest you use Postman/RESTed (or other browser REST plugin) to get the RDF of a requirement that has such sections. You can copy the URI of the requirement from the DN UI as an OSLC link. When performing a GET, remember to specify the configuration context, and include a Oslc-Core-Version: 2.0 header. The first question is whether than RDF includes any representation of "section". The RDF of that requirement should include oslc:instanceShape and then you look at the RDF of that resource shape to see what properties DN is publishing in it.