It's all about the answers!

Ask a question

RRC+RPE: How to get the URI of the base artifact when the artifact is included in a module

Dr. Markus A. Thies (321113) | asked Dec 13 '13, 10:28 a.m.
Modules contain other artifacts.
One artifact has one visible ID which is identical in both contexts: within a module and stand-alone.
The actual URI for both is different.

After studying all available documents I do not get any information on how the ReportableRESTAPI returns the information (URI) to the base artifact. It is not available in regular response.

How do one find during document generation with the RPE , the URI of the base artifact?
That is essentail, since some information related to the stand-alone artifact is not available within the result for an URI which is module based. See also my other post on requesting the information on links.

Thanks for any hints.

3 answers

permanent link
Jorge Flores (1092) | answered Feb 18 '14, 5:25 p.m.
Hi Markus,

This actually a defect, it will is included on the 5.0 version,   but if you need it for a previous release please submit an escalation, and we will provide you a patch.


permanent link
Don Yang (7.7k21110139) | answered Feb 19 '14, 4:43 a.m.
Using binding URI for module seems to work for most types of artifacts for RPE. We only found Use Case Diagrams and Storyboards do not work and need the base artifact UUID for RPE and in that case, as Jorge suggests, it is known defect or we can say it is a new feature in v5.0.

permanent link
Jorge Flores (1092) | answered Feb 19 '14, 10:24 a.m.

I also want to comment that even if the biding URI can be used to get artifact information for most types of artifacts I would recommend to request the fix since those are binding artifacts, the information is limited even when the request is correctly returned.

The biding artifacts are expected to be used as wrappers, so they do not contain all the artifact information.


Don Yang commented Feb 19 '14, 4:22 p.m.

That's good points. Thanks Jorge. I have an end user who has the same problem and I am waiting for feedback from them if they would wait for v5.0 or need a fix for 4.0.5 they are using. If required, I would submit a hotfix request.

Don Yang commented Feb 19 '14, 6:59 p.m.

I have submitted hotfix request for v4.0.5 in workitem 304026. Please review and help. thanks

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.