Product Communities

Hi All, I am trying to use OOTB Archive extraction process step with launcher, but when zip file is having nested folder and files , launcher is not able to extract it properly wheras with manual triggering workflow works as it is triggered by admin.With launcher I am getting below error org.apache.sling.api.resource.PersistenceException: Can't create valid output path    at com.day.cq.dam.core.impl.unzip.impl.UnzipServiceImpl.getValidPath(UnzipServiceImpl.java:206) [com.day.cq.dam.cq-dam-core:5.15.190]    at com.day.cq.dam.core.impl.unzip.impl.UnzipServiceImpl.validateFilePath(UnzipServiceImpl.java:220) [com.day.cq.dam.cq-dam-core:5.15.190]    at com.day.cq.dam.core.impl.unzip.impl.UnzipServiceImpl.handleFile(UnzipServiceImpl.java:211) [com.day.cq.dam.cq-dam-core:5.15.190]    at com.day.cq.dam.core.impl.unzip.impl.UnzipServiceImpl.processZipEntry(UnzipServiceImpl.java:159) [com.day.cq.dam.cq-dam-core:5.15.190]    at com.day.cq.dam.core.impl.unzip.impl.UnzipServiceImpl.processEntries(U

Hi Workfront Community,Crowd-surfing for ideas on how to constructively guide some conversations we’ve been having internally at my org, hoping others dealing with the same challenge might have perspectives to share. With the push to adopt LLM tools, we’re getting requests from users that have exported Workfront data and used Copilot/Cursor to create reports/dashboards that they want built in Workfront.  The Problem(s):Suggested metrics/KPIs calculated based on completely fabricated/hallucinated data  Suggested metrics/KPIs that sound good on paper, but are inedible word-salads   Suggested metrics/KPIs that ARE reasonable, but rely on analytical capabilities and/or functionality that Workfront reporting tools simply don’t have.  Suggested metrics/KPIs that rely on functionality Workfront DOES have, but we don’t have implemented, licensed or don’t use in the way necessary to create the calculations Suggested visualizations that either won’t actually work, or again aren’t supported by an

We have a requirement involving seven different templates in AEM. For each template, we want to allow the Experience Fragment component, but with a restriction: the Experience Fragment should only allow the components that are specifically permitted for that template.In other words, each template has its own set of allowed components, and the Experience Fragment should enforce those rules so that authors cannot add components outside the template’s defined scope.We would like to understand: What is the best possible solution to achieve this scenario? Are there recommended practices or configurations in AEM to enforce template-specific component restrictions within Experience Fragments? Any guidance or examples from the community on how to implement this in a scalable and maintainable way would be greatly appreciated.

I have ran Best Practice Analyzer and found Content Area Violation on some of the shared fields across the project. The path: /apps/project-1/component/granite/ui/components/coral/color-picker/variations/ violates content areas override final path: /libs/granite/ui/components/foundation/form/select  and the content.xml for the component  is having as below   <?xml version="1.0" encoding="UTF-8"?> <jcr:root xmlns:sling="http://sling.apache.org/jcr/sling/1.0" xmlns:jcr="http://www.jcp.org/jcr/1.0"     jcr:primaryType="sling:Folder"     sling:resourceSuperType="granite/ui/components/foundation/form/select"/>   How to resolve this Content Area Violation?

Hi Team,We are working on a Workfront Request Queue where multiple Queue Topics are configured under the same request queue project.Example:Adobe DAM Youtube Social Media PublishOur requirement is:Use a single custom form Dynamically show different fields or dropdown values based on the selected Queue Topic.For example:If user selects Queue Topic = Adobe DAM → show DAM-related fields If user selects Queue Topic = Youtube → show Youtube-related fieldsWe tried using:Display Logic Advanced Logic queueTopicID conditionsHowever:Queue Topic is not available in Display Logic Advanced expression editing is restricted in our package/environmentQuestions:Is Queue Topic–based field visibility supported natively in Workfront custom forms? Is there any supported way to reference queueTopicID in display logic? What is the recommended best practice: Separate custom forms per Queue Topic? Helper dropdown field + display logic? Fusion-based solution? Would appreciate guidance from anyone who has impl

