Make Publish Content Tree Workflow for "Manage Publication" configurable in regards to version creation | Community
Skip to main content
New Participant
January 18, 2024
Investigating

Make Publish Content Tree Workflow for "Manage Publication" configurable in regards to version creation

  • January 18, 2024
  • 1 reply
  • 448 views
Request for Feature Enhancement (RFE) Summary: In AEMaaCS the Manage Publication function does not create a version if editor publishes a page. This is a significant change to AEM onPREM which is nowhere documented. The only way the get the known functionality back is to create an own overlay. This is actually bad solution in regards to future Cloud updates and efforts to maintain overlay.
Use-case: Editors want to have backup from the status of pages when they were published. This is also to legal requirements partly. They are used to have this as it was standard behavior in AEM!
Current/Experienced Behavior: Using Manage Publication does not create a version.
Improved/Expected Behavior: Using Manage Publication (to publish) should create a version. Maybe the ootb workflow "Publish Content Tree" can be made configurable in regards to version creation so that each customer can decide if he needs this or not.
Environment Details (AEM version/service pack, any other specifics if applicable):  
Customer-name/Organization name: Carl Zeiss AG
Screenshot (if applicable):  
Code package (if applicable):  

1 reply

kautuk_sahni
Employee
January 31, 2024

@lutzu 

Thanks for proposing this idea
 
This has been reported to the engineering under the internal reference SITES-19514. The product team will triage this request to verify feasibility based on the prioritization model. This post will be updated according to the Jira request status.
Kautuk Sahni