Under Community Review
over 3 years ago

Versioning of Structure Groups/Folders/Publications

Many times somebody has updated the Publication Properties, Folder Metadata, Structure Group Metadata, Category Properties or Keyword Properties/Metadata only to break something and it be found out later.

We can see the issue, when it occurred, but it would be great if we could see who changed it and get a comparison of the change at least.

We could benefit from complete beginning, although a simpler system would do.

For instance, we could live without rolling back/forward.

I know we can implement our own solutions for this, but it would be good to see this in the core product.

Edit (2017-06-04) by  fixed typo and added Categories & Keywords

  • This feature will be really helpful.

    publication, structure group, keywords with version history and option to roll back/ roll forward will be helpful

  • I think this is also very closely related to the same kind of issue with Localization.  Relying on versions of Localized components fails when they are unlocalized because all versioning and auditability of that content is then lost forever.

    So extending this idea to include the ability to audit component (and other identifiable object versioning) that is un-localized would be required for industries that are highly regulated (e.g. Financial customers).

    This is also noted here in this other idea:
    https://community.sdl.com/ideas/sdl-tridion-dx-ideas/i/sdl-tridion-sites-ideas#pifragment-21389=2

  • This is a legitimate use case for large enterprise customers... a large Financial customer in the US required this, and we had to build a completely custom implementation that used Event System to log out to external ORM system because key things are not versioned.  In addition, we had to design their solution to use custom components with custom schema to hold data so that it would be versioned, while it would have been much easier and cleaner design to use metadata of Publications/Folders instead if that was versioned (or at least auditable).

  • Hey Rick,

    I believe an Audit trail should certainly exist in a product like this, however I'm interested in expanding the version control to cover more item types.

    With the ability to see what changed between versions, when and by whom, with the ability to roll back or copy forward.

    We already have this functionality for some item types, expanding to cover more types would be very useful.

  • Another Idea is to provide audit trail functionality OOTB (i.e. the ability to see which user performed which action on which object).  Would that be a sufficient alternative for what you are looking for?

    In case you really need full-blown versioning functionality on so-called Organizational Items: is it only about the Organizational Item's metadata, or also about its contents (i.e. the items within the Organizational Item)?