Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

Retrieving all attributes within a module via RM.Data.getContentsAttributes client extension API

Questions
Tags
Users
Badges
Joshua Baxter
(91●11●18●26) edited
Jan 21, 8:13 p.m.

I've been experimenting with using the RM.Data.getContentsAttributes Client API in DNG 7.0.3 by doing the following:

  1. Open up a module on a stream (let's call this stream 1)
  2. Get an RM.ArtifactRef object for the module via subscribing to the ARTIFACT_OPENED event.
  3. Call  RM.Data.getContentsAttributes Client API to get attributes for all of the artifacts in the RM.ArtifactRef object obtained from step 2. This should be pulling all artifacts for the module in stream 1.
  4. Switch to another stream (let's call this stream 2) via the context switcher in DOORS NEXT which causes the module to be opened in stream 2. I'm not waiting for the Client API call in step 3 to return results before switching to another stream.
  5. Get a new RM.ArtifactRef object for the module via subscribing to the ARTIFACT_OPENED event.
  6. Call  RM.Data.getContentsAttributes Client API to get attributes for all of the artifacts in the RM.ArtifactRef object obtained from step 5. This should be pulling all artifacts for the module in stream 2.

I've tested the following a few times and it appears that it is pulling the artifact data for the appropriate stream that is switched to, but is the above steps I'm doing safe, or could it potentially lead to erratic behavior? And if it is safe in DNG 7.0.3, I'm assuming that it would be safe to do in DNG 7.0.2 as well?

0 votes

Comments
Ralph Schoon
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER Jan 22, 3:42 a.m.

Consider consulting.

I would consider to wait for switching of a stream to complete before expecting to get artifacts from the new active stream.

As already suggested test your stuff with the lowest version. Public documentation should mention changes to the API for higher versions. e.g. if it works for 7.0.2 it should work for 7.0.3 unless documented otherwise. 

0 answers
88 views
0 votes

Be the first one to answer this question!

Register or log in 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.

Ask a question
Guidelines
FAQ
Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details
× 10,953

Question asked: Jan 21, 8:10 p.m.

Question was seen: 88 times

Last updated: Jan 22, 3:42 a.m.

Confirmation Cancel Confirm