how to mark requirement artifact suspicious using oslc api or javascript in DNG
Hi All,
The requirement is I have to mark Requirement artifact suspicious based on change in RTC source control link.
I have added rtc source control link in requirement artifact using "Implemented by" link(Using oslc api added this link).
I also have created plugin in RTC which will be triggered on delivery of some XML file. Now from the plugin source code I am trying to update requirement artifact linked to this source control link. I am getting requirement artifact but issue is I am not able to mark this artifact as suspicious.
Could you please let me know how to mark artifact suspicious using OSLC or any other way?
Thank you in advance
2 answers
I believe the enhancement you are looking for is: enable jazz SCM to allow creating links to SCM items in a global configuration context and contributing to the validity service (370719)
In particular, the "validity service" is what provides suspicion support for versioned artifacts.
This is currently under consideration for the next release of RTC (6.0.3), so now would be an appropriate time to vote it up if you are interested in this functionality, or add a comment.
In particular, the "validity service" is what provides suspicion support for versioned artifacts.
This is currently under consideration for the next release of RTC (6.0.3), so now would be an appropriate time to vote it up if you are interested in this functionality, or add a comment.
How do you create a implemented by link pointing to a source control item (ie program code)?
Unless I am missing something, requirement artifacts can link to different flavors of work items (change request, defects etc) and trigger suspicion based on changes on those.
So showing how your suspicion profile is setup would help here, specifically how you did the source control linking...
Unless I am missing something, requirement artifacts can link to different flavors of work items (change request, defects etc) and trigger suspicion based on changes on those.
So showing how your suspicion profile is setup would help here, specifically how you did the source control linking...
Comments
Hi Bas,
Thank you for quick response
Using OSLC I have created that link. I have used "Implemented By" link to point to source control.(Through GUI its not possible to link Source control link as implemented by"). I have used this link for POC purpose. The main intention is to show requirement is suspicious on change in source control item after adding to DNG
Basically the question is how to mark requirement artifact suspicious programmatically using oslc or javascript.
Is there any way to show Requirement artifact suspicious programmatically?
About a public API for DNG, there are three API's:
- RRC Reportable API - for reporting purposes, only reading artifacts
- OSLC RM V2 API - the open standard way to programmaticaly integrate with DOORS NG, there is an elaborate workshop to get you started here OSLC Workshop article
- and additionally, there is the so called client extension capability
Not sure about the Javascript client extensions, you can check that yourself
And no, you cannot create a suspicion between an DNG artifact and an RTC source control item. Just check the UI to create a suspicion profile, it just doesn't let you choose a source control item.