Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

Feature Request: MSM / View component dialog box without breaking inheritance

Avatar

Avatar
Shape 1
Level 1
hgeller1
Level 1

Likes

0 likes

Total Posts

10 posts

Correct Reply

0 solutions
Top badges earned
Shape 1
View profile

Avatar
Shape 1
Level 1
hgeller1
Level 1

Likes

0 likes

Total Posts

10 posts

Correct Reply

0 solutions
Top badges earned
Shape 1
View profile
hgeller1
Level 1

22-10-2020

Hello,

our client is using the Multi-Site Management (MSM) features a lot.

When checking component content in a live copy, they need to break the inheritance of the respective component first, so that they can access the component dialog. Afterwards they need to restore inheritance again.

Business Value: This will reduce risks with accidentally not restoring inheritance and also will speed up the content QA process significantly. In AEM/CQ 5.6 (with Classic UI) it was possible to access/open the component dialog on a live copy with enabled inheritance.

Can this be added to AEM?

Thanks & Many regards
Hendrik

feature request MSM
4 Comments

Avatar

Avatar
Contributor
Employee
hamidk92094312
Employee

Likes

101 likes

Total Posts

240 posts

Correct Reply

38 solutions
Top badges earned
Contributor
Shape 1
Ignite 1
Give Back 50
Give Back 5
View profile

Avatar
Contributor
Employee
hamidk92094312
Employee

Likes

101 likes

Total Posts

240 posts

Correct Reply

38 solutions
Top badges earned
Contributor
Shape 1
Ignite 1
Give Back 50
Give Back 5
View profile
hamidk92094312
Employee

14-11-2020

Hi @hgeller1 

By accessing the component dialog are you referring to configuring the component ? If so, this is done as part of maintaining the integrity and consistency of relationship between the source and live copy. When the component configure dialog is open its going into an edit phase which can not be done without canceling the inheritance.

Avatar

Avatar
Shape 1
Level 1
hgeller1
Level 1

Likes

0 likes

Total Posts

10 posts

Correct Reply

0 solutions
Top badges earned
Shape 1
View profile

Avatar
Shape 1
Level 1
hgeller1
Level 1

Likes

0 likes

Total Posts

10 posts

Correct Reply

0 solutions
Top badges earned
Shape 1
View profile
hgeller1
Level 1

16-11-2020

Hi Hamid,

 

yes, this is about the component dialog, which also is shown when authoring content for a component in regular edit mode. I do understand that opening a dialog usually implies to make changes. But this is about opening the component dialog in read-only mode, so that editorial team can view and validate all relevant component settings / content (such as headlines, parameters, etc.), without the need to break the inheritance and then having the need to restore the content inheritance afterwards.

 

Many regards

Hendrik

 

Avatar

Avatar
Contributor
Employee
hamidk92094312
Employee

Likes

101 likes

Total Posts

240 posts

Correct Reply

38 solutions
Top badges earned
Contributor
Shape 1
Ignite 1
Give Back 50
Give Back 5
View profile

Avatar
Contributor
Employee
hamidk92094312
Employee

Likes

101 likes

Total Posts

240 posts

Correct Reply

38 solutions
Top badges earned
Contributor
Shape 1
Ignite 1
Give Back 50
Give Back 5
View profile
hamidk92094312
Employee

25-12-2020

Hi @hgeller1 

Thanks for submitting this feature request. We are further looking into the feasibility of the request and update this thread when an update becomes available.

Status changed to: Investigating

Avatar

Avatar
Contributor
Employee
hamidk92094312
Employee

Likes

101 likes

Total Posts

240 posts

Correct Reply

38 solutions
Top badges earned
Contributor
Shape 1
Ignite 1
Give Back 50
Give Back 5
View profile

Avatar
Contributor
Employee
hamidk92094312
Employee

Likes

101 likes

Total Posts

240 posts

Correct Reply

38 solutions
Top badges earned
Contributor
Shape 1
Ignite 1
Give Back 50
Give Back 5
View profile
hamidk92094312
Employee

28-01-2021

@hgeller1 

This request has been raised to the product team via the Jira CQ-4314786. 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.

Status changed to: Investigating