Expand my Community achievements bar.

Guidelines for the Responsible Use of Generative AI in the Experience Cloud Community.
SOLVED

OOTB properties available in aem

Avatar

Level 2

Hi Team,

When ever i create the component i need to provide properties for the component some of the   like below

1812449_pastedImage_0.png

Where i can see what and all properties available in AEM.

If we  want to create custom property how  we can create.

Regards

Kusuma.

1 Accepted Solution

Avatar

Correct answer by
Level 5

Those are set under the cq:dialog

1812872_pastedImage_0.png

so anything you set under that dialog is save with that name.

1812873_pastedImage_1.png

NOTE: both images are not the same fields

View solution in original post

4 Replies

Avatar

Employee

Its not really clear what component you are referring to so its better to provide a specific use case so we understand the requirements. Meanwhile you can check the following document to get some idea on how to create/extend AEM components:

Developing AEM Components 

Avatar

Community Advisor

you can check all properties at below inside Node Type Administration section

http://localhost:4504/crx/explorer/index.jsp

you can create custom node type by creating  cnd file

Adobe AEM/CQ5 Articles: Creating custom JCR node type



Arun Patidar

Avatar

Employee

Arun Patidar has provided the information to get all the properties for the node type cq:Component. I just wanted to expand on your question about creating custom properties. The node type cq:Component is OOTB and you cannot (should not) modify it to add new custom properties to the node type definition. With that said, you can add custom properties to an instance of the node type cq:Component. You will need to manage the name and the data type definition of the custom properties within your code.

Avatar

Correct answer by
Level 5

Those are set under the cq:dialog

1812872_pastedImage_0.png

so anything you set under that dialog is save with that name.

1812873_pastedImage_1.png

NOTE: both images are not the same fields