Not alow delete content Item has status release after finish wokflow

Question

Hi all,
I create Content Item in the WebCenter Content with a workflow to approve it. After content item was approve and status is "Release", It will show on my portal. I saw that at this status, I still can delete this content Item. In this situation, It not alright with us. In fact, at a news website, when a news was public it can't be deleted so easy like that. The News only can be deleted when it was taken down(not public again) from the website. If the news still public no one have right to delete it.
Do you have any idea with this situation?
Thanks a lot!
Edited by: AS84 on 01:58 03-02-2013

Answer 1

I understand what you want to do, but I'm missing details how you do it, and why.
Anyway, I will try to guide you through the lifecycle, following your scheme:
a) Step1 (Content does not exist): User A will need at least RW permissions to create the content. The content will enter a criteria workflow to be approved.
b) Step2 (Content in the workflow): User B will need at least R permissions to read the content and approve it. As soon as approval occurs, the content is released
c) Step3 (Content published to the Website): all users will need at least R permissions to view the document. User B will need permissions to "unpublish" the content. You did not answer my question how this "unpublishing" is achieved. I would recommend you to expire the content. Expired content is no longer present on the site, cannot be searched for, but is not deleted. Expiration may take place when a user sets up the metadata Expiration date (dOutDate - see http://docs.oracle.com/cd/E23943_01/doc.1111/e10792/c03_processes.htm#r5c1-t19 ). You may want to customize your system that i) expiration is one-click activity b) only User B can expire the content. Unfortunately, security model does not allow securing metadata changes - all users with R permissions can modify metadata. You could define a profile that will hide the field to all users, but User B, but to be absolutely sure, you would have to add a filter that will (on server-side) prevent anyone else to do it.
d) Step4 (Content expired) You again did not answer, if there is any particular reason for not deleting expired content. Therefore, I will expect that there is none. You could use the Archiver to delete all expired content for you in a batch (once a day/week/month).
As you see, no one in the scheme above can actually delete the content.
Another possible implementation would be using: http://docs.oracle.com/cd/E23943_01/doc.1111/e10792/c05_security.htm#sthref863 (AuthorDelete=true) where only the user who is marked as the author (or in this context, rather "owner") can delete the document. This would be a bit awkward, though, as you would need to modify the value of dDocAuthor - this would again require customization.
Yet, another implementation would be using ACLs http://docs.oracle.com/cd/E23943_01/doc.1111/e10792/c05_security.htm#CDDBCIDA where User A in Step1 would have RWD permissions, and UserB would revoke User A's WD permissions (via ACLs), to grant them back in Step4. This will not require customizations, but on the other hand this would put much more responsibility (and training issues) to User B. Besides, ACLs can affect overall performance of your system.