Explore product-specific spaces to ask questions, share insights, and learn best practices.
Recently active
Hi,I have a requirement where I want to pass dynamic number in place of <dynamic number> in below expression. toDateTimeOnly(concat(toString(toDateOnly(nowWithDelta(<dynamic number>, "days"))),"T10:00:00"))This dynamic number is being calculated in below manner - toInteger( ( (toInteger( toDateTime( concat( toString( #{ ExperiencePlatform.ProfileFieldGroup.profile._acssandboxgdcthree.EventReminders.all( currentDataPackField.id == ${supplementalId} ).at(0).reminderDate } ), "T00:00:00.000Z" ) ) )) - (toInteger( toDateTime( concat( toString( toDateTimeOnly( toDateOnly(now()) ) ), ".000Z" ) ) )) ) / 86400000) - 14I tried merging these two like this - toDateTimeOnly(concat(toString(toDateOnly(nowWithDelta(toInteger( ( (toInteger( toDateTime( concat
I have had issues saving and updating a fragment only to have it completely disappear from the email. Now whenever I try to add it it just returns a blank. I can still view and edit the fragment but I am getting nothing in the email. This is another glitch in the editor that needs to be fixed. Full video here: https://docs.google.com/videos/d/1z99oApzDy8m-3uMCleRMXsI_1dLOhHfptdAEsd9N0RM/edit?usp=sharing
After upgrading to ACS Commons 6.15.4, ACS Commons pages are no longer editable via editor.html as they were in 4.x (for example, Dispatcher Flush and Adobe League pages now appear read‑only). Is this expected behavior? Do we have any supported workaround to retain the old page‑based editing model, or is using an older ACS Commons version the only option?https://xxxxxxxxx.dev.xxxxxxx.adobecqms.net/editor.html/etc/acs-commons/dispatcher-flush/test-lts.html
Hi all,I'm working on an AEMaaCS workflow and would like to implement a custom Participant Step dialog with dynamic data coming from a previous Process Step.Here is my use case: An editor starts a workflow on a Content Fragment Editor receives a notification and completes the first task A custom Process Step collects all referenced nodes under the Content Fragment and stores them into workflow metadata like below: item.getWorkflow().getWorkflowData().getMetaDataMap() .put("discoveredNodePaths", collectedPaths.toArray(new String[0])); In the next Participant Step: Editor opens the task from Inbox A dialog should display all discovered node paths as a checkbox group Editor selects some nodes and clicks "Ok" The selected nodes should be saved back into workflow metadata Next Reviewer step: Reviewer opens task and sees selected nodes Can approve or reject If approved, a Process Step publishes all selected nodes My questions is about step4: How can I customize the Participan
We can share the ideas, suggestions, bottle necks , do and don’ts, any known issues on projects with Eds + universal editor. We can meet in person and talk more about this share the knowledge.
Hi, I’m looking for some advice.I have a user who is trying to add a new task to the bottom of a project. The task above it is a recurring task, but this new task should be a separate item. However, when they add it at the bottom, it automatically indents under the recurring task instead of appearing as its own task.At the moment, the only workaround is to add the new task at the top of the project. Is there a way to add a task directly to the bottom of the project without it being nested under the recurring task?
All journey versions in our `dev-beta-testing` sandbox return ERR_JOURNEYVERSION_107 ("journey version can't be deserialized"). Even brand-new minimal journeys (Audience Qualification → End, no email/actions) fail immediately. The sandbox was previously working — we have deployed and stopped versions. The version store appears corrupted: `GET /journeyVersions?journey=<uid>` returns the same 10 versions for every journey regardless of the filter. Other sandboxes in the same org work fine. Requesting guidance
The Concept: In sourcing, identifying cost pattern shifts or rogue spend requires heavy week-on-week spend analysis and deflation tracking. Adobe Analytics has built-in AI for this exact type of monitoring.The Adobe Connection:Intelligent Alerts & Anomaly Detection: Instead of using these features just for spikes in website traffic, they can be configured on internal B2B platforms to flag sudden spikes in unclassified spend or deviations from contracted pricing structures.The Conversation Starter: "Adobe's Anomaly Detection isn't just for spotting a sudden surge in website visitors. Imagine applying that same AI-driven alert system to internal B2B portals to instantly catch 'tail-spend' leakage or week-on-week deflation shifts without manual Excel tracking."
When adding a custom HEX code to a background color in the new Marketo builder, the editor does not apply the color; you cannot hit select/enter to apply the settings. The only way I have found to actually apply the settings is to paste the HEX code into the color block, then arrow up or down to change the color to an adjacent color, then return to the original color I pasted to get the color to apply.When applying a background color to a component using a HEX code, the change doesn't take effect automatically and we need to press the Tab key for the change to apply.This isn’t very intuitive and we would expect that hitting enter or selecting the value would automatically apply the custom Hex code for a background color.
In the AEM Assets Omnisearch UI, when a user opens the filter rail and selects any filter (file type, date range, tags, etc.), a search is automatically triggered on every single filter interaction. This causes: Multiple overlapping HTTP search requests fired in rapid succession Server-side query timeouts under normal DAM load UI freezing while waiting for responses Users unable to combine multiple filters before seeing results Required behavior: User selects multiple filters freely without any search firing A custom "Execute Search" button is visible in the filter rail Search only fires when the user explicitly clicks "Execute Search" This is a production workflow issue affecting all DAM users performing filtered asset searches.
Hi everyone, I have read the documentation and browsed the Q&As but so far, I am still not sure how an exit rate works combined with an eVar or Prop, hope you can help:We have few pages on our website and a lot of applications, sometimes several per page. That's why I need to use eVars / Props to check after which interaction with an application or after which process step a user left the website. The challenge here is, the eVars / Props I am referring to, are not always filled.Here is my example, I need clarification on:Case1:Hit 1: eVar_X (Application Name) fired with Value App ALast Hit before Exit: eVar_X (Application Name) fired with Value App ACase2:Hit 1: eVar1 (Application Name) fired with Value App ALast Hit before Exit: eVar_X (Application Name) not firedCase3:Hit 1: eVar_1 (Application Name) fired with Value App AHit 2: eVar_1 (Application Name) not firedLast Hit before Exit: eVar_1 (Application N
Packaging design plays a crucial role in shaping customer perception and influencing buying decisions. A well-designed package not only attracts attention but also communicates the brand’s identity effectively.Here are a few important benefits of strong packaging design:Enhances product visibility on shelves Builds brand recognition and trust Creates a memorable unboxing experience Helps differentiate from competitorsAt Design Concepts Creative, we focus on creating packaging that not only looks appealing but also drives real business results.You can explore some of our recent packaging design projects here:👉 our packaging design portfolio
Hi Team,Question 1I am using cloud SDK and experiencing jcr:title and jcr:description is not getting sync when I use OOTB rollout from master to live copies.anywhere I can look into custom configuration and add these properties.How to add them if they are not added ? Question 2I have checked libs/msm/wcm/rolloutconfigs and could not find anything related to these properties such as exclude node. I checked in apps/msm and could not find a custom configurations either so that meant we are using OOTB configuration only ? in that case do we need to raise a adobe ticket for this ?
We have browser height and width bucketed but it there another dimension that allows us to look at all the values (non bucketed)?
Hello everyone,With the upcoming migration from traditional classifications to Classification Sets in Adobe Analytics, I had a question regarding performance optimization.Previously, when using classifications, we had to create them separately for each report suite, even if the same variable existed across multiple report suites.With Classification Sets, we can now create a single classification set and apply it to multiple report suites, which simplifies governance and management.However, the official adobe documentation mentions two important points :• Processing time improved from ~72 hours to ~24 hours• Performance mainly depends on the number of unique key values, especially when combining variables from multiple report suites into a single classification set.ScenarioSuppose we have the same variable (for example an eVar) across 8 report suites.Instead of creating one classification set covering all 8 report suites, would it be better from a performance perspective to create: Two
Hi Team,We are facing an issue on a multi‑locale AEM site, where some users from the EU region are seeing broken/distorted pages.SymptomsBrowser console shows errors indicating that CSS files are not loading properly In the Network tab, we see a 301 redirect happening for a ClientLib CSS URLExampleOriginal ClientLib URL:https://domain.com/etc.clientlibs/site/clientlibs/clientlib-react.lc-e0056d5c22903998fcc41c48a71c217e-lc.min.cssRedirected URL:https://domain.com/de/etc.clientlibs/site/clientlibs/clientlib-react.lc-e0056d5c22903998fcc41c48a71c217e-lc.min.cssSince /de/etc.clientlibs/... does not exist in AEM, the redirected request ends in a 404, which results in the page breaking.ObservationsThe same behavior is reproducible using a curl request (301 redirect observed) There are no references to /de/etc.clientlibs/...: Not in AEM configuration Not in Dispatcher Not in rewrite rules The only place where this URL appears is in CDN logs, where it shows cache=pass We are not caching an
Hi,Can anyone explain why i can only watch first module of courses on any topic.After watching it shows start module and not in progress or finished.
In Adobe Orchestrated Campaign (OCM) Provide functional significance to the "Enable for Segmentation" toggle present on relational schemas. Why is this feature important to you UI elements that have no backend functionality create confusion for data architects and marketers during implementation, leading to unpredictable behaviors and wasted configuration effort. How would you like the feature to work If the toggle is present, it should actively allow the fields within that relational schema to be leveraged in the standard AEP segment builder. If this is not technically viable, the toggle should be removed from the UI to prevent confusion. Current Behaviour The “Enable for Segmentation” toggle on relational schemas has no current significance
Enable Adobe Journey Optimizer (AJO) Journeys to natively query and consume data residing in relational tables. Why is this feature important to you Siloing relational data strictly to Orchestrated Campaigns creates a disjointed architecture. Real-time journeys often need contextual data (like store inventory or loyalty tier lookups) that is best suited for relational storage. How would you like the feature to work Allow AJO journey conditions and personalization syntax to securely reference and pull data from relational schemas linked to the primary profile. Current Behaviour Relational tables are designed for OC only and cannot be directly consumed by AJO Journeys
In Adobe Orchestrated Campaign (OCM) Introduce a native, automated feature to clone XDM profiles into relational stores without dual-ingestion or Query Service workarounds. Why is this feature important to you Architectural simplicity reduces technical debt and maintenance costs. Forcing data engineers to ingest data twice or build scheduled Query Service scripts just to populate relational tables is an inefficient use of platform resources. How would you like the feature to work Provide a UI-driven toggle or standard data prep mapping function that allows specific XDM profile attributes to automatically sync or "clone" into designated relational schemas upon ingestion. Current Behaviour There is no free auto clone feature for xdm profiles into relational stores; data must be ingested twice or derived via Query Service
In Adobe Orchestrated Campaign (OCM) Enhance the test profile creation wizard to include functional hooks for updating or populating relational tables via CSV upload. Why is this feature important to you Robust QA requires highly specific, multi-dimensional test data. The inability to inject test data directly into relational tables hinders our ability to thoroughly validate complex orchestration workflows that rely on those data structures. How would you like the feature to work The test profile wizard should support a CSV template upload that maps test identifiers not only to XDM profile attributes but directly to custom fields within linked relational schemas. Current Behaviour The test profile creation wizard lacks placeholders or functional hooks to update or populate corresponding test data within relational tables via CSV upload
In Adobe Orchestrated Campaign (OCM) Update the standard AEP Profile UI to display relational store attributes and cross-table relationships. Why is this feature important to you A true 360-degree customer view is the primary promise of the Adobe Experience Platform. If relational data used heavily in orchestration is hidden from the Profile UI, practitioners cannot easily validate data ingestion or troubleshoot personalization logic. How would you like the feature to work The Profile UI should include a dedicated tab or widget that surfaces the underlying relational data and schema links associated with that specific profile's primary identifier. Current Behaviour Relational store attributes and cross-table relationships are not reflected in the standard Profile UI, preventing a unified “360 view” of a specific profile’s relational records
In Adobe Orchestrated Campaign (OCM) Enhance saved audiences to support incremental evaluation (entries and exits) rather than requiring full static snapshot re-evaluations. Why is this feature important to you Processing efficiency is critical when dealing with millions of profiles. Forcing a full re-evaluation is computationally expensive and delays the timely execution of campaigns that only need to trigger on net-new audience entries or exits. How would you like the feature to work Provide an option for saved audiences to evaluate continuously or incrementally, accurately flagging profiles that have recently qualified for or fallen out of the audience parameters. Current Behaviour Saved audiences function as static snapshots requiring full re-evaluation; they lack method to identify incremental entries, exits
In Adobe Orchestrated Campaign (OCM) Update the orchestration canvas UI to display unique profile counts rather than total records. Why is this feature important to you Architects and marketers rely on canvas counts for immediate sanity checks and sizing estimates. Displaying total records instead of unique profiles artificially inflates the perceived audience size, leading to misaligned expectations for campaign reach. How would you like the feature to work The numbers displayed above nodes and paths on the canvas should represent deduplicated, unique XDM profiles flowing through the orchestration step. Current Behaviour Counts displayed on the orchestration canvas represent total records rather than unique profiles
In Adobe Orchestrated Campaign (OCM) Enable the orchestration engine to dynamically re-evaluate consent and opt-in status mid-execution rather than relying on a static snapshot. Why is this feature important to you Compliance with privacy regulations (GDPR, CCPA) requires strict adherence to real-time consent. If a user opts out while a multi-day orchestrated campaign is running, they must be immediately suppressed from downstream deliveries. How would you like the feature to work The engine should natively ping the profile's consent attributes immediately prior to any delivery or action node, ensuring messaging is suppressed if the opt-in status has changed since the campaign started. Current Behaviour Consent opt in status is a static snapshot taken at the start and does not update mid execution
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.