| Request for Feature Enhancement (RFE) Summary: |
Lower the risk of having an unresponsive server by restricting the page reach for the functionality “Create launches”
|
| Use-case: |
A content author opens the Adobe Experience Manager (AEM) Launches interface (/libs/launches/content/launches) and clicks “Create”. The next step is to click to top-left button “+ Add Pages” to select a page or a folder. On the next screen, the content author selects “Included subpages”. The top-right button “Next” is clicked, the next screen is displayed and “Inherit source page live data” is clicked along with “with existing content”. The button “create” is clicked.
|
| Current/Experienced Behavior: |
The current behaviour is described above, with the mention the content author is allowed to select any page or node, even the top folder that might include a very large number of pages that will trigger AEM to create copies for all those pages. Due to the number of nodes, a site-wide transversal is triggered, resulting in an unresponsive AEM instance.
|
| Improved/Expected Behavior: |
To prevent the situation described above we would suggest the following improved behaviour.
- When the content author selects a page or a node ensures he has the write permission for that page or node
- Restrict the number of pages or nodes to be included in the Launch by leveraging a configuration field via sling:osgiConfig.
|
| Environment Details (AEM version/service pack, any other specifics if applicable): |
AEM 6.5
Service Pack 14
|
| Customer-name/Organization name: |
Service Canada / Government of Canada |
| Screenshot (if applicable): |
|
| Code package (if applicable): |
|
