Q4 Update Request Enhancements-Thoughts on This?

[CBuckwal]

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!

[skyehansen]

if y'all are ok with it, I'm going to move this under the discussion for the new req experience, so Vazgen can keep better track but also... you might want to submit a case to WF Support.

[Tracy_Parmeter]

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?

[Halie_Baer]

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. 

[CBuckwal]

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. 

[JustinRenteria2]

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.  

[CBuckwal]

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. 

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

[MegSVT]

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]

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? 

[ChristinaRe1]

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]

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. 

[KatherineLa]

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. 

[PollyCo]

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]

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

[ConnorO2]

@PollyCo I tried setting up filters today that I would like to put on the layout template but the Entered By ID doesn't allow wildcard filters. 

I'm just trying to understand what the whole thought process of these new UX changes are for. 

Really wish time and energy would be put into other features within Workfront.