You can add the extra option to the Page Info Popover at [1]. And refer [2] to create/trigger the workflow using the API from code, without the need of workflow selector. I hope this helps.[1] /libs/wcm/core/content/editor/jcr:content/content/items/content/header/items/headerbar/items/pageinfopopove...

As per my understanding, content fragments would be good option to use in case you wish to have global header n footer. A content fragment could be managed from a single source and changes would be easily pushed to all the pages without much effort.Refer:Adobe Experience Manager Help | Using Content...

Hello Everyone,As of now openJDK is not supported and yes regarding the accessibility of Oracle JDK, Adobe is working to make them available to all customers via a common platform.For the meanwhile, please raise a daycare request and the Oracle JDK would be shared to you, which you can use in your e...

The logic to fetch or create data for TouchUI inbox is not at the front end as in case of classicUI but at the Java side. below is the basic flow:A request to '/aem/inbox' resolves to path '/libs/cq/inbox/content/inbox'This renders data per [1] which creates the html page per [2]At the same time [1]...

The logic to fetch or create data for TouchUI inbox is not at the front end as in case of classicUI but at the Java side. below is the basic flow:-A request to '/aem/inbox' resolves to path '/libs/cq/inbox/content/inbox'-This renders data per [1] which creates the html page per [2]-At the same time ...

Hi Karan,Resource Resolver Factory is the solution for your case; just configure url mapping like [1] it will hide the configured content hierarchy in both the cases, url and anchor tags. Check the url mapping description in configuration for more details[1] /content/site/en/-/

Changing 'deny' to 'allow' in rule#0086 should help.

In such a scenario the previous request is aborted and the error [1] is logged depicting that the very same request is triggered again so aborting the previous one.That being said, this should not cause any issue to the functionality as the final/last request will succeed and the result for the requ...

Hi Nitin,Below are few pointers regarding the functionality:com.day.cq.dam.core.impl.event.CommentNotificationSender.java creates the task at [2]com.day.cq.workflow.impl.email.TaskEMailNotificationService.java reads the task/event and triggers the mail using the template [1]The legacy root for the e...