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
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

Another question about how to add custom columns to the AEM Inbox

JonMaguire
Level 2
Level 2

I want to add two new columns to the AEM Inbox: Content Path and Initiator. I've read through a lot of inbox questions here on Experience League, but I am still confused on how to do this.
This question basically reflects what I want to accomplish. It is marked as solved, but the solution is another post by the OP that links to an AEM Forms solution. Is the AEM Forms doc really the correct solution for what I'm trying to accomplish in regular AEM? If so, am I supposed to create two services for both Content Path and Initiator? Both of these values are part of the Workflow Info tab so I assumed these values are already exposed somehow?

1 Accepted Solution
Vijayalakshmi_S
Correct answer by
Community Advisor
Community Advisor

Hi @JonMaguire,

Inbox items are populated based on the OOTB implementation from com.adobe.granite.workflow.* family.

In particular, it is the implementation of com.adobe.granite.workflow.WorkflowSession interface (OOTB implementation class is available in com.adobe.granite.workflow.core bundle)

Similar query and comments addressed in another thread for reference - 

https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/extending-aem-touch-ui-inb...

View solution in original post

2 Replies
Vijayalakshmi_S
Correct answer by
Community Advisor
Community Advisor

Hi @JonMaguire,

Inbox items are populated based on the OOTB implementation from com.adobe.granite.workflow.* family.

In particular, it is the implementation of com.adobe.granite.workflow.WorkflowSession interface (OOTB implementation class is available in com.adobe.granite.workflow.core bundle)

Similar query and comments addressed in another thread for reference - 

https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/extending-aem-touch-ui-inb...

View solution in original post

JonMaguire
Level 2
Level 2
Thanks for your reply, @Vijayalakshmi_S. Reading your answer on the other thread, are you saying extending this wouldn't be advised because it would be like rewriting the whole implementation?
Vijayalakshmi_S
Community Advisor
Community Advisor
Yes, On a very high level itself could visualize it would involve many other related changes - both frontend and backend.