Deleting released objects

I know that the whole purpose of releasing objects in the database is to keep them safe and prevent changes. However, we have an issue that requires deleting released publications and maps from the database.

Can anyone please provide a method to do this?

I have administrative rights, but in this case that is not enough - or so it seems.

We are presently on Tridion Docs 15.1.6

emoji
Parents
  • Hi Ragnar,

    Deleting released objects is possible. However, in a system where referential integrity of links and hyperlinks is a corner stone.

    The key thing is to see the system as a pyramid of links

    1. PublicationOutput, released (so baseline frozen) or not, links over root map and resources to content objects. This could be multiple PublicationOutputs reusing the content objects.
    2. DITA Maps link to DITA Topics or DITA Library Topics
    3. DITA Topics link to Library Topics
    4. DITA Topics and/or Library Topics link to the Images

    So to remove, it is easiest to start with the object types that have no incoming links.

    For Content Objects (so DITA Maps, Topics, etc) you need to configure a Released to Draft status transitions under the Settings area.

    Since 14SP4/14.0.4 there is a privilege to "Unrelease" PublicationOutputs as mentioned on https://docs.rws.com/en-US/tridion-docs-main-documentation-1165616/user-privileges-986494 as VPRIVILEGEUNRELEASEPUBLICATIONOUTPUT that "Unrelease" will implicitly also "Unfreeze" a Baseline. Remember that the Baseline is an internal object that tracks content objects (over LogicalId typically GUIDs, and of course versions).

    Typically Admins over Administrator user role get all privileges, including "Unrelease Publication Output Privilege". The one thing that does not happen - from the top of my head - is that the user interface will not show an "Unrelease" button next to the "Release" button of Publication Outputs in Organize Space. The functionality is only available over customer extension and the API to enable clean up operations.

     

    Putting this all together, you need the API, for example over ISHRemote, to resolve the tip of the pyramid.

    New-IshSession ...
    Set-IshPublicationOutput -LogicalId GUID-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx -Version '1.1.1' -LanguageCombination 'en' -OutputFormat 'PDF (A4 Manual)' -Metadata (Set-IshMetadataField -Level Lng -Name FISHPUBSTATUS -ValueType ELEMENT -Value VPUBSTATUSPUBLISHEDDRAFT)

    1. When you did an "Unrelease" PublicationOutputs of ALL PublicationOutputs linking to the content objects you can continue. 
    2. "Unrelease" Maps in Organize Space or over the API
    3. "Unrelease" Topics in Organize Space or over the API
    4. "Unrelease" Library Topics in Organize Space or over the API
    5. "Unrelease" Images in Organize Space or over the API

    I hope the above contains some hints on what you need. If you are still blocked, can you describe the steps and potential errors you see in detail?

    Best wishes,
    Dave

    PS: Wrote this mostly from memory, did not execute it in full. Note to self, anything else required to unfreeze the baseline ;)

    emoji
Reply
  • Hi Ragnar,

    Deleting released objects is possible. However, in a system where referential integrity of links and hyperlinks is a corner stone.

    The key thing is to see the system as a pyramid of links

    1. PublicationOutput, released (so baseline frozen) or not, links over root map and resources to content objects. This could be multiple PublicationOutputs reusing the content objects.
    2. DITA Maps link to DITA Topics or DITA Library Topics
    3. DITA Topics link to Library Topics
    4. DITA Topics and/or Library Topics link to the Images

    So to remove, it is easiest to start with the object types that have no incoming links.

    For Content Objects (so DITA Maps, Topics, etc) you need to configure a Released to Draft status transitions under the Settings area.

    Since 14SP4/14.0.4 there is a privilege to "Unrelease" PublicationOutputs as mentioned on https://docs.rws.com/en-US/tridion-docs-main-documentation-1165616/user-privileges-986494 as VPRIVILEGEUNRELEASEPUBLICATIONOUTPUT that "Unrelease" will implicitly also "Unfreeze" a Baseline. Remember that the Baseline is an internal object that tracks content objects (over LogicalId typically GUIDs, and of course versions).

    Typically Admins over Administrator user role get all privileges, including "Unrelease Publication Output Privilege". The one thing that does not happen - from the top of my head - is that the user interface will not show an "Unrelease" button next to the "Release" button of Publication Outputs in Organize Space. The functionality is only available over customer extension and the API to enable clean up operations.

     

    Putting this all together, you need the API, for example over ISHRemote, to resolve the tip of the pyramid.

    New-IshSession ...
    Set-IshPublicationOutput -LogicalId GUID-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx -Version '1.1.1' -LanguageCombination 'en' -OutputFormat 'PDF (A4 Manual)' -Metadata (Set-IshMetadataField -Level Lng -Name FISHPUBSTATUS -ValueType ELEMENT -Value VPUBSTATUSPUBLISHEDDRAFT)

    1. When you did an "Unrelease" PublicationOutputs of ALL PublicationOutputs linking to the content objects you can continue. 
    2. "Unrelease" Maps in Organize Space or over the API
    3. "Unrelease" Topics in Organize Space or over the API
    4. "Unrelease" Library Topics in Organize Space or over the API
    5. "Unrelease" Images in Organize Space or over the API

    I hope the above contains some hints on what you need. If you are still blocked, can you describe the steps and potential errors you see in detail?

    Best wishes,
    Dave

    PS: Wrote this mostly from memory, did not execute it in full. Note to self, anything else required to unfreeze the baseline ;)

    emoji
Children
No Data