Why design_dialog properties are stored in etc folder in Adobe Experience Manger(AEM)? | Community
Skip to main content
adarsh_nayak
New Participant
Sep 6, 2019 3:12 PM UTC
Solved

Why design_dialog properties are stored in etc folder in Adobe Experience Manger(AEM)?

Is there any place where we configured, because of which properties are getting stored in etc folder?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
arunpatidar
arunpatidarAccepted solution
New Participant
Sep 7, 2019 5:24 PM UTC

Hi, The design_dialog properties are saved in etc because values can be shared at the template level. If values store in the content page then sharing would be complex.

with dynamic templates, design_dialog values are stored in the form of policies inside the conf folder.

You can change only via overriding the OOTB code but is there any special requirement to change the storage location?

Arun Patidar
View reply

1 reply

arunpatidar
arunpatidarAccepted solution
New Participant
Sep 7, 2019 5:24 PM UTC

Hi, The design_dialog properties are saved in etc because values can be shared at the template level. If values store in the content page then sharing would be complex.

with dynamic templates, design_dialog values are stored in the form of policies inside the conf folder.

You can change only via overriding the OOTB code but is there any special requirement to change the storage location?

Translate
Arun Patidar
Terms & ConditionsAccessibility statement

Loading footer...