Product Communities

Hello Everyone, We have observed an inconsistency between the Content Fragment Editor and the Universal Editor regarding enforcement of Content Fragment model constraints.A multi-value field  in our Content Fragment model is configured with Maximum number of items = 3.In the Content Fragment Editor, this constraint is respected and authors are prevented from adding more than three entries. In the Universal Editor, the same field allows adding a fourth item, and the value is persisted without any validation error. After saving from the Universal Editor, reopening the fragment shows all four values stored in the repository.This suggests that the Universal Editor does not currently enforce the max items constraint defined in the Content Fragment model.Please confirm:Whether this behavior is expected or a known issue If there are plans to align Universal Editor validation with Content Fragment model constraints Whether any server-side validation or configuration is recommended to prevent t

Hi, To resolve "Deprecated Service User Mapping Detected", I created the following file under the osgiconf of the ui.config"org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.amended.cfg.json"Following are its sample content. {   "user.mapping": [        "com.adobe.acs.acs-aem-commons-bundle:twitter-updater=[serviceuser--com.adobe.acs.acs-aem-commons-bundle--twitter-updater]",         "aem-precompiled-scripts:scene7-asset-reader-service=[serviceuser--aem-precompiled-scripts--scene7-asset-reader-service]"     ]}Does it look good to resolve the "Deprecated Service User Mapping Detected"? Or is there anything more to do?  

We have a large number of emails that we’d like to archive or unapprove to avoid accidental sends. Is there functionality in Marketo to do that?  Also, is there functionality to set emails to expire approval after a particular period of time or can you use a workflow to do that?  Thanks in advance for any insights!

Is there a way to use Send time optimization in Marketo?

It would be extremely helpful if the Adobe Cloud Manager UI displayed clear information on which user initiated a pipeline execution as well as which user approved or rejected the pipeline in the approval step.Today, identifying who triggered or approved a pipeline often requires navigating through logs or API calls, which is not intuitive. Having this information surfaced directly in the Cloud Manager interface would provide:Better traceability – Quickly identify the person responsible for starting a deployment or making an approval decision. Improved auditability – Essential for teams that must comply with governance, security, or compliance standards. Faster troubleshooting – When a deployment causes issues, teams can easily see who initiated or approved the pipeline and follow up with the appropriate individual. Enhanced collaboration – Team members and stakeholders can more effectively coordinate by knowing who has taken action at each stage.Displaying the triggering user and the

Hi in CJA text component https://experienceleague.adobe.com/en/docs/analytics-platform/using/cja-workspace/visualizations/text is there any way to add values from components ie such as todays date or is it only all static text cheersdaven

Hello, I’m having a problem with my tracking server. We have set the tracked links to expire in 3 days in a delivery, yet it isn’t expiring at all. Does anyone know in which part of server is this treated, and how could I inviestigate and debug this further?Thank you in advance!

Adobe Summit has always been about more than sessions - it’s about connection. The ideas sparked in sessions come alive through conversations with other attendees who are solving similar challenges, exploring new strategies, and pushing boundaries in their organizations. This year, we’re making it even easier to connect with other customers in attendance -whether you’re looking to network across solutions or dive deep with the Workfront community: 🌐 Option 1: Join the Official Adobe Summit Discussion Group (All Attendees)The official Summit Discussion Group is now live in the Experience League Community and it’s your go-to hub for connecting with the broader Summit audience across ALL Adobe solutions. This space is designed to extend Summit beyond the event itself, creating a shared experience that starts now and continues long after the conference ends. Inside the group, you can:Start networking with other attendees before you arrive Plan your Summit schedule and prioritize sessions

Currently, setting the default filters and groups in a Layout Template > “Home” > “Widget Settings”, changes the default filter for all areas of Workfront. IE if a user is on a layout template where the default grouping for the “My Tasks” widget is set to “Project”, all areas of Workfront where the user views tasks will be grouped by project. This is simply a poor UI choice - these settings should either only affect the home widgets, or they should be moved to a section of the UI that indicates they affect the entire system.

We have two custom actions in our journey. Based on these custom actions we personalize content in our channels.Eg:ProductCustomActionv1 and PriceCustomActionv1According to the setup, we first call ProductCustomActionv1 and then use the information in ProductCustomActionv1 to call PriceCustomActionv1 to find out the price and we use the price information in our channel(sms and email).Now if something changes in ProductCustomActionv1 and we created a new version ProductCustomActionv2 now we have to go manually to all steps within our journey to change the custom action reference. Instead if there is a custom action alias reference that is possible to set within the journey custom action configuration. then we don’t have to change anything within our journey.for ex: ProductCustomActionv1 is set with an alias pdtCustomAction, any new custom action I create I will also give the same alias then all the references of the custom action within the journey would automatically resolve. Please re

In my DSN (Adobe demo environment) I see such a field which can digest the asset directly from AEM Assets. However that field is a typical string. How to set up such field which can digest assets from AEM Assets?  

