In AEM 6.2 I created a simple workflow model with only participation steps. This is for reviewing/approving/publishing AEM Content Fragments.
I tried two options, but one doesn't work and the other seems to have an error...
What is the process to display an AEM Content Fragment from a workflow step when clicking on the payload?
Yes, the link shows how to create an AEM Content Fragment. However, how do you review the content fragment in a workflow step? The payload has the link to the content fragment and will never have a link to another page containing the fragment.
It's similar to an asset in the workflow step: clicking on the payload link will display the asset.
If you look at the screenshot, you see that the payload link is not resolved propertly.
I don't know if there is a bug, In notifications page it is creating assets link with assetdetails.html to open assets in Asset editor(which is correct) but for content fragment it should be opened like page with editor.html to see content fragments
even http://localhost:4502/bin/wcmcommand?cmd=open&path=%2Fcontent%2Fdam%2Fwe-retail%2Fen%2Fexperiences%2... also opening Asset editor in classic UI.
Thanks, arunp99088702. Yes, correct. The challenge however is the link provided in the workflow step (payload). If you work on an AEM Content Fragment and want to review the content fragment via workflow, then the payload link does not show the content fragment. It actually does nothing...
I could of course add a "sling:resourceType" pointing to some GET.jsp to read the content fragment and display it, but that is quite cumbersome for an author creating content fragments with the AEM tool.
I could also try to write a workflow process step, but I can't add a modified link to the "comment" programmatically.
I have a feeling a rendering resource is missing for AEM Content Fragments. See, if you edit an asset, e.g. image and review/approve via workflow, the link opens a viewer to display the asset. As a workflow member I can click on the payload and actually see the image, without having to leave the inbox. Hence I assume this must be possible for AEM Content Fragments as well.