New Participant

Q4 Update Request Enhancements-Thoughts on This?

Forum|Forum|6 months ago
September 3, 2025
13 replies
2634 views

In reviewing the Q4 Update documentation, I came across the new look for requests in preview. I can still see the old request page, but there is an option to "Use New Experience." The new requests page removes the option to change the Requests page layout. We have a Requests management report for users to track their requests that is very customized to our workflows. The new Requests page doesn't really meet our workflow needs and will seem confusing to our users.

From the documentation, new Requests seems to only be available for unified experience instances after the Q4 update. Our production instance is not on unified experience, but our non-productions instances are on unified experience. We don't have Planning now, but the documentation relates that the Request page change is an attempt to bring Workfront Planning and Workfront Requests together.

Will the new Requests page be mandatory at some point? Will the "Use New Experience" option be available to my non-unified experience production instance in the Q4 update? This isn't a great change for my company so we would like to understand the mandatory timelines better for this change and know what our users see on the Request page after the Q4 update is complete. Thanks!

P

PollyCo

New Participant

So this new toggle for the request/issue UX is another change that Workfront is forcing administrators to accept. The problem is that we can' t toggle that off for our users or ensure that our users don't even get that option. The UX is very disconnected to our overall user experience as the page does not look like what our other pages look like. What's the use of the layout template? The new UX is not controlled by the layout templates. They don't keep the available filters on the original page or layout we have so the new experience look so messy and then my users are lost on how to navigate the UX.

Anybody else having issues with this and how do they set up filters for users in a layout template?

Kurt_Jones

New Participant

I do know this feedback has been provided to the Product team to consider; it's having the same affect for most of us.

JustinRenteria2

New Participant

Has anyone been successful in obtaining a list of users who have enabled the New Requesting Experience from Adobe? Our support person told me no such list exists but wondering if anyone else has heard differently.

K

KatherineLa

New Participant

In order for the UI to correctly display any given setting, that setting MUST be saved somewhere that can be cross-referenced with the user's record. That collection is the 'USERPF' collection, and you're looking for the attribute "enable-unified-requests". It will be true if they have that toggle turned on.

MegSVT

New Participant

I've skimmed through many of these comments and perhaps I've missed it (apologies in advance), but I am wondering about the "copy" function in the current experience and why has that disappeared in the new experience? Am I missing something??

EmeraldWe

New Participant

Our group is also missing the "copy and resubmit" function, which is critical to the way we do work. Has anyone heard if this feature be permanently removed in the new experience?

C

ChristinaRe1

New Participant

Yes, thanks @megsvt and @emeraldwe for bringing this up - our team submits many similar requests and needs the copy function - if that is removed it will be a huge step backwards.

JustinRenteria2

New Participant

I'm really disappointed that this unfinished experience is being forced onto our user base. Looking at it this morning, I noticed that users cannot close the "New Request Experience" dialog box without being forced to enable the new experience.

C

CBuckwalAuthor

New Participant

Thanks for pointing that out. We already sent out user communication to prep users for the new request view and instructing the user to use the "skip" option. To remove that option 2 days before the release and after the Release webinar is really not helpful or useful. Forcing users to see unfinished functionality is a detrimental practice for user adoption.

@vazgen_babayan Please add the "Skip" button back to the new request experience popup today so users will see that option in the Thursday production release.

Halie_Baer

New Participant

Are other people struggling with the "Converted to" Column in the new experience? I assume it would now populate in the "Created Object" column, but mine is showing blank on all issues.

C

CBuckwalAuthor

New Participant

I checked with support on the Created Object and Status columns on the new request page, since they don't match up to what can currently be seen in the old requests page. Support response is below.

-The status shown in the list represents the Request object's status, while the issue itself may have a different status.

-The Created Object field refers to the object generated when an intake form is submitted. For Planning forms, this corresponds to the record created in the associated record type.
-In the new UI, there’s currently no way to view the converted object relationship. The Created Object column remains empty for Workfront issues, as this is by design and not related to the Converted To column from the old experience.

The new requests page and widget are not useful at all and actually confuse users since there is no converted object showing and the request status showing isn't the request status that users want to see.

Tracy_Parmeter

New Participant

We currently have the toggle switch to use the new request experience but we are wondering if there is a planned date to sunset the previous request experience?

A

AdrianoMe

New Participant

Any new Requests are currently displayed as "In Progress" in the new Request experience, even when they have not yet reached an In Progress status. This discrepancy causes significant confusion for our users due to the mismatch between the status of the Request itself and what is shown on the Requests page. For example, as illustrated in screenshots 1 and 2, my test request appears as "In Progress" on the Requests screen, but when you view the Request details, the status is actually "New."

Additionally, in the New Request Experience, when filtering by status (refer to screenshot 3), the available options are:

- Completed
- In Progress
- Rejected
- In Review
- Pending Review

