Retired Custom Content

Support has received the following Enhancement Request from an administrator within The Andersons, Inc. in case IS-04150325. They are requesting the following:

"There should be a way to reinstate or copy/edit retired content in case of accidental retirement. Also, if an asset is retired, it should not show in a channel to be edited. Also, I should not get an error when reusing a title if the original version is retired."

8
8 votes

Archived · Last Updated

Comments

  • Patrice Koonce
    Patrice Koonce
    ADVENTURER
    edited February 2022
    @Erin Emerson, @Sue Orchanian
    Using a retired filename came up in our internal conversations as well.
  • Erin
    Erin
    ADVENTURER
    Third Anniversary
    edited February 2022
    @Patrice Koonce & @Sue Orchanian
    Yes, that is one part of our internal conversation that we see with the way the system is designed when updating SCORM files. I do agree that there should be more robust admin tools and features.
  • Unknown
    edited March 2022
    Yes! I would love this feature. Just had an experience where I retired a Channel and tried to use the same name for a Journey. There was no way to "Un-Retire" the channel or even Edit the retired Channel to use the name again. 

    Until this feature is added, the workaround would be to change the name of the item first, then retire the content.
  • Michael Murphy
    Michael Murphy
    CARTOGRAPHER
    Third Anniversary 100 Comments 5 Likes Name Dropper
    edited April 2022
    Hi all! This is definitely a popular request lately. We recognize there are lots of reasons customers want to access retired content.
    We'll be working "un-retiring" retired content into our plan. At this early stage, I don't have a timeline for this yet.
  • Tim Lawrence
    Tim Lawrence
    ADVENTURER
    First Anniversary Name Dropper First Comment
    edited July 2023

    Our team has also run into the need for editing and/or reinstating retired content.

    We've noticed that retired content titles will block the creation or use of content following a similar naming convention, but the retired content cannot be edited to say "Retired", "Do Not Use", etc.

    While Kevin's idea is from 2022, our team and stakeholders would like to express similar interest and a need for this update.