Hi everyone,I have created a content approval workflow in which I am using OR split with 3 branches. Branch 1 is for Approval, branch 2 is for Rejection and branch 3 is for auto advance handler if there is no action from approver group in specified time. In branch 3 (Auto Advance Handler) I am using...

Hi All,I have written a replication agent on my author instance which index the content pages on a search server on activation of page. The issue I am facing is it index the long url. But I need to index the short url. If I apply the rule under etc/map tree on my author instance, this rule gets appl...

Hi,I have a requirement where I need to apply CUG on DAM Folder in AEM 6.3. There is option to add CUG on folders in classic UI but that is not working.I applied the CUG by adding user group, login page and enable CUG checkbox, but when accessing an asset, instead of redirecting to login page, it is...

Hi,I want to create a group in AEM 6.3 which can manage user and groups permission. I mean user of this group can create, edit, delete, modify new users and groups, can assign permissions to newly created user and groups.I created a user and gave it all the permissions on root folder, then also I am...

Yes. Extending the components will change the resource type and you need to take care of that in js file. But when you check the stored content, you will find that the resource type stored content is ootb component resource type and not yours.

If you want to change the resource type, you'll have to customize the backend code. But if your resource type is not changing, it should work with existing apis.

I looked at the journal jar, there component resources type is hard coded. That's why it is being set to ootb component resource type.

For 1st approach : I guess, you have created the abc.jsp. If yes, then it wont include base.jsp file which actually include your header file.So, the approach should be like : in base component, create body.jsp, and base.jsp. Base.jsp should include body and header  jsp.Now in Abc component, you crea...

Facebook login does not work in AEM 6.2 if you have not upgraded the instance with FP/SP.This is due to by default AEM 6.2 supports FB api version < 2.5. However, if you fully upgrade the instance with FP/SP, it'll work.

Hi, One use case I faced in Aem 6.2 is if any of the classes is using annotations from package 'org.osgi.service.component.annotations', annotations of package 'org.apache.felix.scr' are ignored by Aem. So, you can take a look at the codebase if any class is using annotation from 'org.osgi'  annotat...