How does Sitecore Experience Editor deal with component items on a page when a new version of a page is created?

Question

I've come across an instance where a client was using the Experience Editor to create a new version of a landing page and the components on the page did not increment the version number.

Is this expect behaviour? Or, should the components on the page also increment versions?

Ideally, the client wants to be able to revert back to the previous version for all the content (components) on the page and not just the page item itself.

---

Thanks everyone for contributing. It seems that the issue is with the SXA.

With "regular" Sitecore items, the versioning of components on a page is working as expected. See @hishaam's notes.

Answer 1

By default, when you apply a workflow on an item and it has been updated, a new version should be created for this item.

As your page has a workflow and not your component datasource, it is the expected behaviour that the version is not incremented.

Now, if you have a workflow on the page, when the user will need to update it, he/she will require to Lock and Edit the item. This is when a new version is added to the page.

After you have applied a workflow on the datasource item, you should test it with a non Admin account as this will bypass the workflow. I have tested this on my local instance and with an Admin user, the version is not incremented even if there is a workflow on it while using a content author account, the version of that particular component datasource is incremented by 1 including the page.

If you want to still apply the workflow mechanism for admin users, you'll need to implement a handler which will get triggered on the item save event. The purpose of the handler is to change the workflow of a particular item / datasource even for admin users.