Hi @h_kataria , thanks for your response. please find updated query as you suggested but still the expected result 12 was not coming.QUERY -1 ========= path=/content/wkn/en/us/c/support type=nt:unstructured group.1_property=sling:resourceType group.1_property.value=wknd/components/text group.2_prope...

Hi Team,      i was trying to execute below query on my query builder, when i execute this query (search text: Smart Lock) im getting 12 result count which is expected result, same when i execute this query with (search text: smart lock) im getting 0 result. I also tried with the group.2.operation=e...

Hi @arunpatidar , kindly please gothrough my above screenshot, i have used exisiting user account. also im currently using the same groovy console version which is not compatable with aemascs.

Hi All, i got through this post AEMasCS  , above groovy console package will not support in AEMasCS  kindly pls confirm.

Hi @arunpatidar , im able to use currect user session but still facing same issue.PFB,  import org.apache.sling.api.resource.ResourceResolver import org.apache.sling.api.resource.ResourceResolverFactory import org.apache.sling.pipes.Plumber import org.apache.sling.pipes.PipeBindings def resourceRes...

Hi @MukeshYadav_ , pfb i have added the user to admin group, but still have same issue, 

Hi @Harwinder-singh , i have added groovy-console-system-user into administrator group as well. but still have same issue.  

Hi Team, we are in AEMasCS, we are trying the update a Text content across our global pages, for that we are using sling pipes,i downloaded the package of groovy script from below git hub Github link and installed in my local. here is my groovy script,when i tried to execute the script im getting us...

thanks much @EstebanBustamante , @MukeshYadav_ .

Hi Team, we were trying to implement find and replace content on our project which is similar to classic UI search and replace functionality.  i have created a component find and replace. while executing the code on my localhost:4502, its working as expected, where when we deploy the code in AEMasCS...