Questions about the deleteNode function and deleting documents using the web service

We are working on developing a web services call from one of our internal applications to delete images that had previously been stored in Content Server.

The behavior we are seeing in our environment is that the call to DeleteNode is removing the document, but the version information is remaining. A second call to DeleteNode with the same ID appears to remove it completely - which is what we are going for.

Is this the expected behavior for this process, or is there a better way to configure things where multiple calls are not required?

Find more posts tagged with

Comments

Nizar Ghazal

Hi John,

Is the delete perhaps sending the object to the RecycleBin?

That may explain why you need to double-tap delete to get rid of it, completely.

Thanks,

Nizar

Hans Stoop

I don’t know what you actually mean by that the version information is still there.

I would expect that your first call moves to document to the recycle bin and the second call removes it from the recycle bin.

Hans

On 1. Mar 2019, at 17:08, eLink Entry: Content Web Services Forum <otdncontentwebservices971forum@elinkkc.opentext.com> wrote:

eLink : Questions about the deleteNode function and deleting documents using the web service
Questions about the deleteNode function and deleting documents using the web service Posted by john.williams@bbva.com (Williams, John) On 03/01/2019 11:05 AM

We are working on developing a web services call from one of our internal applications to delete images that had previously been stored in Content Server. The behavior we are seeing in our environment is that the call to DeleteNode is removing the document, but the version information is remaining. A second call to DeleteNode with the same ID appears to remove it completely - which is what we are going for. Is this the expected behavior for this process, or is there a better way to configure things where multiple calls are not required?
[To post a comment, use the normal reply function]
Forum: Content Web Services Forum
Content Server: My Support

appuGmail

In versions like 10.5, the first delete for subtypes like Document ended up in a new volume called Recycle Bin(its a move internally). If you went to DTreeCore.Deleted for that DataID it would say 1 active=0

The second delete identified by the DataId would remove it completely. In Auditing, it would call Purge. In V16 the Move between volumes is not happening. They handle it differently.

If you do not want RecycleBin to get into your process you can say in its administration page documentsubtype=144 is not Recyclable in which case the single delete would suffice, but again

I would make sure your web services(soapserver) and the LL server its communicating has that setting.

Recycle bin and its cousin undelete can also be removed totally from old servers if you were doing huge deletes.I have done those as well.

Ciao,

..... appnair appunair( Livelink Rocks )

Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937

On Fri, Mar 1, 2019 at 10:08 AM eLink Entry: Content Web Services Forum <otdncontentwebservices971forum@elinkkc.opentext.com> wrote:

Questions about the deleteNode function and deleting documents using the web service Posted byjohn.williams@bbva.com (Williams, John)On 03/01/2019 11:05 AM

We are working on developing a web services call from one of our internal applications to delete images that had previously been stored in Content Server. The behavior we are seeing in our environment is that the call to DeleteNode is removing the document, but the version information is remaining. A second call to DeleteNode with the same ID appears to remove it completely - which is what we are going for. Is this the expected behavior for this process, or is there a better way to configure things where multiple calls are not required?
[To post a comment, use the normal reply function]
Forum: Content Web Services Forum
Content Server: My Support

John_Williams

It does look like these documents are in the deleted documents volume.

Is is possible to adjust settings for items in certain folders to not recycle?

Nizar Ghazal

Hi John,

I believe Recycle Bin does it per object type, and not location. So if you wanted to, all documents would be fully deleted, instead of recycle, and so on.

You could probably log a feature request, perhaps?

If you need to do particular actions in a specific location, you may have to consider something like a WebReport Trigger, or so (if you have WebReports).

Your CWS application can delete, once, and then get on with its business. Wherein, the WR Trigger, when hooking into a delete callback (or any sort of activity in a given location), can perform some sort of action on the node (in this case, check that it's okay that it was deleted, and then purge it, perhaps?).

Just a few ideas.

Thanks,

Nizar