Build better products with our product team
Request for Feature Enhancement (RFE) Summary: Standardize the time zone display for workflow-related “Start Time / Start Date” across all AEM as a Cloud Service authoring UIs (Workflow console and Inbox) so that they are consistent and user-friendly for business users. Use-case: Business users frequently monitor and operate workflow instances (e.g., publication approval flows) from the AEM author UI. Currently, the “Start Time / Start Date” of the same workflow event is displayed in different time zones depending on the screen: • Workflow instance list vs. workflow instance history • Inbox list vs. Inbox item detail This inconsistency causes confusion for operators, makes it difficult to correlate events between screens, and increases the risk of miscommunication when discussing schedules (e.g., “when was this request actually started?”) with non-technical users. This affects daily operational work for multiple business users who coordinate publication schedules, and the confusion around timestamps has already led to repeated internal inquiries and additional verification steps. Current/Experienced Behavior: For the same workflow instance / work item, the time zone of “Start Time / Start Date” is not unified across screens: 1. Workflow instance Start Time • Tools > Workflow > Instances > [List] ◦ Start Date is shown in UTC (e.g., 4/2/26, 3:06 AM) • Tools > Workflow > Instances > [Individual Item] > Open History ◦ Start Date is effectively shown as JST / user’s local time in the tooltip ‣ e.g., title="Thursday, April 2, 2026 at 12:06:18 PM Japan Standard Time" 2. Work Item Start Time / Start Date • Inbox > [List] ◦ Relative time and tooltip are shown in JST / user’s local time ‣ e.g., title="Thursday, April 2, 2026 at 12:06:18 PM Japan Standard Time" • Inbox > [Open individual item] ◦ Start Date is shown in UTC in ISO-8601 format ‣ e.g., Start Date: 2026-04-02T03:06:18.238Z From a user’s perspective, even though all of these timestamps refer to the same workflow event, some screens show UTC while others show local time (JST), without a clear indication or consistent labeling. This is perceived as inconsistent and confusing behavior rather than an intentional design. Improved/Expected Behavior: The “Start Time / Start Date” for workflow instances and work items should be consistent across all AEM authoring UIs, including: • Tools > Workflow > Instances (list and detail/history views) • Inbox (list and individual item views) The core expectation is that the same workflow event should not appear with different-looking timestamps across screens without clear indication, and that operators can reliably interpret times without needing to mentally convert or guess the time zone. Ideally, all workflow-related timestamps in the authoring UI should be shown in the user's local time zone (based on profile or browser locale), with a clear time zone indication in the tooltip or label. At minimum, the same workflow event should use the same time zone and a consistent format across all related screens, so that operators do not need to mentally convert or guess the time zone. Environment Details (AEM version/service pack, any other specifics if applicable): Adobe Experience Manager as a Cloud Service Customer-name/Organization name: ASAHI KASEI CORPORATION Screenshot (if applicable): Code package (if applicable):
We'd like to be able to create a report based on users tagged in updates/notes. For example, if someone tags me or my team in an update, I'd like to have a report on my dashboard where I can see and address each one. Since we cannot customize the in-app system notifications, simply tagging a user in an update is no guarantee that they will actually see it. Our workers have hundreds of updates flooding in each day, so for the most part the entire notification system has become useless for this purpose. Although our workers each have the email notification setting turned on for when they/their team is tagged, those emails don't always come through, making it a spotty system at best and not reliable for ensuring each tagged update is addressed. With a report filtered by who was tagged in any given update/note, my team can trust that they're not missing anything important. Bonus points if there can be a way to "dismiss" updates that don't require a response (so that they don't clutter the report with irrelevant information).
Description - Custom home widget to add reports & dashboardsWhy is this feature important to you - Ability to see daily reports on homepageHow would you like the feature to work - custom widget to pull in selected reportsCurrent Behaviour - N/A
Request for Feature Enhancement (RFE) Summary: Make it possible to hide the video download button. Use-case: If you embed a video directly instead of using a YouTube video Current/Experienced Behavior: The options menu will always be displayed. Improved/Expected Behavior: You can toggle the display of the options menu. Environment Details (AEM version/service pack, any other specifics if applicable): Experience Manager as a Cloud Service Customer-name/Organization name: asahi kasei Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: It will be possible to set links from the same domain to open in a new tab. Use-case: When setting up a link within the same domain Current/Experienced Behavior: It's not possible to determine whether the `target=_blank` setting is enabled or disabled, so transitions within the same domain always result in transitions to the same tab. Improved/Expected Behavior: You can toggle the setting of `target="_blank"` for each link. Environment Details (AEM version/service pack, any other specifics if applicable): Experience Manager as a Cloud Service Customer-name/Organization name: asahi kasei Screenshot (if applicable): Code package (if applicable):
Description - Currently, when you share a document folder on a project template with a group / team / individual, or choose to not allow inherited permissions, when you create a project those same permissions set do not carry over. However, part of the purpose of templates is determining permissions to be on the created projects, so this setting not carrying over doesn't make sense...Why is this feature important to you - We need the ability to restrict access to certain document folders and should not have to do it on each project, but rather at the project template levelHow would you like the feature to work - Created projects should receive the same folder permissions set on the project templateCurrent Behaviour - Projects created from templates do not retain the same folder permissions set on the project template when created
When a custom object that is part of a CRM sync has been changed, it needs to be disabled and reenabled in Marketo to recognize those changes. However, the system requires the objected to be disconnected from everything it is used in. This makes it impossible to change an object when it is used widely as we not only have to disconnect it from everything, but then reconnect it once the object is re-enabled. Ideally the object could be disable and re-enabled without disconnecting it, and then any conflicts created by the changes to the object could be highlighted.
At my organization, we have several shared tasks within project schedules. The users on these tasks are half individual assignments and half team queues. When teams assign users from their team queues, it will remove the original “primary assignee” on the step. I would love to see this logic removed from shared tasks as it causes many issues for the way that teams operate.
We would like to add user fields to a custom form that we use in request queues that will prefill based on the request's primary contact. For example, we would take populate fields for the user's phone number, email address and location based on who the primary contact is. There may be ways to make this to work after the request is submitted, using tokens, but we would like the fields that prefill to have the ability to be changed it if the information is incorrect.
Having a typeahead field that is bringing in Portfolio Names is great because now we don't have to maintain a separate dropdown field with the Portfolio Names as new ones are added or old ones marked "InActive". The problem is that I have other fields that need to display based on the Portfolio selected and I don't want other fields to display when that Portfolio is selected. Allowing display logic to use the typeahead field is a great next step.
I apologize if this is duplicate but I did not see it anywhere. We have a need to create parent projects that would live between the Program level and the current project level. While I understand that the work could be completed in one project using parent/child tasks we have many departments that would prefer to have their projects tracked separately. There would be many child projects which would roll up to many parent projects and into ONE program. I saw some talk about this on the Global forum but that was it. Please help me vote up this feature request! Thanks!! Michael
Recently, deactivated users can now be assigned to things. Why this would be helpful escapes me. Why this would be harmful is obvious.Let's say I accidentally assign a really important task to a deactivated user, guaranteeing it will be ignored… and late. A great way to anger a client.I cannot think of a single good reason to assign anything to someone who does not work here anymore and will absolutely, 100% not fulfill the request.
Description - Slack module/addonWhy is this feature important to you - AlertsHow would you like the feature to work - Allow workflows to trigger alerts to slack, an extra option in the workflow properties to configure under which state an alert will be triggered, also, enhance current workflow "Alert activity" to choose between email or slack alert or both.Current Behaviour - non I've seen clients developed their on integration with slack for monitoring purposes, but it would be nice to have a native module.
Description –Currently, assets such as audiences and activities created via the Audience API or Activity API in Adobe Target cannot be edited in the Adobe Target UI. Why is this feature important to you –Our customers want to use AI to create audiences and activities automatically. However, there are cases where they need to review and manually edit these assets later in the Target UI. The inability to do so limits flexibility and usability for marketing teams. How would you like the feature to work –We want assets created via the Audience or Activity API to be editable directly in the Adobe Target UI, just like those created manually within the interface. This would ensure consistency and allow users to make adjustments without recreating assets. Current Behaviour –Assets created using the Audience API or Activity API are not editable through the Adobe Target UI. Any updates or modifications must be done programmatically through API calls.
When using custom quarters, reporting is inconsistent. If you filter for a custom quarter, your timeline ends at 12:00am on the last day of the custom quarter - meaning anything dated the last day of the quarter gets missed in the report.If you filter for a longer period of time and group by quarter, the items that are dated the last day of the quarter properly show in the correct quarter. This inconsistency was reported to support but development stated it's not a bug or oversight so it's here in the innovation lab hoping to get some traction to be addressed properly.The correct functionality should be that custom quarters throughout the system all use 11:59 PM as the timestamp for the custom quarter end date instead of 12:00 AM
This is something that we had in a past chat program that just helps when you are setting up your targeting. After you put in your URLs, you were able to grab a URL from the site and it would verify if the bot would show up. It wouldn’t take any of the other criteria into account (which is fine), but it helped if I put in website.com/blog* to ensure it shows up on our blog posts, then I had a field where I could pop in a blog URL to double check that it was set up correctly. It’s a bit painful that we can’t verify we set it up correctly until it is live and then if we have other filters (i.e. must be in Canada, but I’m in the US) then I can’t verify until we start to see reporting on if it is working or not.
When we add new assets into the DAM the system creates renditions of those assets for use by AEM. We also create custom renditions for use by our users. When users view and asset or click to download it they see all of our custom renditions PLUS the system renditions. Given that the system related renditions are soley for the use of the AEM platform, can we please hide those from our view so they are not noise for our end users?
Description - Many times database connection on Query Service get disconnected due to various reasons (limit of users reached being one of it). This affects the focus work as it disrupts the query execution, to avoid it User should have a connection refresh button which will allow the Database connection to be re-established without having to refresh the entire browser multiple times.Why is this feature important to you - Helps users to continue important focus query time without disruptionsHow would you like the feature to work - A simple refresh button the page should reestablish the connection to the database.Current Behaviour - Users need to copy the entire query and refresh the browser, it clear all the query results previous queries might have returned on the browser.
Description - Many of our users are expressing pain points when it comes to finding specific information related to communications made on a project. Why is this feature important to you - Having transitioned from Outlook and Teams for project communication, users are used to having the ability to track down keywords and important info with the use of the search capabilities. How would you like the feature to work - Add a search button and field on the Updates Page in each of the elements of Workfront, ie. Projects, Task, Issues, etc. This search function would be able to show the updates that contain the Searched information. Current Behaviour - Currently, in Workfront, users are having to use valuable working time to scroll through sometimes lengthy Update feeds to try to find the necessary info, which is made more difficult by the auto-collapsing functionality of threads. Thanks for the consideration!
Description: Increase the size of the Descriptive Text Field while typing in it in a report. Please make this field taller while editing. No matter how many lines of text, the edit function in a Report view makes it ~7 lines of text for the height currently.Why is this feature important to you? Our MPMO uses text fields in reports daily to document key project updates, tasks and hot topics. As we continue to move more and more into Workfront, we will continue to use Descriptive Text Fields. The current size of the text field makes users have to scroll a lot to get to their desired area of the text field which causes a clunky experience for users.How would you like this feature to Work? The request is to increase the number of lines of displayed text while typing. It would be great to have the text function realize what size the cell is already and adapt to display that many lines. For example, if the field has 20 lines, then display the 20 lines of text without shrinking the field for editing.Current Behaviour: No matter how many lines of text, the edit function in a Report view makes it ~7 lines of text for the height.
Currently it is very slow to go from seeing an unpublished draft in a list view to having it published. click it (then wait) then click draft (then waiiiiit) then click publish (then wait).This takes a long time if there’s a few things that need to be published. Why not just add a publish option to the … menu?
We use this as our screen to send proofs to team members and discovered this messages box, which is great because we always want to send a note with the proof. We get the message with our email proof, which is great! It took us like 5 clicks to find the message back in the document in Workfront…. The message is not showing in the project or document updates. This would be a huge help for my team to have those messages flow into the updates of the document and project. It feels like if the updates is a comprehensive stream of the project, not having the proof message flow there is a miss. Thank you!
Current status: when you build a multiple data blocks in the same Excel file using report builder, it can sometimes be difficult to distinguish between them. It is currently possible to group them based on metrics, dimension, or what sheet they're on. But if you have multiple data blocks with all the same components but just different date ranges, it's very difficult to tell them apart in the list of data blocks. How the feature should work: when making a data block there should be an option to give it a name. The ability to name data blocks will allow users to more easily distinguish between similar data blocks and make it easier to maintain their reports. Why this feature is important: the new report builder has been such a huge upgrade from the legacy version, but it can still be improved upon. Having named data blocks will make it easier when trying to maintain reports and share them with others.
Take information from Workfront planning to pull into WKFT core reports
Sometimes I get lost trying to figure out how to publish something in the New Email designer in Marketo – it seems like the button just isn’t there.After a while I realise there is one, but in a different spot and not outlined or coloured, so it just looks like some text.Then a few months later I get back to using Marketo and forget about it and have to hunt for it all over again.The publish button usually looks like the first image, but sometimes it’s somehwere else like in the second image. I have no idea what differentiates these two types and why there is a need for it to be different, and why these actions are included in a ‘summary’ and not ‘actions’ or similar.It seems like it would be better to keep them the same, or at least in the second screenshot give the buttons an outline so they actually look clickable and stand out more.
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.
