Hi Tam,   Do you see any exceptions in your author logs? Regards, Peter

Hi Manikanta,   First of all we can configure AEM to open in Touch UI by default [1]   In addition we can configure Sling Redirect to redirect any request into cf to editor.html Thus any content author who may have bookmarked old page will be redirected to TouchUI alternative.   [1] user interface -...

Hi Vaishnav,   We normally get these errors when maven versions are incorrect or maven dependencies are set in the wrong order, Please cross check your maven imports against this sample WKND project: GitHub - adobe/aem-guides-wknd: Tutorial Code companion for Getting Started Developing with AEM Site...

Hi Mario,   Once you get hold of your object you can ask Jackson to render the object for you:   JsonNode jsonNode = new ObjectMapper().valueToTree(product); String json = jsonNode.writeValueAsString(jsonNode); Regards, Peter

Hi TB3dock,   1. Config's that communicate with Dispatcher.so module mostly live in farms, Apache HTTP config's reside in vhosts.   As per Adobe Docs here's good explanation of the farm files. Explanation of Dispatcher configuration files | Adobe Experience Manager   2. We can put absolutely everyth...

Hi Mario,   Inside execute method of your workflow, you can use ResorceResolver rr; to get resource and then ask adaptTo method to get your Model.   Something along these lines would work:   Resource productResource = rr.getResourceResolver().getResource(workflow.getWorkflowData().getPayload().toStr...

Hi Jeevan,   Saw same issue, re-engineered Forms to submit data via ajax on Submit into a custom Servlet.   No more not replicatable on OOTB instance issues where data get's duplicated, or submitted as Null under load or exceptions like this one.   Works like charm. Regards, Peter

Hi Sonuk,   As per today's Cloud solution[Q1 2023], you need to marry all projects together for the deployment to cloud environment [1]   [1] https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/using-cloud-manager/managing-code/cloud-manager-repositories.htm...

Hi Shelly,   You can include exec plugin to tell you the java version during the build, it will be located in the build logs.   <plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>exec-maven-plugin</artifactId> <version>1.3.2</version> <executions> ...

Hi Shelly,   I assume on your local you got  Java 11 and pipeline fails with Java 1.8.   Create file .cloudmanager/java-version with 11 as content. [1] complete docs on subject.   This error indicates that code executed on Java 1.8, requires Java 11.   As per mockito-core release notes it's minimum ...