Hello, I have a 2 custom forms, one at the project level, the other at the issue level. They both have 2 typehead fields that both live on each level. When trying to pull the value at the issue level I do not get a value. The view never gives me the option to pick between what level. Any help would be greatly appreciated. 

I created a segment based on a fallout touchpoint in Adobe Analytics, and then used that segment within a calculated metric wrapped around an event.However, I’m noticing that the value of this metric changes depending on the overall date range selected in the report.For example, when I set the date range from January 1 to January 31, the metric count for January is 100. But when I expand the date range from January 1 to April 30 and then break the data down by month, the count for January increases to 200 instead of remaining at 100 (which I believe is the correct value).Can someone explain why this is happening? Is this expected behaviour when using a segment derived from a fallout touchpoint within a calculated metric?

Why not third? 

I am creating forms in Indesign with specific font styles to export into interactive pdfs to be used by non-designers for in store signage. Certain elements are not available to set in the forms window such as leading and creating centered or flush left or right text. I need help from someone who know how to do this. I can’t find documentation to make this work.

I want to create a Time Bound Date of Birth Component, may be by extending the datepicker aem form core component, where user is allowed to select a date between a specific date range, so once i have created this component then i want to use it inside the adaptive form, but how can i do this, i dont see any AEM forms core components under /apps/core/fd…., i am trying to install the latest service package and the forms add on package my instance is breaking, Kindly help here

 I am currently migrating AEM Classic Forms to AEM as a Cloud Service (AEMaaCS) and need to generate PDFs using an XDP template and XML data.I attempted to use the Output Service API as described in the documentation:Generate PDF documents using output service | Adobe Experience ManagerHowever, I am encountering import/package resolution errors when deploying my bundle to the local AEMaaCS SDK.Current Dependency (not working in AEMaaCS)<dependency><groupId>com.adobe.aemfd</groupId><artifactId>aemfd-client-sdk</artifactId><version>6.1.152</version></dependency>From my investigation, this dependency is intended for AEM 6.x (on-prem/AMS) and is not compatible with AEM Forms on Cloud Service.Proposed ApproachIt seems that for AEM Forms CS, the correct dependency should be:<!-- Source: https://mvnrepository.com/artifact/com.adobe.aem/aem-forms-sdk-api --><dependency><groupId>com.adobe.aem</groupId><artifactId>aem-

How to find out which attributes are being used from List in the live workflows. Eg : if a list have 100 attributes in the list, then how many are being used in live workflows and need to remove the unused from the list.  

Hey Community,          I’m trying to edit an email content and save the changes of a live journey. However the issue is that I can’t find the save option even though there is a tip-tool box mentioning that option. This save button used to be present before the generic Action activity update and that used to republish the journey. And my updated content logic is not being rendered in the new subsequent emails. Note: I can see the modified changes within the email designer.Even in the documentation the save button is not present (in screenshot) and doesn’t provide clear & helpful steps to proceed. I’d not want to create new versions just for every frequent & small updates. Appreciate any help on this! Thanks,Ganesh Kumar

We are using the trackingfeature attribute in HTML file  like this:<coral-card trackingfeature="aem:tracking:test">In older AEM versions this works fine, but in AEM 6.5.2 LTS, the value is not getting set when it contains a colon (:). If we remove the colon (for example aem-tracking-test), it works correctly.Why is the colon value not working in AEM 6.5.2 LTS, and what is the correct way to use values like aem:tracking:test while keeping the colon?

Hello Team,Does anyone has experience working with Custom action using mTLS certificate-based authentication ?I am trying to make an API call that uses mTLS certificate-based authentication (the certificate is used for both authentication and authorization). As per Adobe documentation - https://experienceleague.adobe.com/en/docs/experience-platform/landing/governance-privacy-security/encryption#mtls-protocol-support:~:text=of%20the%20data.-,mTLS%20protocol%20support,-You%20can%20now , no changes are required in the custom action or journey, as Adobe will automatically handle the process to enable mTLS. However, the API call is returning a 403 error.Could someone please help confirm if any additional configurations are required to resolve this issue?​@SatheeskannaK ​@Mayank_Gandhi ​@Pulkit_Jain_ ​@ManikSingla 

