Unrelease a publication output via UI (Organize Space and/or Publication Manager)

We have a few post publish plugins that we run when a user marks a publication output as release. Once a publication output is released it can no longer be published. We have had instances where the publish process fails and now we have to version up the publication and release it again. We would like to take advantage of the "unrelease" user privilege, and have been successful unreleasing a publication via API. We are wondering if there is a way anyone has implemented to allow a user with this privilege to trigger the unrelease through Publication Manager or Organize Space. We are on Tridion Docs 15.2 Patch 1, TIA.

emoji
Parents
  • Hi Akheil,

    I'm not convinced that "Unrelease" is the right answer based on the given information.

    I'm missing something in your explanation when you write "We have had instances where the publish process fails...". Can you explain in more details what and when your custom IPostPublishPlugins trigger?

    Like...

    1. Publish to Draft, there is a "PDF" or so attached. It is a Draft because the publishing train, including IPostPublishPlugins, vote that something is not good regarding versions are missing, links missing, DITA-OT errors, etc
    2. Publish to Release Candidate, there is a final "PDF" or so attached. It is the one you want to ship and freeze. You only get a Release Candidate as all validation on versioning, resolutions, links, hyperlinks are good. Nobody voted against.
    3. Then you do a status transition from "Release Candidates" to "Release" which on the standard product is labelling all objects and freezing the baselines.
    4. But in your customization your custom plugins make it fail? And then you need to upversion or unrelease? How did the transaction close successfully to released anyway?

    Best wishes,
    Dave

    PS: One of the recent references regarding PublicationOutput "Unrelease" is on  Deleting released objects  

    emoji
  • Hi Dave,

    Thank you for the insight into the process, we do run into the issue when we run custom plugins( step 4). We get the package post publish, clean up whitespace, zip up files for downstream internal system to consume. We run into issues when the background task services are restarted on the server or something similar happens, which kills the process prematurely. In this case we need to rerun the post publish plugins to create the zip and we are hoping unrelease and rerelease will allow us to accomplish this goal without additional customizations.

    emoji
Reply Children