DOORS NG OSLC API Question
Hi,
I writing a widget that identifies test steps which are linked to deleted requirements.
When getting the Validated By link in ETM, I often see links to requirements with URLs like:
rm/resources/MB_xxx
When I paste the URL into a browser, the requirement comes up fine after a redirect to a location like:
/rm/resources/BI_xxx
I have a second DOORS API call that gets ALL requirements, and it gets me all the BI_ (and other) artifacts, but there are zero MB_ artifacts returned from DOORS. Thus, I can't tell if the MB links are broken or not.
Do you have any suggestions on fixing my approach? How can I get a list of all available requirement urls (including the MB_ ones)?
Thanks!
Accepted answer
The MB_/BI_ is an internal implementation detail, one that has changed from 6.x to 7.x - so I guess these bindings were upgraded from 6.x because the URL of bindings (which could have MB_ or no prefix) doesn't change during the upgrade, where new bindings will all have BI_.
The OSLC APIs will have unchanged URLs for upgraded artifacts. If you're seeing a different URL for an upgraded artifact in an API result that's likely because you're using a private API where the 'no change for upgraded artifact URLs' rule isn't applied.
If you can navigate the links correctly then there's nothing wrong with them whatever the details of the URL, i.e. I'd say there's nothing about your approach to fix.