we can call getParent() on any page object and not necessarily on current page only.so In your case, Get the page object using child page path/resource and then call getParent() method.You have multiple options to convert it page object based on your child page path or object type. For example:  If ...

@JakeCham It's better to write all your business logic in sling models/BE services instead of Sightly.  You can use below method to get appropriate parent page details in sling models or services.  Page getParent(int level)Returns the relative parent page. If no page exists at that level, null is re...

It should work. Please make sure you're updating ui.content filters. Please check reference. https://jackrabbit.apache.org/filevault/filter.html 

Hi Raja,There are two ways you can try:Option 1: 1. Use the 'Publish page' option from page itself. 2. Then it will pop additional screen where you can disable XFs/references which you don't want to publish.   Option 2:  Using Manage Publication options from sites1.  Click Manage Publication  2. Dis...

You can write custom process step for the rejection and keep it after Reject Participant step something like below:   Here is the sample code you can write in process step and configure it.Please note that you need to choose appropriate route based on your workflow model structure. List<Route> backR...

As  I heard offset and limit parameters have been added in the latest AEM as a Cloud Service but I'm not sure whether this feature is part of the version you're using or not. 

did you try like this?query { articleList(offset: 5, limit: 5) { items { authorFragment { lastName firstName } } } }please check for more info:  https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/headless/graphql-api/content-frag...

@Shashi_Mulugu I think using sling model we can only expose content as json using sling exporter.@Exporter(name = ExporterConstants.SLING_MODEL_EXPORTER_NAME, extensions = ExporterConstants.SLING_MODEL_EXTENSION)https://developer.adobe.com/experience-manager/reference-materials/6-4/javadoc/constant-...

I think you have to update update your graphql queries as well when you upgrade AEM to 6.5.15, prior to AEM 6.5.15, graphql was querying data based below properties of content fragment model but now it works based on content fragment model name itself.      

please check https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/sling-filter-with-multiple-resource-type-and-specific-query/td-p/454045 and see if that helps.