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. 

[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??