@Veena1    Is it the OOTB Replication properties being used? Are we selecting pages based on OOTB replication date? As per my understanding, Replication properties are not synced to Publisher OOTB. PID = org.apache.sling.distribution.serialization.impl.vlt.VaultDistributionPackageBuilderFactory.4c1b...

@Divya_T13    One option could be to use a Service User that can impersonate as the initiator & then trigger the new workflows.

Adobe documentation suggests   The AEM Cloud Service SDK is compatible with Java 21 and can be used to validate the compatibility of your project with Java 21 before executing a Cloud Manager pipeline. Edit a runtime parameter:When running AEM locally with Java 21, the start scripts (crx-quic...

Hi AEM Community,I'm looking for insights on measuring the reusability and value of assets in AEM.Many of us strive to create assets that can be used across multiple projects, regions, campaigns etc. But how do we effectively quantify the reusability and the value these assets bring to the organizat...

@Divya_T13    Please refer to following APIs https://github.com/Adobe-Consulting-Services/acs-aem-commons/blob/master/bundle/src/main/java/com/adobe/acs/commons/workflow/WorkflowPackageManager.java https://github.com/Adobe-Consulting-Services/acs-aem-commons/blob/master/bundle/src/main/java/com/adob...

@aem_geek    If its AEM 6.5 and a one time activity, probably you should clone the publish instance to set up the second one.   If its a regular one, then Author should be replicating to all publish instances.   Loading a publish instance with responsibility sync another would slow it down. Its bett...

@ArchitAr2    Please use ${appId}/components/xfpage. WKND might not be as updated as an archtype

@Divya_T13    Multiple payloads are not supported. It can only be one.   If you want to keep the related ones together, Maybe you should try exploring: Tasks & Projects instead. https://experienceleague.adobe.com/en/docs/experience-manager-65/content/sites/authoring/projects/task-content Workflow Pa...

Please add pathEmbed attribute for images to retain the Clipping path information. Example: https://example.scene7.com/is/image/myImage?pathEmbed=1&clipPathE=Outline    

Clipping paths aren’t extracted out-of-the-box in AEM DAM since they’re stored in Photoshop metadata, not XMP headers. But with a custom workflow, you can extract and store them for seamless use in Dynamic Media.  For details, refer to: Clipping Path Extraction in AEM DAM: A Custom Workflow Approach...