I've created a repo-init script in my code base and I saw that it will be adding or modifying the changes in the instance while deployment but I removed some lines from the script and it's not reflected there. Is it possible to replace the entire repoinit script with new rules? Is there any filter m...

I have created some sling models by using a delegation pattern(by extending core components) but I've had some issues while writing unit test cases for these sling models. Hopefully, someone can give me some suggestions. thanks Thanks

Hi @Ronnie09 ,   You can use "Styles", which is another RTE plugin. The styles are implemented by adding <span> around the selected content therefore it will support multiple styles as well. Please see the documentation, https://experienceleague.adobe.com/docs/experience-manager-64/administering/ope...

Thanks all for the suggestions. I've been checking whether the agenId is a preview or publish if the agenId is a preview it will invoke the OOTB workflow and else it will trigger our customized workflow.

Thanks all for the suggestions. I've tried the above approaches but it wasn't working for me and after some research on the generated-package in /var, I found the paths are stored under contentRootPaths. So the below code snippet gets the whole path for me. workItem.getWorkflowData().getMetaDataMap...

Thanks for the reply. Could you please provide some hints or helpful links for the 2nd approach? I mean where I can update the custom workflow path for publishing to the Preview env.

I've customized the Request for Activation Workflow by overlaying libs/../managepublicationwizard and I can publish the Content to Publish environment and it is working as expected(As per my logic). But in the case of Publishing Content to Preview the same customized workflow will be triggering this...

Thanks for the reply. As per the documentation provided by the Adobe, we need to remove the right to the replicate action from all appropriate users for all relevant pages; to have this workflow triggered as a default action when any of the users try to publish (or replicate) a page. https://experi...

I've customized the Request for Activation Workflow by overlay libs/../managepublicationwizard and the manage publication button is showing for all pages and it's working as expected. But in Experience Fragments and files in the Asset folder, the manage publication button is not visible. But if I p...

Yes, the user has all the access rights/permissions.