It's all about the answers!

Ask a question

How to extract a json / xml with the requirements of a project in DNG?

Pablo de Llanos (111) | asked Mar 15 '23, 9:42 a.m.


At my company we are developing some extensions in DOORS Next Generation for a set of projects, and we would like to know how to extract the requirements so we can create different charts and graphics based on the value of their attributes (id, status, etc..). We are hosting the extensions into an Azure server, so that it reads the ".xml" of each of extension and runs the corresponding ".js" files when it loads on the DNG widget.

Currently we are working with the Reportable API, but it is messy and slow whenever it loads the extension - this way extracts all the data from a given project and later we need to apply various filters to retrieve the useful data. Our problem is that we need to particularize this for every project, as each database may contain different attributes for each artifact.

We have looked deeply into the documentation and it seems to be a way of working with "RM" calls, but we have not found a solution to make that the extension recognizes the "" instructions, like the ones shown at the code of the example available at the following link (

We have also considered to retrieve data using OSLC queries as in this video ( but we still need to apply various filters to retrieve data, and therefore difficult to handle with.

Is there any other solution that would retrieve the data (for example, via SQL query) with the required filters of the attributes already applied? We have also looked at the json format link available when accessing at the Report Builder (which is designed to be coupled to IBM Engineering Lifecyle Optimization - Publisher), but the problem is that it does not update the register/report if new artifacts are created inside the requirements module.

All answers or past experiences related to this topic would be of much help. Thanks in advance.


2 answers

permanent link
Bhagath P B (3888) | answered Mar 16 '23, 2:45 a.m.

 Hi Pablo,

Please have a look at, which have example queries that you help retrieve artifacts that are in the view(also include views having filters)

permanent link
David Honey (1.8k17) | answered Mar 16 '23, 5:48 a.m.
edited Mar 16 '23, 5:49 a.m.

Pablo, you can find the ELM Landing page at That has links to a number of DN API pages. You should also read about OSLC - see and You can use OSLC discovery to find an OSLC Query Capability that you can use to find resources of interest.

Most public REST APIs are focussed around RDF (see not JSON. So if you want data from APIs, especially those that relate to OSLC capabilities, you should use RDF. There are no public SQL capabilities. The database schema is private, undocumented, and unsupported, and for internal use only.

So your only options are to use Reportable REST or OSLC related APIs.

Your answer

Register or to post your answer.

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.