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

Add new artifact attribute data type in DNG for specific PA using API

Hello All,

Could you please help me out in adding new artifact attribute data type in DNG for specific PA using REST/OSLC API.
E.g.: New enumeration value of artifact attribute data type to be added.

Please also let me know the reason whether it possible through OSLC API/REST API?

Also let me know the procedure.

Any help is greatly appreciated.

Thanks.

0 votes



10 answers

Permanent link
I don't think there are any APIs supported for this function. Setting up new types is usually a one time task. Is there any reason that you don't want to use the Web GUI and opt for the API?

0 votes


Permanent link
Hello Donald

Thanks a lot for your response. I wanted to check whether user can modify project properties.via API or not.

Is it possible to fetch and modify the data?

Thanks.

0 votes


Permanent link
Is it possible for REST API or OSLC API?

0 votes


Permanent link
If it is possible to modify the project propertied using REST Client, please let me know the steps.

0 votes


Permanent link
Hi Shriraam Balasubramanian
I would propose submitting an enhancement request for the API for 'useful' functions. Automating this kind of activity across multiple projects and modules is a must for larger companies - having to use the GUI would be a catastrophe.

0 votes


Permanent link
Hello Adrian,

Sure I will submit an enhancement request.

Also please let me know whether it is possible to fetch or modify DNG project properties for specific PA using REST Client????

I will also provide the consolidated APIs requested for some useful functions.

Thanks a lot.



0 votes


Permanent link
Hi Shriraam Balasubramanian

I don't have the answers - I am also searching for answers to similar questions as you.
I come from a DOORS9/DXL background - by comparison the DNG API is very basic.

IBM cannot possibly provide all end-user required functionality in a timely manner themselves - providing a more powerful API will enable end-users themselves to address this need. This was a good feature of DOORS 9 which has not yet been made available in DNG, leaving it a much less convincing tool option.

We are also compiling a list of needed API enhancements but looking at the turnaround time for enhancement requests it may take quite some time to get them implemented - all the more reason to concentrate on developing the API so end-users can take some of the development load.

0 votes


Permanent link
While DNG carries a name similar to DOORS, it is a different product and you need to change your mind set when switching to a new product.

After so many posts, a clear user case has not been identified, and you only kept asking for the API. Have you ever considered alternatives?

For example, if the purpose is to create projects based on a template, you can use a project template with all the customization built in.

0 votes


Permanent link
Hi Donald

Understood that you can create a new project from a project template but...

There seems to be an IBM assumption that 1 R&D project in an organization = 1 DOORS NG project and that changes during the project are none/minimal  - this is not necessarily a correct assumption.
  • In large organizations, one R&D project could easily be 30 workpackages each containing 30-40 modules, giving 900-1200 modules per R&D project in a typical scenario. There is no way in the world we will manage that under a single DNG project, especially when there is no longer a module baseline capability. This means our setup would best be split into 1 DNG project per workpackage/sub-project.
  • Our typical R&D project lifetime is 3-4 years with resources coming and going and constantly subject to the need to improve way-of-working efficiency. 
Given the above conditions, rolling out changes & efficiency improvements across projects and modules must be capable of automation - to maintain this manually per module per project is not practical - therefore the interest in the API.

0 votes

Comments

I have to read your post several times to understand the use case. Does it mean that you have multiple projects that will get the same new artifact type at some stage? If so, process configuration sharing may be a better solution than using API - in other words, all child projects inherit the process configuration from the parent project. RTC has had this feature for many years, but DNG really falls short in this area. I believe some users have already requested for this feature but I cannot locate the enhancement work item.


Permanent link
Hi Donald

(For some reason the IBM website is not letting me reply to your last comment, so I post my reply here separately.)

Thanks for your answer - your understanding of the use-case is correct.

The concept of inheritance is interesting but would need another feature we look for to be able to make it work -> a project must be able to contain other projects (hierarchy) as a pre-requisite for inheritance.
This would still only give us a partial solution though, as a  re-usable component will exist in a DNG project and that would be linked to multiple other 'higher-level' projects not under the same product hierarchy.
The best answer for us would be to enable cross-project copy/update.

0 votes

Your answer

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.

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,938
× 479
× 234
× 139
× 60

Question asked: Apr 05 '16, 10:26 a.m.

Question was seen: 5,588 times

Last updated: Apr 12 '16, 8:59 a.m.

Confirmation Cancel Confirm