Hi,Is it possible to automate the step below when a new issue is created?Our process: There is a particular type of issue (queue topic), whenever it is created, we create a copy of a SharePoint Excel template and attach it to the issue. The copy file lives in SharePoint. After creating the copy using Fusion, how do I link that file to the new issue? Any suggestions?

Hi Everyone, I'm having a use case where i should use a option variable to make the content on/off  inside the web application how to do it if option is 1 then banner should be visible 0 disappear

If a marketer makes a mistake with a file created in Workfront, how does your team handle it?Do you:have the user open a new project, add additional tasks to the original project/post, or use a dedicated workflow to identify and manage errors or rework?Also, how do you handle mistaken content if you use the AEM native connector, so it displays in Content Hub?

Hi,I tried to upgrade Adobe Campaign Classic from 7.3.5 to 7.4.3 as test (base installation is clean)after this when server is starting I’m getting errors like below in watchdog.log2026-05-22 15:35:42.484+02 00001968 00001EA4 1 info log Launching task 'web@default' ('nlserver web -noconsole -tracefile:web@default -instance:default -detach -tomcat -autorepair') in a new process2026-05-22 15:35:47.485+02 00001968 00001EA4 1 error log SRV-810019 The server process 'web@default' (pid=15508) has unexpectedly crashed. It will be restarted. (iRc=-53)2026-05-22 15:35:47.485+02 00001968 00001EA4 1 info log Launching task 'web@default' ('nlserver web -noconsole -tracefile:web@default -instance:default -detach -tomcat -autorepair') in a new process2026-05-22 15:35:48.483+02 00001968 00001EA4 1 error log SRV-810019 The server process 'web@default' (pid=1996) has unexpectedly crashed. It will be restarted. (iRc=-53)2026-05-22 15:35:48.483+02 00001968 00001EA4 1 info log Launching task 'we

I am implementing frequency capping (e.g., max 2 impressions per user) for offers in AJO Campaign (CDE setup), but the capping is not being respected.Setup:Offers fetched using decisioning.request Impressions tracked using decisioning.propositionDisplay  Offer-level capping configured Event dataset includes Experience Event – Proposition Interactions field group Both request and display events are visible and stitched to the profile in AEPImpression Event Used:alloy("sendEvent", {    xdm: {        eventType: "decisioning.propositionDisplay",        _experience: {            decisioning: {                propositionEventType: {                    display: 1                },                propositionAction: {                    tokens: [tokensList]                },                propositions: window.latestPropositions            }        }    }});Issue:Even after the user reaches the defined cap, the same offer continues to be returned and rendered.What I Have Verified:propositionDis

I want to exclude assets from AEM Dam search if value is set searchable=false.can I do this by customizing damAssetLucene index. I can exclude a path from search but how can I do based on a property.

Hi There, Where do I start the Journey Optimizer Certification considering that I am a novice.

Would the event be generated only once / multiple times in AJO?

Wondering how everyone notifies their users when there is a known issue with Workfront. I know about the status page but recently we have had proof outages that have lasted half the day with no status update posted by Adobe. We have a technical support request queue and every time a Workfront issue occurs we get 50 different tickets entered saying the same thing. We created a FAQ section with the Request queue embedded, and we mark issues as Important Notices highlighted yellow so they can see there first that there is an active issue. However users are not looking and submitting the tickets anyway. It’s a huge chunk of time to respond to these tickets when we should be focusing on solving the issue or finding Workarounds. We don’t want to send out an announcement, because many people may not be effected and there is no reason to alert them. I’d love a way for them to get a popup that says something like “This issue has already been reported” or something like that. Has anyone found a

Retain a UI or Query Service metadata link back to the original AJO template name after an email is published in an Orchestrated Campaign. Why is this feature important to you Once an email is live, it becomes practically impossible to trace which template was originally used without relying on manual implementation notes, which severely hinders template auditing, governance, and optimization efforts. How would you like the feature to work Published messages should persist a metadata attribute indicating the Source Template used to create them, maintaining a traceable link back to the original asset. Current Behaviour Once an AJO template is applied to an OCM email and published, it becomes an independent message and AJO does not retain a UI or Query Service metadata link back to the original template name