How to remove/delete requirements in Doors 9.5.1.2 using OSLC?

Hi, I am looking the guide for RDNG
https://jazz.net/forum/questions/180675/how-to-update-dng-module-using-oslc
but I can not find a way to remove requirements? Also I saw that there is adding/remove artifacts from collection.

  1. So what I have to do when I have a requirement which is part of multiple formal modules how to remove it from all of them?
  2. How to delete requirement which is no part of any module/collection?
  3. How to purge the deleted requirement?
  4. How to remove file embeded as OLE/ attached in Doors ?
  5. How to purge requirements after deletion? Is it needed?

Is there OSLC way or I have to use the DXL extensions?


Dinio - Tue Dec 01 05:54:48 EST 2015

Re: How to remove/delete requirements in Doors 9.5.1.2 using OSLC?
SudarshanRao - Tue Dec 01 10:21:24 EST 2015

Hi Dinio.. So we talk again here :)

Some questions are relevant only for RDNG, not DOORS. For example, the first 2 questions. In DOORS you cannot use same requirement (object, as it is called in DOORS) in multiple modules. Each object is tied to just one module. As far as delete is concerned, if you need to do it via OSLC, I think you can do a Delete operation on the resource (I've not tried it personally, but I think it should work).

About 3, as I mentioned in jazz.net forum, you'll need to create a DXL Service, if you need to purge via OSLC client (see OSLC DXL Services for Rational DOORS section in Help). It depends on from where and how the user should be able to purge. If it is within DOORS UI, you can as well create a DXL script, which is much more easier. Even if it is not within DOORS UI, you can still use DXL via automation client support. For more info, refer to Extending Rational DOORS via DXL section.

About 4, using DXL, yes, you can just remove OLEs in an object. Without it, I don't think it is possible.
About 5, Whether it is required to purge a deleted object is user's choice.

So, depending on what your objective is, you may want to consider using a mixed approach - OSLC and DXL.

Btw, any question around DXL, do post it in the DXL related forum - that's usually the most active amongst the three forums related to DOORS. :)

Cheers,
Sudarshan

Re: How to remove/delete requirements in Doors 9.5.1.2 using OSLC?
Dinio - Tue Dec 01 10:48:33 EST 2015

SudarshanRao - Tue Dec 01 10:21:24 EST 2015

Hi Dinio.. So we talk again here :)

Some questions are relevant only for RDNG, not DOORS. For example, the first 2 questions. In DOORS you cannot use same requirement (object, as it is called in DOORS) in multiple modules. Each object is tied to just one module. As far as delete is concerned, if you need to do it via OSLC, I think you can do a Delete operation on the resource (I've not tried it personally, but I think it should work).

About 3, as I mentioned in jazz.net forum, you'll need to create a DXL Service, if you need to purge via OSLC client (see OSLC DXL Services for Rational DOORS section in Help). It depends on from where and how the user should be able to purge. If it is within DOORS UI, you can as well create a DXL script, which is much more easier. Even if it is not within DOORS UI, you can still use DXL via automation client support. For more info, refer to Extending Rational DOORS via DXL section.

About 4, using DXL, yes, you can just remove OLEs in an object. Without it, I don't think it is possible.
About 5, Whether it is required to purge a deleted object is user's choice.

So, depending on what your objective is, you may want to consider using a mixed approach - OSLC and DXL.

Btw, any question around DXL, do post it in the DXL related forum - that's usually the most active amongst the three forums related to DOORS. :)

Cheers,
Sudarshan

Hi, Sudarshan. Sorry for the first   2 questions I forget to remove them.

To clarify, users in my case can not see the UI, they use another system to make the operations over the Doors 9.5.1.2.

For 3 I still do not understand, user can use delete/purge on objects? Am I right? Delete can be done via DELETE request to the URI of the requirement and it is irreversible? So why purge is needed? Is only through DXL is possible soft and hard deletion?

I think I do not understand something, I was thought that some user delete a requirement and this object is not visible any more, but it is hidden in DB and only the user with appropriate permissions can make purge of these objects. But from