Content views aren’t that intuitive but they are well documented.
If you’re using regular content views you could probably re-promote an older version. I haven’t tried this myself so good luck.
If you’re using composite content views you could change the version of the underlying content view containing the packages you’re interested in to an earlier version then publish and promote a new version of the composite content view.
We are using composite content views because, although they are more complicated to manage, they allow more flexibility.
The doc article you linked to is unfortunately not going to be useful to you.
it basically says that the feature is not available in Satellite 6 however it’s being treated as a request for enhancement in a future relase which is being tracked in a private redhat bug track.
Ah ! I forgot ! Do you know when and how the “subscription-manager refresh” (to update /etc/yum.repos.d/redhat.repo file) is executed automatically in clients after promoting another version ?