Out of these, we only utilize Completed and In Progress, and there are several statuses we use that are not represented. To improve clarity, the filter options on the Requests page should include all active Issue status options, similar to those available when filtering Issue status in a Report. Furthermore, the status displayed in the status column on the Requests page should accurately reflect the current status of the Request.

V

vikkigibbs_ibm

New Participant

Hello,

I'm wondering if the screen shots you attached of the 01 Request screen status is showing a report/custom dashboard view, rather than the standard Workfront Request page as that has fixed column headers as per below & they don't match the ones in the screenshot;

If you're looking at a report is it possible you aren't filtering to the Group which has the statuses created that you expect to see, e.g. the Group used on the Request queue project. Another area to check is in Set Up>Groups>Statuses - check the statuses are set up for Request rather than Issue as per the screenshot.

Kind regards

Vikki

Vazgen_Babayan

Employee

Hi everyone and thanks for the feedback! We have captured it and it already is being reflected in our priorities and solution design moving forward. I am really grateful for all the provided context, notes and screenshots - they help us a lot as we enhance the product!

I also want to provide insight into the roadmap we have for the Requests page in the context of the current enhancements. The enhancements to the Requestor experience are the first in a series of improvements planned for the overall work intake capabilities of Workfront. These include:

1. A new "request" object, which is connected with the work objects it spawns, so that there can always be a clear picture of where the request is in its journey.

2. Ability to submit not just Issues, but other objects in the system, like Projects, Tasks or Workfront Planning objects, with approval processes gating the creation.

3. A centralized "Submitted requests area" which not only combines the Worflow and Planning requests, but also will have the support for custom views and Layout Template controls (both currently being worked on by the team).

4. The "Recently accessed request forms" capability, surfacing the recently used forms for quicker access

5. The centralized "search" picker will evolve from being just a search of existing queues toward an AI-native prompting capability, allowing to not only find the right queue but also populate the form based on the prompt or an uploaded file (also currently being worked on).

6. Redefined queue management system, evolving from queues being Projects in the system but toward a dedicated object, with enhanced routing, allowing spawning multiple objects as a result of a single request (planned for 2026).

Overall, the main objective of enhancements to the Requestor experience are targeting to greatly decrease the time it takes to submit requests, while not only preserving the same level of quality of the input, but raising it through an AI-supported experience. The improvements to the Administrator (or Queue Manager) experience are targeting the different levels of automation and approvals for the request routing and creation of target objects, decreasing the time it takes for the request to end up as a work object, reducing the need for Fusion for converting Issues to Projects.

Hope this helps provide insight into the direction we are taking with the Requests page. We are actively enhancing the page and believe that even in its current state it can provide additional benefit to the Requestors via a quicker search of the queues and recently accessed forms. At the same time, we realize that the solution is not in a state to replace the existing Requests experience, hence we have provided a toggle, which is OFF by default and allows to switch between the experiences at will.

S

ScottMo1

New Participant

Hi Vazgen - I appreciate the willingness to share what can regarding the roadmap for the Requests. I would like to start with your last comment. Correct, at the moment it can be toggled, but as many other functions that have a toggle - it will eventually move to the new experience without option.

Reading through your explanation, I am concerned that this is being designed with a strong Marketing Workflow influence. What is being created may not necessarily work well for your non-marketing customers. I would be cautious on what is being developed and launched as I don't think Adobe would like to start alienating other users.

But, in fairness to you and your team, I have not been on any development calls to understand the impact of these changes. If you would like me to participate as a 'non-marketing' voice, I would be happy to provide feedback at anytime.

K

KatherineLa

New Participant

Acknowledging that I'm a bit late to the discussion, but my org concerns align with Scott's here. We are not a traditional marketing org so some of these changes are all negative updates without any upside I can use to get my team onboard. I'm happy to participate in any brainstorming/product sessions to share our perspectives as well.

_Manish_Singh

New Participant

Few suggestions:

The form looks compressed in terms of width, 50% screen is empty. The form should take at least 80% space in the new window.

"+" button is nearly invisible. Change it to empty box, similar to what we have in report filter for consistency.

New request experience can be improved. Large font, more space between two queue options. It would be better if "What request do you want to submit" can be replaced with a button. The box seems more like a search rather than a new request button.

This is not necessary. Can be removed to have more space for existing requests.

S

ScottMo1

New Participant

@jerflo I am in full agreement. The Request Enhancements are not user friendly for our teams. We are in a manufacturing environment, and the Request are vital to the execution of our projects. The Request Enhancements is confusing and does not make sense for the workflow of our teams.

In addition, the users have no idea what "Request Form" means. The way we have our Request set up, they go to a project. But even changing the Request Form to Project is not helpful to the Users the way that we utilize Request.

I also agree with the point about losing the left pane - this is used by our teams as well to quickly navigate to requests that are important to them. The filter options are very limiting, and the summary area is now gone.

Please do not push this enhancement forward as a required upgrade - it needs a lot more work before it is user friendly.

Show more replies

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded