Expand my Community achievements bar.

Content Reference fields in a Content Fragment should be updated when references are moved

Avatar

Level 2

2/3/21

Request for Feature Enhancement (RFE) Summary: Content Reference fields in a Content Fragment should update when references are moved
Use-case: When Content Reference fields are used in a Content Fragment model, and populated in the Content Fragment to point to an asset or content, when this asset or content is moved, these Content Reference fields should update like any reference fields.
Current/Experienced Behavior: When a content reference field is populated to point to an asset, and if the asset is moved, the content reference field is not updated. The Authors need to manually update these content reference fields to point to the new location of the asset.
Improved/Expected Behavior: The content reference field should update when an asset is moved.
Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5.7
Customer-name/Organization name: ANZ
Screenshot (if applicable): Behaviour is available OOTB. Just add a Content Reference field to a Content Fragment Model. Create a Content Fragment using this model. Populate this reference field to point to an asset e.g. another Content Fragment 'X'. Move the Content Fragment 'X' to a different folder. The Content Fragment that contains the reference to CF 'X' does not have the reference udpated.
Code package (if applicable):  
1 Comment

Avatar

Employee

2/19/21

This request has been raised to the product team via the Jira CQ-4316820. The product team will triage this request to verify feasibility based on prioritization model. This post will be updated according to the Jira request status.

Status changed to: Investigating