Build better products with our product team
We would like to have the option to color code cards on a Board, similar to how we can apply conditional formatting to tasks in the List view of a project. Having this option would allow our users to quickly see task statuses, categories, etc. without having to read the card text. It could work similarly to how conditional formatting is applied in the List view, by having the option to apply a specific "view" to the board overall.
When viewing a list of projects, I want to use the native Milestone View - but I only want to display SOME of the milestones. The requirement behind this design is that different stakeholders want to track different milestones. In other words, multiple milestone paths on a single project. Since you can't apply multiple paths to a single project, my solution is to lump all the milestones into one path and then use filtered reports/dashboards to deliver the necessary data to each stakeholder group. I really like the native Milestone View and wish I could create filtered versions of it… so that each stakeholder group could use that view but only see the milestones that are relevant to them.
It would be useful to be able to use Regex when creating segments in Adobe Analytics to help segment based on patterns/sequences rather than on specific values. It would also prevent the need for building complex, “stacked” segments with multiple criteria/containers.
We'd like the ability to copy / duplicate document folders. Some of our projects have hundreds of documents and it would be easier to copy folders and slightly modify the names vs creating every single folder
The Time off Calendar in Workfront Workflow is hidden away and not in a easy location for Users to Navigate to. It would be amazing if there could be a Time Off Calendar Widget, so Users can add to their Home Page and log their Time Off there.
Description - Allow the option to hide the hourly breakdowns on weekly calendar view or expand the collection of calendar items in the top portion of the calendar Why is this feature important to you - We have many tasks that pull into a calendar view and the many tasks are now all scrunched together at the top. When the list is super long, a scroll bar appears and you can scroll within the tiny area. There is not a way to hide the hourly blocks below or expand the top portion to have better visibility into the items like the current/old calendar weekly view. How would you like the feature to work - Add a toggle button to hide the hourly blocks and/or a way to expand the top portion of the calendar to be able to see more items on the screen. Current/Old Behavior - New Calendar -
DescriptionI would like the ability for Adobe Analytics admins to mass merge or mass delete Workspace tags and component tags without needing to view the affected Workspace dashboards or affected components themselves. There should also be an ability for us to rename tags so they are either all capitalized the same way - e.g., Sentence case, Title Case, or lowercase. At the moment, people at my company are able to create tags on their own, which means that if there are typos to a tag, or if there are duplicates, we need to go into each Workspace dashboard or each component itself for us to correct it. It makes it very difficult to find the Workspace dashboard we need. Tags then become an unused feature for us on Adobe Analytics, and we just end up using the search bar, which is not always effective. I have attached some screenshots to help visualize the problem.Why is this feature important to youTo make it easier for users to search for the Workspace they need without needing to rely on the Workspace listing search bar, which is not always effective, because it pulls up a large number of Workspaces (including drafts, finalized copies, and QA test boards).How would you like the feature to workThere should be a feature accessible to all admins or people with admin permissions where we can easily mass merge or mass delete Workspace tags (for both the dashboards and the components) without needing to click to adjust each one manually. Current BehaviourCurrently, for us to delete and merge tags, we need to slowly go through each tag, mass select the dashboards or components, remove the unneeded tag, and redo this entire process until there is only one tag left. This is incredibly tedious. We are also not able to edit tag capitalizations at all.
As noted in this community post, there isn’t a means of adding fallback fonts in Theme font selection UI. Fallback fonts are a standard best practice, and interestingly, the Design Accessible Content documentation page mentions fallback fonts. Without it being built in as an option, custom CSS is required to add them to email designer emails. A noted on the custom CSS documentation page, users who choose to leverage custom CSS do so at their own risk and will not be supported by Adobe Support. To support best practices and ease of use, I’d propose the product team incorporate fallback fonts into the Theme functionality—whether built in behind the scenes for each standard/Google font, or a more flexible user-driven option.
I propose Marketo allow us the add in a Details constraint into the "Synched to SFDC" filter and trigger so we can operationalize workflows to inform us when a record fails to sync. I would like to be able to create an alert that fires off to my Operations team with the lead info and include the Details on the Sync failure so that both Marketo Ops and SFDC Ops are aware of something going wrong.Currently this is a manual process where we have to look into our workflows that sync records to SFDC and manually extract the lead information including the failure reason. This is time consuming and not an efficient way to ensure that all records are coming over as expected.
There is no API endpoint for being able to move assets to different folders. We should have this API endpoint made and then added as a tool call to the native MCP so that agents can move assets into folders for us. At the moment moving folders between assets is a manual task
When entering tags (the free text keywords, not tags from a fixed list), e.g. “engineer, female, tech, big data” in the meta data schema, there ae only options available where you enter one tag, hit Enter, type the next tag, hit Enter etc. This process is time-consuming, especially as many assets are supposed to have lots of tags. While AI tags can help with search, we can’t control them and you also cannot copy them to the main tag field to work with them. That means it is still necessary to enter tags manually. It would be way better to be able to copy/paste or type a list of comma-separated tags, e.g. “engineer, female, tech, big data” into ONE metadata field, and then hit Enter, whereas the system recognizes the tags as individual entities separated by comma and turns them into individual items automatically.
I'm aware that Workfront Reporting Canvas will be available in coming months, but it would be nice to have Workfront API working with Viz tools like Power BI and Tableau.
I am desperately trying to deliver on an ask to provide our “worker” level users with access to the To Do list on their home page. Issue is this requires them to have the ability to create tasks. Our users need to be able to fill out custom forms on PM’s projects so they need Edit access to projects but at some point the Project Sharing started allowing users with Project Edit access the ability to be given Manage access to Projects. If they are mistakenly given manage access on someone else’s projects they now would have the ability to add tasks in their timelines. I would love if we could find a way to let them use that feature but not allow the accidental oversharing.
Description - If you go to settings > interface and then try to edit a filter or a view, there is no responsiveness when you click "save filter." Though this is the tiniest thing, I get no confirmation visually that my changes have actually been applied and I have to close the window/open the filter or view back up to verify or just trust that it was applied. Why is this feature important to you - Would improve UX when editing views and filters. How would you like the feature to work - 1) Ideally when I hit "save filter" the window would close, and I'd get the little pop up confirming my changes have been applied, similar to when you save a custom form edit. 2) But I'd take anything really! A check mark to appear upon hitting save. A pop up confirming my changes have been applied. Anything! Current Behaviour - When you click "save filter" nothing happens- I therefore end up clicking it like 5 times thinking it isn't responding to me 😉
Description:The Upcoming Campaigns panel in Marketo Sales Insights (shown in the Salesforce contact view) lists scheduled email campaigns for the next 30 days. It also says these are "not limited to qualified leads."Problem:Our Marketo instance supports multiple businesses and brands. Sales reps see campaigns from other businesses in the panel and assume the contact is about to receive those emails. This causes confusion and unnecessary escalations. Reps think the contact is being mis-messaged, when in fact the contact doesn't qualify for those campaigns.Requested enhancement:Add an admin setting or user toggle, such as "Show only campaigns this lead qualifies for", that filters Upcoming Campaigns to campaigns whose smart list and filters the lead actually meets. If full qualification evaluation isn't feasible, allow admins to filter the panel by workspace, program channel, or tag, so each business sees only its own campaigns.
Use case and current behavior: We are migrating from AEM on-premise to AEM as a Cloud Service (Sites). On-premise, we override the Welcome screen so that each user group sees personalized links and shortcuts. On AEM as a Cloud Service, /libs is immutable, so this override is not possible, and there is no supported out-of-the-box way to show different Welcome screen content per user group. Business impact: Authors and managers would find the right links more easily if the Welcome screen matched their area of access and job responsibilities. This improves productivity and onboarding, and it allows teams to migrate to AEM as a Cloud Service without unsupported customizations. Our Support case in Adobe: E-002518751 Expected behavior: 1. Welcome screen in AEM Author content and links can be defined per user group. 2. The configured URLs can be managed and updated after release, either through configuration in AEM Author or through a code/config release (for example, a Cloud Manager pipeline), without overriding out-of-the-box components. 3. URLs support locale placeholders.See our custom override examples on AEM on Prem.
Title: Hide custom fields from filter/view/grouping field pickers when the user has no access to the custom formCurrent behaviour: Field pickers in filters, views and groupings, including Browse fields in the new filter experience and enhanced lists, list every active custom field for the object type, whether or not the custom form is shared with the user. Restricted fields on access levels only blank out the values; the field names stay visible.Desired behaviour: Respect custom form sharing (or offer an access-level option) so that fields on forms a user can’t view are left out of field pickers entirely.Why: In multi-team instances, users are shown dozens or hundreds of irrelevant fields, which hurts adoption and causes confusion. Field names can also be sensitive on their own (e.g. HR or financial fields).
Applies to: AEM as a Cloud Service (author and publish)I ran into this while building a generic REST connector. You import an OpenAPI spec, authors set up a connector in /conf, and the data ends up in Content Fragments. The data side was the easy part. Credentials were not. Every API needs a secret, and on AEMaaCS a secret only reaches your code through OSGi config that ships with a deployment. So "an author adds a new API" quietly becomes "a developer ships a release", which defeats the point of a generic connector.This is the idea I came up with for that, and I'd like to know what you think of it.A quick word on where it stands. It's my own design on top of what Adobe documents, not an Adobe recommendation. I've compiled and unit tested the service class on a plain JDK, but I haven't run any of it on a real AEMaaCS environment. Adobe documents the local setup for placeholders (it uses the Felix configadmin plugin) but not how the cloud runtime resolves them, so wherever I lean on the plugin's behavior I'm going by its README and source. Worth checking on a dev environment before you trust it.The ideaInstead of one secret per integration, deploy a pool of numbered slots once: REST_SECRET_01, REST_SECRET_02 and so on. Each slot is a $[secret:...] placeholder in an OSGi config, sitting next to the hosts it's allowed to be sent to. The connector config in /conf only stores the slot name, for example "secretRef": "REST_SECRET_01". A small OSGi service looks the slot up when you make the call, and it only hands back the value if the URL points at one of that slot's hosts.For a host that's already declared, an author then needs a Cloud Manager variable and a connector config, with no code release. A brand-new host still needs a config change in Git. I'm fine with that, because the host list is the thing that stops a credential going somewhere it shouldn't.Declaring the slotsThis goes in your ui.config module. I only declare slots under config.author, since the sync jobs run there and publish is the internet-facing tier. Name the file after the component's class, so in my case com.example.restconnector.core.secrets.SecretSlotService.cfg.json:{ "REST_SECRET_01": "$[secret:REST_SECRET_01]", "REST_SECRET_01.hosts": ["api.example-weather.com"], "REST_SECRET_02": "$[secret:REST_SECRET_02]", "REST_SECRET_02.hosts": ["auth.example-stores.com"], "REST_SECRET_03": "$[secret:REST_SECRET_03]", "REST_SECRET_03.hosts": ["auth.example-stores.com"]}Why hosts per slot and not one global allowlist? With a single list, an author editing a connector could pair a token meant for API A with API B's host and send it to the wrong place. Per-slot hosts close that gap. They don't help against someone who can deploy code, since code can read any slot.Two things to keep in mind. Preview takes its OSGi config from publish (there's no config.preview folder), and config is resolved per PID from the most specific runmode folder, so you can't spread one PID across config.author and config.author.dev. Also, I set configurationPolicy = REQUIRE, which means the service doesn't exist on a tier with no config for it. The OSGi spec says a required configuration has to be present for the component to be satisfied. Anything on publish that references the service needs an optional reference.The serviceIt's one DS component. It keeps an immutable map of slots, swaps in a new one whenever the config changes, and its activate method takes a Map<String, Object>, the same as the secrets manager in Adobe's tutorial. getSecret() is the only method that returns a value, and this is the check that decides:if (!"https".equalsIgnoreCase(target.getScheme()) || target.getUserInfo() != null) { return Optional.empty();}if (target.getPort() != -1 && target.getPort() != 443) { return Optional.empty();}String host = normalizeHost(target.getHost());if (host == null || !slot.hosts.contains(host)) { return Optional.empty();}return Optional.of(slot.value);A slot counts as unset if the value is missing, empty, still the literal placeholder, or has a line break in it, so isSet() and getSecret() can never disagree. Host names get normalized on both sides (lowercase, punycode, no trailing dot) and have to be plain names, so no wildcards, paths, schemes, ports, underscores or IP literals. When an entry gets dropped, or a slot has a value but no usable host, it logs a warning, so a typo doesn't fail silently. A Unicode host in the URL won't match, so use the punycode form, because java.net.URI gives no host for non-ASCII names. It never logs a value. isDeclared() and isSet() are there for a status page.You need Java 10 or later because of Map.copyOf(). Cloud Manager builds with JDK 8 unless you set .cloudmanager/java-version, and Adobe's build page says that file should contain only 21 or 17.Using itBuild one URI, check the secret against it, and pass that same URI to the client, so what you checked is exactly what you call:URI target = URI.create(url);String token = secretSlotService.getSecret(connector.getSecretRef(), target) .orElseThrow(() -> new ConnectorException( "Secret slot " + connector.getSecretRef() + " is unavailable for this request"));HttpGet request = new HttpGet(target);request.setHeader("Authorization", "Bearer " + token);I build the HttpClient once on activate and close it on deactivate, with redirects off so a redirect can't carry the header to another host:client = HttpClientBuilder.create() .useSystemProperties() .setDefaultRequestConfig(RequestConfig.custom() .setRedirectsEnabled(false) .setConnectTimeout(1000) .setSocketTimeout(5000) .setConnectionRequestTimeout(1000) .build()) .build();The 1 second connect and 5 second read timeouts are what Adobe's development guidelines suggest. useSystemProperties() matters if you use a dedicated egress IP or VPN, because Apache HttpClient needs it to use the proxy. Whatever you do, keep the secret, the headers and any URL with credentials out of error messages and logs, and don't turn off TLS hostname verification.If an API needs two values, like a client ID and a secret, use one slot per value. Those slots only list the token host, and the access token you get back stays in memory.Then in Cloud Manager, create a secret variable named exactly like the slot, pick the service it applies to, and paste the value without leading or trailing spaces. Save once for all the variables you're changing.What to watch out forAdobe's docs don't quite agree on how a change is applied. The OSGi page says calling the API deploys new variables like a code deployment, and that author and publish restart, typically within a few minutes, without the quality gates. The environment variables page says changes take effect without code changes or deployments, and shows an Updating status. A KB article about preview-scoped variables mentions only Preview restarting, and nothing says what an author-scoped variable does. I'd test it on dev and schedule changes outside editing hours. If a variable sits on Updating for more than 10 to 15 minutes, KA-36282 says to look for stray whitespace in the name or value.On limits: names are 2 to 100 characters matching [a-zA-Z_][a-zA-Z_0-9]*, and INTERNAL_, ADOBE_ and CONST_ are reserved. Values can be 2048 characters, but the API reference says secretString values must be under 500. The number of variables per environment is 200 on the OSGi page (the 2020.7.0 release notes say it was raised to 200) and 400 on the environment variables page. I plan for 200. A pool of 20 slots uses 40 if each slot is set separately for author and publish.If no value is set, Adobe says the placeholder stays in place at runtime, so your code sees the literal $[secret:...] text. That's why the service treats it as unset. Placeholders only work in OSGi config. According to the Felix plugin README, a DS component gets resolved values, but code that reads ConfigurationAdmin properties directly sees the raw placeholders.For outbound calls, ports 80 and 443 are open by default. Other HTTP(S) ports need one of the advanced networking options and the documented proxy, and that page also recommends connection pooling.Anyone who can open the OSGi Components view in the Developer Console may see the injected values. Adobe doesn't say whether secret variables are masked there, so I'd assume they aren't, and I'd limit who has console access. To check whether a slot has a value, use your own isSet() status page rather than the console.This isn't meant for OAuth refresh tokens or anything else that changes at runtime, for credentials of around 500 characters or more (PEM keys, say), for big pools, or for changes that must take effect instantly, since every secret change is an environment update.A few habits I'd keep. Never log values, the activation property map or request headers. Restrict write access to connector configs under /conf, because anyone who can edit one can choose any slot. Use separate secrets per environment. Rotate by changing the value in Cloud Manager, which Adobe's tutorial says needs no redeployment, but values aren't versioned, so a code rollback can pick up a newer value. For risky changes, put the new value in a spare slot and repoint the reference. And when you replace a placeholder with a hardcoded value, delete the old variable too, because KA-27437 says AEM keeps preferring the existing secret until you do.Testing locallyAdd this to the end of crx-quickstart/conf/sling.properties and restart:org.apache.felix.configadmin.plugin.interpolation.secretsdir=${sling.home}/secretsdirThen create one file per secret in that folder, named exactly like the variable, with no extension. Adobe's OSGi page says all the secret files go in the same directory. Write each file without a trailing newline, for example printf '%s' 'value' > secretsdir/REST_SECRET_01. The plugin source trims whitespace, but its README describes the file contents as taken as-is, and a trailing newline would make the slot count as unset in this service.A Tools page for empty slots (idea for later)When several sites each keep their own connector configs, people need a way to see which configurations are still waiting for a value. I'm thinking of a small AEM tool, maybe under Tools > REST connector > Secret slot status, that lists each connector configuration, shows whether its slots are set, empty, unknown or missing, and names the Cloud Manager variable to create. It would only use isDeclared() and isSet(), so it never sees a secret value. That's just an idea for now, and I'll add details to this post later.That's where I am. If you've solved this a different way, or you can see a hole in the host binding, I'd like to hear about it.Docs I usedManaging secrets in AEM as a Cloud Service Configuring OSGi for AEM as a Cloud Service Environment variables in Cloud Manager Cloud Manager API reference Cloud Manager release notes 2020.7.0 Build environment of Cloud Manager AEM as a Cloud Service Developer Console AEM as a Cloud Service development guidelines Configure advanced networking KA-29983, preview-scoped environment variables KA-36282, variables stuck in Updating KA-27437, stale environment variables OSGi Compendium: ConfigurationPolicy Felix interpolation plugin README
If a task is pulled into an iteration, we would like to be able to move it back to the backlog...currently you can only Add to Iteration or Add to Kanban Board. Would like an option to Add to Backlog. There are times when tasks are not finished at the end of a sprint and we do not want to move them to the next sprint - we want to move them back to the Backlog. Currently, we must do a manual process: first we remove the pod name from the assignment and then manually add the pod name back to the assignment. That is the only way to get the task to the backlog. This is a waste of time.
DescriptionEnable OpenFeature providers (https://openfeature.dev/docs/reference/concepts/provider/) for the API/SDKs/languages you currently support. This would speed up the installation of Adobe Target server side by working on multiple platforms.Why is this feature important to youWe have built an Experimentation tool wrapper around the OpenFeature specification. We have multiple feature flagging tools across the enterprise and through leveraging the OpenFeature specification, we can bring the same context and tracking to all the tools. Also, we primary use Adobe Target for digital marketing experimentation, primary on the front-end. By supporting OpenFeature, other channels would be able to subscribe to Test & Control with minimal effort. Currently Target is not in the convo to support feature flagging and experimentation for other channels like IVR, Chat and App.How would you like the feature to workSee the OpenFeature specs: https://openfeature.dev/specification/Current Behavior - N/A
As the title suggests, enhanced lists functionality for Tasks and Issues (similar to the new experience on the Requests page).
Please add the ability to export email using the new email designer from the main view. Currently this can only be done by going back into edit mode. This is useful to have after the email had been published.
With our consolidated B2C, B2B & B2P instance/sandbox currently in production which includes Salesforce and Marketo account data via the native Marketo connector as well as batch ETL ingestion from our datalake. The result of this is duplicate account profiles with multiple/different primary & external source keys. Currently we have two options to manually correct for these duplicate account profiles: Option 1: Fix the Mapping Change the mapping on the Marketo side so that the “primary key” field (account key) for accounts brought in from Marketo uses the same format as the Salesforce/account data brought in via other sources. Example: If Salesforce/S3 uses 001xxxx...@salescloud.redhat as the account key, configure Marketo’s field mapping to use the same convention instead of the out-of-the-box 001xxxx...@<OrgId>.salesforce. This aligns the account keys from Marketo and Salesforce/S3, allowing AEP merge policies to recognize them as the same account and unite/stitch all attributes and relationships into a single unified profile. Option 2: Add a Shared Identity Field Create an additional identity field on the account schema (e.g., b2bAccountSharedId) and populate it with a value that both Marketo and Salesforce/S3 can map - so both sources submit a common ID in a new field, marked as an identity. You then configure this field as an additional identity namespace in AEP, allowing merge policies to stitch on either the classic account key or the new shared ID. Accounts originating from either source will have a shared secondary identity that can be stitched, even if the original (primary) field isn’t harmonized, and without disrupting existing integrations. It would be ideal for the ability for duplicate account profiles to unify and/or merge across multiple primary and external keys instead of the manual correction/workaround options.
In Planning, connected fields have Record Filtering Rules. When you are in a table and you click to select from the connected records in that field, you are only shown the ones that meet the criteria for those rules. Great feature! However, it does not apply to a Request Form built for that table. The filtering does not apply. AI Coworker confirmed this and said the best workaround was to manually filter your data set. That’s not good enough. I badly want to be able to apply filtering rules to connected fields/records in Planning. It seems like an oversight that we can’t do this now.
Pretty self-explanatory. I have a batch smart campaign that I need to run every hour on a daily basis with no end date. Since "hour" is not a frequency option, I had to create 24 recurring batch smart campaigns to achieve this result. I'd much prefer to manage this through on smart campaign, as opposed to 24!
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