Hi AEP Community, Greetings! How much time does it take for profile attributes to sync in the profile store when ingestion type is streaming?I had the idea that, all profile attributes that is either ingested as batch ingestion or streaming ingestion (from a true streaming source), then it takes about 24 hours or 24+ for the values to be synced in the profile store and only then we could create segments. Is my understanding correct? or does streaming ingestion helps with profile attributes being updates in under few minutes and the audiences would qualify in under few mins? Thanks,Sambit

Hi, I’m trying to setup a daily dataflow from AEP to an SFTP using Destinations in AEP. I’ve setup the SFTP destination and have been able to connect to it successfully, but keep getting the following error:Unable to create directory for path sftp/SFTP_220260324_120519/part-00000-tid-2776579317160816273-5bb6a03a-8b4a-46fc-8fca-d3f38be573b0-1414191-1-c000.json.gz with the parameters flowId=9a432588-4c13-442c-85c0-9b968c07a5c3 datasetId=65aefbff544b412c9f33e273 flowRunId=d9568853-f592-4361-9b08-df20bb1db29f. The error message returned by the destination is Can't make directory for path "sftp" under "/".. Please verify that you have the necessary permission to perform the operation to the destination and the path is correct. We’re aiming to have the file upload to the root folder under the SFTP, and have confirmed that AEP has all of the necessary permissions to read and write the root folder in SFTP, but are still encountering this error. Has anyone encountered a similar issue in the pas

Hey All,Need your expert opinion on an Adobe Target + AEM Cloud setup.Currently, our AEM homepage is built using a single layout container (all components inside it). Because of this, Target (VEC) sees it as one DOM block, making it difficult to: 1. Reorder components 2. Inject experience fragments 3. Run personalisation without custom JS We are considering a few approaches - 1. mBox container for injection 2. Custom JS to reorder components 3. Nested layout containers (split page into sections) 4. Converting sections/components into Experience FragmentsAdditionally, we have three different user types, where the homepage content varies based on the user. One approach I am considering is to create user-specific content as Experience Fragments, export them to Target, and let Target handle the personalisation. On the AEM side, I would provide designated containers on the homepage where Target can inject the relevant content.From an Adobe best practices perspective, what would you recommen

I am trying to create configuraion to purge workflows which are older than 100 days for AEM as clouds service.Documentation -https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/operations/maintenance Above link says to create a node under /conf where as the link below asks you to create node under /apps for maintenance window.Sample configuration - https://experienceleague.adobe.com/en/docs/experience-cloud-kcs/kbarticles/ka-25921#environment  I'm trying to determine the correct way to create a maintenance window. I used the sample configuration and it worked, but after reviewing the documentation for second time, I realized that the maintenance window is supposed to be created under /conf. So what is correct place to keep this configuration?

I’m working on a Power BI dashboard for some of our business partners.  I’m told that delays with these projects frequently stem from the partners failing to approve proofs in a timely fashion.  In addition to project info, I am hoping to show folks info on current tasks and any pending proof approvals.I know that proofs use a completely different API than does Workfront.  My thought is to create a custom form for documents and populate it with reviewer/status info obtained from a Workfront Proof module (that way I wouldn’t have to hassle with making a Workfront Proof API call in PBI).  I tested the back end of this idea--pulling reviewer names/roles/approval status, aggregating those values, and updating a custom field attached to my document with the aggregated text--and it worked.I’m now trying to figure out the best way of isolating the population of objects I need for the front end of the scenario.  For my initial test, I’m hoping to pull documents with pending approvals for proje

I’ve created a scenario that automatically creates a Jira ticket when the issue status is set to In Progress. The scenario runs, however I need to create it for individual teams to ensure only their issues are adding to their Jira boards. I currently have a filter in place between the watch events and read a record for the teamID, however I’m hesitant to run the scenario because there’s a chance it would pull every other request that is newly In Progress to the incorrect board. Does anyone have any experience/feedback on this or if the recommendation is to create a new Webhook with the teamID as a filter in the first module rather in between the two? 

I have this ruleRewriteRule ^/content/my-project/([a-z]{2})/en/(.+)\.html$     /$1/$2 [R=301,L] Now when i hit with CDN domain then my CDN domain gets converted into AEM publish domain and this is true for all the 301 & 302 redirects. Followed couple of articles and did not worked like by adding {HTTP_HOST}, is any header needed in CDN to support this?

Hey AJO practitioners, One thing that keeps coming up when I talk to teams across the industry: staying on top of Adobe release notes is genuinely hard. Not because the documentation isn't there - it is - but because carving out time to check it regularly just doesn't happen when day-to-day work takes over. I built DXP Intel to solve exactly that. It monitors release notes across Adobe Experience Cloud solutions weekly, summarises what's new, and surfaces it in one place. You subscribe to the products you care about - Target, AEP, CJA, AJO, whatever's relevant to you - and only get an email when there's actually something new. No noise, no digest of nothing. Check it out → dxpintel.com Happy to hear any feedback - this is early days and I'm actively improving it.