| Request for Feature Enhancement (RFE) Summary: |
Update Timewarp functionality to work with nested launches and with launches utilizing experience fragments. |
| Use-case: |
Successfully utilize Timewarp functionality within all AEM launches, to avoid capturing manual screenshots of all scheduled updates to have on record. This will allow us to compare our home page to older versions of itself in order to compare metrics, trends, and any other data needed to help us improve our business.
|
| Current/Experienced Behavior: |
Timewarp does not work as desired for Nested Launches or when experience fragments are used. The experience fragment is not loading when the page is viewed in Timewrap or the Version UI for Preview or Compare versions. The experience fragment does load appropriately if it was part of the initial template.
Our process for home page launches today involves creating nested launches off each Sunday's home page. The breaking the inheritance on components that will change for the next launch. Then we reauthor those components changing and set up for a future launch date.
|
| Improved/Expected Behavior: |
When utilizing timewarp we expect to be able to review previous version of any page regardless of how it was launched or what components were used on the page.
|
| Environment Details (AEM version/service pack, any other specifics if applicable): |
Production |
| Customer-name/Organization name: |
DSG (DICKS Sporting Goods) |
| Screenshot (if applicable): |
|
| Code package (if applicable): |
|
