Question about new content versioning system in v12

[Burvs]

I’m just trying out the new content versioning system in V12 and it seems like a big improvement.
Am I right that there’s also a proper draft / approval workflow with permission controls also in development? And if so… any idea how far off that’s likely to be?

[chrisjennings]

Hi @Burvs!

I’m glad you’re liking the direction we’re heading on that front. While I don’t have any specific timeframes to share at this time, further improvements to versions, approvals, etc. are an active area of planning. If you have specific use cases and scenarios you’re hoping to solve, please share them! They will help inform how we approach and validate what we’re doing!

[Burvs]

Hi @chrisjennings. It would be great to be able to have something like this:

• Non-admin users can create drafts and versions, but can’t publish. When creating a new draft or version, they can submit it for approval by an admin user.
• We notify that admin user that there’s a pending version for approval (via an email or internal notification).
• Admin users can visit the collection and easily view a list of all items that have drafts / versions which are marked as pending approval.
• Admin user can review changes and publish those items.

We have something similar to this in place that we put together pre-v12, and based on this: Build Content Approval Workflows with Custom Permissions but it’s honestly a bit janky.

It’s great that in v12, it’s now possible to view a collection list and use the button at the top to view all items with drafts, but (correct me if I’m wrong), that only works with “draft” versions and not versions named other things. So it’s still a bit opaque which items may have other versions unless you go hunting around for them..?

It would be good if there was a clear system for achieving all the above, and/or an up-to-date guide in the docs. Thanks!