Explore product-specific spaces to ask questions, share insights, and learn best practices.
Recently active
The current journey design adopts wait steps after each segment ranging from 30 mins to 4.5 hrs. This unnecessarily uses a wait nodes. I want to simplify the journey/reduce the number of nodes. Therefore, I instead want to replace these wait nodes with a single custom wait step. I have written an expression. The AJO expression editor has validated the syntax (yay!), so it seems I might be on the right track. However, can anyone confirm that this expression is correct? Do I need to include other functions? Or is there a simpler expression I can write?Note: I am using the event schema to trigger profiles to enter the journey, and each profile that enters is segmented as defined by the triggerDelay attribute defined in the schema construct. I am using this segment to define the number of minutes to wait ranging from 30 minutes to 270 minutes (4.5 hrs).if (@event{DW1267_J1_WBC_Dec_AdvocacyDW1267_J1_WBC_Dec_Advocacy._wbg.customerEventAttributes.nonPiiAttributes.triggerDelay} == "1") then (
Yesterday we started seeing a new message when making comments/updates in requests and projects. The message we’re getting is ‘This comment can’t be saved because it’s formatted content is too large’. Is anyone else getting this message? We know this is new because we use the same script with some clients, and the script used to be able to be pasted in full. Now we have to break it into two chunks. Why are they adding random limitations like this off-schedule? We’re just trying to work, and this doesn’t help at all.
Hi,I installed ACC 7.4.3 with Open JDK 11on Windows 11 and using IIS as web server. I am getting below error message when try to start the web module. 2026-06-01 11:23:32.045+05:30 0000258C 00002AA8 1 info log Launching task 'web@default' ('nlserver web -tracefile:web@default -instance:default -detach -tomcat -autorepair') in a new process2026-06-01 11:23:40.027+05:30 0000258C 00002AA8 1 error log SRV-810019 The server process 'web@default' (pid=32040) has unexpectedly crashed. It will be restarted. (iRc=-53) As per documentation, I have set both JAVA_HOME and JRE_HOME. Here are the outputs when I run these commands. C:\Program Files\Adobe\Adobe Campaign Classic v7\bin>nlserver.exe start web -verbose14:14:12 > Application server for Adobe Campaign Classic (7.4.3 build 9394@28aaec9 of 03/30/2026)14:14:12 > Launching task 'web@default' ('nlserver web -verbose -tracefile:web@default -instance:default -detach -tomcat -autorepair') in a
We have an ongoing requirement where API triggered campaign will be triggered from CDS source system when they make the API call. The namespace we are using is EID - which is the profile identifier for the existing users within company’s system. Now, we need to integrate another namespace which will be non-profile identifier for new first-time users which are not present in the source system. The source system integration with AJO API triggered campaign is based on campaignID value which is unique per campaign. Now, we cannot add 2 namespaces within same campaign and creating multiple campaign versions based on namespace is not a viable solution. Is there any way we can accommodate the requirement of non-profile identifier and profile identifier both within same campaign? As the campaigns will be relevant for new & existing users both. Another caveat is that in AJO we cannot store the JSON data for API triggered campaigns, only the event-based data will be available in profile stor
I've had clients that would have liked to reference a unique reference number for Portfolios and Programs. However, Portfolios and Programs do not get a reference number like a Project or Issue gets upon creation.
Description - Would love to see Workfront develop logic that allows users to see only the options that are applicable for them within a field, without having to create multiple fields. An example - I have two values that I want project owners to populate. One is Business Group and the other is Product. Each Business Group has its own products. In current state, there are two options. One is to have one Product field that lists all of the products for all of the business groups. The second is to create multiple fields - one Business Group field and then multiple Product fields (one for each business group). In the first option, project owners might have to scroll through a long list to see the one that they need, and if products are similar between business units, there could be confusion about which one to choose. There's nothing stopping them from choosing a product that doesn't match the business group. In the second option, you're maintaining extra fields even though all
I’m parsing a downloaded CSV like I have done many times before but for this scenario I am getting bad encoding. Any ideas what could be wrong?
We have a fully functional React SPA - it is standalone and not part of the Adobe architecture. A portion of the same website does utilize AEM to serve its content. The business would like to be able to personalize some content utilizing AEM and publish that as content on a React page/route. What is best practice to going about this? Some of the content may be dynamic based on some data that the React SPA fetched from an API as well.
In many enterprise environments, AEM is the backbone of digital experience delivery—powering critical customer journeys across channels. While much of the focus is often on content and features, I’ve found that operational excellence is what truly unlocks AEM’s full potential. Over the past year, my focus has been on shifting AEM operations from a reactive support model to a more proactive and predictive approach. The ChallengeLike many organisations, we faced common challenges:Limited visibility across AEM, APIs, and downstream systems Longer troubleshooting cycles due to fragmented logs Reactive incident handling impacting business SLAs These challenges highlighted a key gap—not in capability, but in end-to-end observability and operational alignment. The Approach To address this, we focused on three key areas:1. End-to-End ObservabilityWe integrated monitoring across AEM, dispatcher, and backend services to gain a single view of system health. This significantly improved our ability
Hi Team,What is the best option to monitor Web SDK calls and Adobe Analytics calls on public websites and send notifications whenever issues are detected? Any ideas, tools, or reference implementations that would be helpful? Thank you
We are interested in finding solutions to expose video content stored in an external file store like Azure storage through a common experience like Content Hub. Is something like this possible today or on a development roadmap? Additionally, do teams store native video assets in AEM Assets aaCS for this purpose?What other creative ways are teams storing and sharing video assets that we could consider adopting?
Hi All, Quick question, I have a requirement to pass my customer ID such as SEV ID in the a URL of a Button of Content Card, is it possible to encrypt the URL that will be dynamically populated based upon each customer identifier.Please note this is specifically for Content Card channel and button feature in it.
Hi everyone, I’m building an abandoned cart flow and hitting an identity namespace limitation.Journey starts with a web pageView (Namespace: CICID). Waits 15 mins, then sends a WhatsApp message. Needs to wait for a WhatsApp button tap (Unitary Event, Namespace: Phone).A single journey locks to CICID, preventing me from adding the Phone unitary event in the middle. Supplemental Identifiers aren't an option since both are person-based identities.The Catch:I need contextual payload data from both events simultaneously to execute the final step: the cart data from the web event, and the wamId and button text directly from the incoming WhatsApp event payload.My Current Workaround:I split this into two journeys:Journey 1 (CICID): Fires on the web event, sends the WhatsApp message, and uses an Update Profile activity to temporarily park the cart data into custom fields on the user's AEP Profile. Journey 2 (Phone): Triggers natively on the WhatsApp reply event. It pulls the wamid and button te
Hi Marketo Support Team, Could you please confirm if the endpoint mkto-ab190135.com is still active, configured, or tied to any existing Marketo instance? Thanks!
Good afternoon!We use (AEM/Guides) Native PDF output and have our draft comments set to display in PDF output with special formatting.They had been working fine until we recently updated to 5.1. Now everything in Guides shows correctly (author, source, preview) but there are no Draft Comments in the output PDF. What could have caused this? Is there a default that reverted possibly? Any help is appreciated!Thanks,Josh
Hello everyone,I’m trying to create an Audience consisting of visitors to our website who went to a certain section of our site at least twice in the last 30 days.To create it, I created two identical Event rules where-Server equals <our server/domain> AND URL contains <the section name in English> or <the section name in French>As I mentioned there are two Rules like above, completely identical. Then I selected In last 30 Days in the canvas. Is this Audience created correctly?Thank you.
Happy Monday, everyone! 👋 We kicked off our new monthly roundtable format today with a great turnout, 18 attendees and 59 chapter members and counting. We had folks join from across Ohio and well beyond, including Pennsylvania, Colorado, Massachusetts, and even Canada, spanning system admins, Fusion developers, solution architects, team leads, and end users. We also celebrated a first-time Summit speaker from our own chapter.We tried something new this month: we asked everyone for a burning question, a frustration, or a win when they registered, then talked through them as a group. Here are the main topics we covered, in case they help you or come up in your own instance:Preserving historical display logic on intake forms. When you turn off display logic on a request form, the historical summary it generated on older projects can disappear. The fix discussed: move the affected fields into a hidden or admin-only section, and keep the field sequence intact (the field carrying the "displ
The previous version of the community page included a score bar displaying progress toward the next level. Following the UI update, this information no longer appears to be visible.Could you advise whether there is an alternative way to track current level progress and the points required to reach the next level?
Hi Team,We have a business requirement where, whenever bulk data is ingested in Marketo, the records should flow to AEP with the attribute bulkupdate = true. Subsequently, for any genuine (normal) updates to the same records, the bulkupdate flag should be reset to false, and the updated data should flow to AEP accordingly in the same flow run.However, based on our testing, we are observing that bulkupdate = false is only being set when specific attributes are updated. Since it is not feasible to include all attributes in a Smart Campaign trigger, this approach is not scalable.Could you please advise:Which attribute or trigger should be used to reliably identify any genuine update to a record?Is there a recommended approach in Marketo to handle this type of logic, where a field needs to behave like a reset flag after any update?For example, we attempted to use Updated At as a trigger, but it is not qualifying records as expected.Looking forward to your guidance on the best-practice appr
Product area / feature areaAdobe Workfront > Reporting > Canvas DashboardsSub-areas: dashboard-level filters/prompts, Classic Report interoperability, cross-object reporting Current behaviorCanvas Dashboards can include existing Classic Reports, but dashboard-level filters/prompts do not apply to those embedded reports. Filtering only works consistently for Canvas-native reports.Canvas also has limited support for combining related-object data, making it difficult to build reports that bring together fields like Project + Task in one view. Desired behaviorDashboard-level filters/prompts should apply to eligible embedded Classic Reports so users can filter all dashboard blocks consistently.Canvas should also support stronger cross-object reporting so users can combine related data in a single dataset or visualization without duplicating logic or relying on external workarounds.At minimum, this could include:Full support for related-object fields, Supported join model for related o
We are excited to announce our Adobe Experience Manager Champion of the Month for May, @VidyR! Vidy was a clear choice for this recognition, as she truly embodies the spirit of the Adobe Champion Program. Not only does she actively raise her hand to support key initiatives like speaking on our upcoming Champion Application webinar, writing articles on Perspectives, and sharing feedback with our AEM Assets Product teams, but she regularly attends AEM Champion social events and fosters relationships outside of programming. She is a rising star in our community, and the program wouldn’t be the same without her bright personality. Thank you, Vidy, for your leadership and commitment to the Champion Program!
Welcome to the second edition of the Workfront Wire! This is your new monthly roundup built just for Workfront customers. Think of this as your one-stop-shop for the latest news, updates, events, and everything happening across the Workfront world. Each month, we’ll bring you what’s new, what’s next, and what you should know to get the most out of Workfront, without having to dig for it. Let’s get into it and be sure to check back next month for another edition of the Wire. Roadmap Webinar: See What’s Next for Workfront on June 4 The Adobe CX Enterprise Roadmap bi-annual webinar series is here! This is your best opportunity to learn about the future of Workfront (and other Adobe solutions) and ask questions in real time with the team building it out. Join the Adobe Workfront Product Marketing team for an inside look at how AI is shaping the next chapter of Workfront. In this 60-minute live session, you’ll see how upcoming capabilities like Workflow Optimization Agent, AI Collabora
Hi Team,I'm currently working on a custom component in AEM as a Cloud Service.In the Rich Text Editor (RTE) field of my dialog, when switching to source edit mode (HTML view), I noticed that plain text input is automatically wrapped with <p> tags. For example:Input:Hello WorldOutput:<p>Hello World</p> I would like to disable this behavior so that plain text remains unchanged, without being wrapped in <p> tags. Is there any configuration available to prevent automatic <p> insertion in source mode?Or would this require a custom plugin or overlay? Thanks in advance for your help!
We're currently using a request queue that creates issues by default. Our team then works with tasks, so we end up with both issues and tasks in our projects. This is causing confusion.Ideally, we'd like requests to come in as tasks only — no issues at all. We want to keep things simple and have one object type for the team to work from.I know routing rules can auto-convert issues to tasks, but the original issue still remains. Is there a way to either:Have the request queue create tasks directly, skipping issues entirely?Or is there another approach anyone has found that achieves a "tasks only" experience?
Hi Team,Last week, my team needed to deploy an urgent, time-sensitive hotfix. The fix itself was incredibly minor just a two-line null-check update inside a core OSGi service. We tested it locally against the latest SDK, the PR was approved, and we kicked off the Cloud Manager production pipeline.Twenty minutes later, the pipeline abruptly halted with a Hard Failure at the Code Quality step. I pulled the logs, expecting a missed unit test, but instead found this:[WARNING] [region-deprecated-api] ... Usage of deprecated package found: com.day.cq.commons.jcr.JcrConstants. For removal: 2026-06-11[ERROR] Rule region-deprecated-api failed. Build halted.Because of the strict API deprecation gates rolled out in the recent 2026 releases, what used to be a passive log warning had instantly become a deployment blocker.The frustrating part? The code that failed was not even part of our hotfix. It was an old legacy utility class deep in our core Java bundle that hadn't been modified in three years
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.