Product ideas | Community
Skip to main content

Ideas

Filter by idea status

10000+ Ideas

rwunsch-adobeAdobe Employee

Content Copy / Content Sync should preserve published state and support scheduled, scalable Author→Author+Publish syncNew

AEM as a Cloud Service "Copy Content" copies author-tier content only and intentionally strips replication-status metadata (cq:lastReplicated, cq:lastReplicationAction, cq:lastReplicatedBy, incl. the _publish/_preview variants). As a result, after a Prod→Stage copy the destination author has no record of what was published on the source, and nothing is published on the destination's publish tier.The only way teams can reproduce the source's published state today is to build external tooling that:1. queries the source (Prod) for the full activated set (e.g. via QueryBuilder), then2. re-replicates exactly that set on the target (Stage), chunk by chunk.This is inefficient by construction — it re-derives state the source environment already holds, it's bounded by QueryBuilder-over-HTTP result limits and request timeouts, and it doesn't scale to largerepositories (millions of nodes / multi-TB). We built and open-sourced such a tool to prove it works — https://github.com/rwunsch/aem-content-sync — but the fact that every customer has to build this isthe problem: it's redoing work the Content Copy tool itself should do.Requested:- An option to preserve replication status through Content Copy, and/or- Auto-publish copied content on the target (so the destination publish tier matches the source), and- Make these schedulable and scalable (delta/incremental, resumable), so lower environments can be kept in sync unattended without external scripts.This would eliminate a whole class of brittle, slow custom tooling and make environment refreshes accurately reflect production's published state.

RodWinLevel 2

Workfront Delegations - Problems & SuggestionsNew

I recently had a very frustrating time trying to figure out how we could use delegations when people are away. I see a few have posted on this subject. Here’s my two cents worth. Current Method User goes to Workfront Home/Worklist page. Click Delegations. Enter a date range and delegate, Save. This creates a delegation for the user's tasks that have a Planned Completion Date in the specified date range. The delegate can now perform the delegated tasks, issues, approvals etc as long as they have the appropriate Access Level. Problems Delegation delegates specific tasks to the delegate rather than just allowing the delegate to perform any of the delegator's tasks during their absence. The delegated tasks are those with a Planned Completion Date in the specified date range. The Start Date of that range cannot be earlier than today. Any tasks with a Planned Completion Date before the start date cannot be delegated. These would be the oldest tasks the delegator has outstanding and thus the most in need of delegation and work. The delegated tasks cannot be seen anywhere except in the Worklist. We don't use the Worklist at all. All users have a dash with reports of work that needs doing. The delegated tasks cannot be reported on. The only reference to delegations in the standard reporting system or API is the USRDEL object. This object can be used with an EXISTS filter to report ALL the tasks assigned to the delegator, viz: EXISTS:1:$$OBJCODE=USRDEL EXISTS:1:fromUserID=FIELD:assignedToID EXISTS:1:toUserID=$$USERID However there does not appear to be a method where that can be restricted to tasks that can actually be performed by the delegate i.e. those with a PCD in the range. Suggestions Change the method of operation so that delegation provides the delegate with permissions to perform ANY of the delegator's assigned tasks/issues/approvals during their absence (given they have the appropriate access level). The date range should be when the person will be away - Planned Completion Dates then have nothing to do with it. OR If we must use the current method of delegating specific tasks by date range of Planned Completion Dates, allow the Start Date of the range to be in the past so older, urgent tasks can be included in the delegated work. Provide reporting tools so that delegated tasks can be included in reports of assigned and delegated work by user. How does the Worklist pick them up? Allow a user to delegate their work to multiple people, or perhaps a team, so the work can be spread around. Provide the facility for planners/managers to create delegations for others in their groups/teams.  No doubt others will also have some suggestions.

PuneetAhujaAdobe Employee

How Simulation Mode Saved Me Hours When I Updated My Post-Purchase JourneyNew

A few months ago I built a Post-Purchase journey in Adobe Journey Optimizer that sent a personalised follow-up email based on what the customer bought. The journey had three branches — one each for Electronics, Sports, and HomeDecor — all tested, validated, and live.Then the business expanded into two new product categories: Grocery and Fashion. I updated the journey to add the two new branches and needed to validate them before re-publishing.  The Problem with Test Mode To validate the Grocery and Fashion branches in Test Mode, I needed two new AEP test profiles — one with a Grocery purchase, one with a Fashion purchase. Creating new profiles in AEP is straightforward, but it takes time for them to reflect and become available for testing. I could not just create them and start immediately.With a deadline to re-publish the updated journey, waiting for two new profiles to propagate was time I did not have. Simulation Mode: New Users in Seconds I switched to Simulation Mode instead. I created two new Simulated Users directly inside AJO — one representing a Grocery purchase, one representing a Fashion purchase — and they were available to test immediately. No waiting for anything to propagate.I triggered both in the same simulation session and got step-by-step execution logs confirming that both new branches routed and sent the correct email.What would have taken hours of waiting took minutes. Whenever you are adding new branches to an existing journey, Simulation Mode is the fastest way to validate them. You do not need to wait for new AEP profiles to reflect — you define the simulated user you need right inside AJO and test immediately.The existing branches (Electronics, Sports, HomeDecor) were already covered by my earlier test profiles. For the two new ones, Simulation Mode was the clear choice — and it saved me hours.Have you run into a similar situation when updating a live journey? Share your experience in the comments. Referenceshttps://experienceleague.adobe.com/en/docs/journey-optimizer/using/orchestrate-journeys/create-journey/simulate-journey/simulate-journey