Enable page versioning from page editor UI

[#1]

Request for Feature Enhancement (RFE) Summary:	Enable page versioning from page editor UI
Use-case:	A content author is making changes to a page and would like to create a version with its current state before proceeding with editing
Current/Experienced Behavior:	One should go to Sites navigation UI, switch the left toolbar to Timeline, create the version and return to the editor
Improved/Expected Behavior:	It is possible to create the version without leaving the editor. I see two ways how it could look: 1) there is a new "Create version" item in the "Page information dropdown"; 2) in "Page information" dropdown, when you select "Start workflow", there is an out-of-the box "Create page" workflow model you can pick. Please see pictures for both options attached.
Environment Details (AEM version/service pack, any other specifics if applicable):	AEM 6.5 SP8
Customer-name/Organization name:	Veeam Software
Screenshot (if applicable):	Option 1: Option 2:
Code package (if applicable):

[#2]

Hi @Alexander_Prikhodko 
For the second approach, I think you already have a solution that can be implemented without delivering features from Adobe.

As you mentioned, you can simply create a workflow 'Create Version'. with create Version Step and start a workflow from page information.

But for the first approach, it will make sense to add create version option in page information similar to the timeline trail option.

[#3]

Hi @arunpatidar 

Yes, I thought of this too, but custom workflows require additional maintenance as workflow API may change version to version. So we try to minimize such changes if they are not specific to our website's functionality.

[#4]

Hi @Alexander_Prikhodko ,

Thanks for proposing the idea. Looks like for the second approach there should not be any challenge with custom workflow as API change should not impact since the "Create Version" step is available OOTB. Let us know if that helps and we can raise an improvment specifically for the first approach.

[#5]

@Alexander_Prikhodko As mentioned by Akash,

Thanks for proposing the idea. Looks like for the second approach there should not be any challenge with custom workflow as API change should not impact since the "Create Version" step is available OOTB. Let us know if that helps and we can raise an improvment specifically for the first approach.

[#6]

@Alexander_Prikhodko , as mentionde by Akash, Looks like for the second approach there should not be any challenge with custom workflow as API change should not impact since the "Create Version" step is available OOTB. Let us know if that helps and we can raise an improvment specifically for the first approach.

Do you have more information for us?

[#7]

@Alexander_Prikhodko , We are closing this ticket as we do not hear a response from you. Please reply with information asked on this thread to reopen it again.