We have a user who uploaded a pdf to a conversation. The user then deleted the conversation and noticed the PDF is still accessible via the link. Is it possible to delete this PDF?
We have a user who uploaded a pdf to a conversation. The user then deleted the conversation and noticed the PDF is still accessible via the link. Is it possible to delete this PDF?
Was this PDF inserted in the conversation through insert --> image/file/video?
Did the user include a direct link in their conversation? Or did they link through the PDF?
It was inserted in the conversation.
Luke R Davidson even though the user is uploading the files - are they uploading a PDF directly from their computer?
Yes...as an attachment. It probably gets saved to CFS, but when the conversation is deleted, it does not appear the PDF is also deleted from CFS.
Yes, I can see what you are seeing. This is how Verint's OOTB functionality works with file storage - you can store the link and then you would have to navigate there to manually delete the pdf. There is an API endpoint that can help with this: Delete Media REST Endpoint
If you have any more questions please don't hesitate to ask
The issue is a non-admin started a conversation, uploaded a file, deleted the conversation and noticed the PDF was still floating out there. They wanted their PDF to be gone as well as it was scoped to that conversation.
To me this seems like a BUG...it doesn't seem like a PDF uploaded to a private conversation should still live in CFS once that conversation has been deleted.
Ben Tiedt thoughts?
Here is some more information on CFS: community.telligent.com/.../centralized-file-storage
Yes, I know all about that. However if I have a community of 10,000 people how am I supposed to find orphaned PDFs from deleted conversations?
There is an API endpoint that can help with this: Delete Media REST Endpoint
Ok...so that endpoint deletes media items...NOT pdfs added to a conversation. Ben Tiedt Michael Monteleone
A conversation is only deleted when all participants delete the conversation, until then, the participants who decided to leave/delete are flagged as inactive.
To access files embedded within a conversation, a user must be a participant in the conversation (and the conversation must exist).
When not all participants have left/deleted the conversation, all participants (ever) are associated to the conversation and can still access files within the conversation (the validation checks that the user is a participant, but not that they are currently active).
When the conversation has no active participants, it is deleted and no participant should have access to the files that were embedded within the conversation.
I have logged a bug to ensure that inactive participants do not have access to files embedded in the conversation:
Thanks Ben. I don't think this is a bug then. We had one user delete the conversation, but then complain he could still access the file. If this is by design we can let him know how it works.
Thanks Ben. I don't think this is a bug then. We had one user delete the conversation, but then complain he could still access the file. If this is by design we can let him know how it works.