Skip to main content
Level 6
May 23, 2019
Question

Removing the Subject field from the Request form

  • May 23, 2019
  • 76 replies
  • 10118 views
Hey everyone, >Renaming the Subject field on the request form is currently one of the top-voted items for the Idea Exchange. We are currently debating an option to automatically generate incoming request names using a predefined naming convention and remove the Subject field from the request form altogether. There are several options we're thinking of for the naming convention, so your feedback will be invaluable for us to understand whether we are close with our hypothesis or completely off track. If you could please fill up the form below, that would help us immensely!

76 replies

Level 3
June 19, 2019
As we are on the subject, I know this has been asked in the ideas exchange, but it would also be a great help to be able to embed this field and the other "Queue Specific" fields (such as Attach Document) into the main body of our custom form. It would make the form we are asking users to fill out a lot more logical...…. Jonathan Thain BT Group
TamBou
Level 5
June 19, 2019
Hello @Vazgen Babayan , I have completed your survey here. To provide the requested feedback, we're in the process of onboarding our internal power-requesters (soon) and this change was made right before their training session - prior to that it was testing and introduction. I met with them last Friday and warned them about this change and they seemed to get it. Then I met with them again today to do the walkthroughs of them submitting requests and their presumption for that field was to put their name. Like Skye mentions below our end users/stakeholders also will likely avoid training and won't then get clarification on that field. At minimum put a descriptive alt/hover text for them to see what is needed. Tammie Tammie Bouchard National Safety Council
TamBou
Level 5
June 19, 2019
Yes, this. Our people are confused by the Name field We would have issues if the name generated the same thing for each request - need them to be unique. The consistent task names are already an issue in the scheduling area and some lists. Like Skye mentioned We need the auto numbering option for job We would find value in connecting to pre-existing field on the custom form as Skye mentioned. I read that Workfront will be reverting this change. Not sure where that leaves all those that requested a change, not likely this change, but a change to that field. Tammie Bouchard National Safety Council
PK717
Level 2
June 18, 2019
We are experiencing the same issues. People are now putting their own name in for the project. I can see changing the name of the line, but not to the generic "Name." Project Name or Project Title are more descriptive to what is needed. This change is causing an unacceptable amount of work as we now have to rename every project request. Please either change it to one of the above or allow admins to rename the field themselves. Thanks for listening, now I'll wait for your doing. Karen Adams Karen Adams MK - Marketing and Communications
PK717
Level 2
June 18, 2019
We are experiencing the same issues. People are now putting their own name in for the project. I can see changing the name of the line, but not to the generic "Name." Project Name or Project Title are more descriptive to what is needed. This change is causing an unacceptable amount of work as we now have to rename every project request. Please either change it to one of the above or allow admins to rename the field themselves. Thanks for listening, now I'll wait for your doing. Karen Adams Karen Adams MK - Marketing and Communications
Level 10
June 18, 2019
To add to Bob Sleigh's comment #2: Rename any, or at least more off, the system fields so they'd be more useful. I already think it's cool we can rename so many interface elements, this would be a plus. Something that has had limited traction in Idea Exchange that could be implemented at the same time is the idea of a "coding field name". Don't know the proper term, but it's the idea is the field "name" that the user sees (which in our case is often long-winded sentences or questions) is separate from a behind-the-scenes name we can assign. So for custom fields I could have a field "What is the expected customer response?" but I can customize it's name when doing reports and calculations to "cust_response" or "custResponse." For system-level fields, this coding name could be displayed and greyed-back to show the admin what it is, but not change it, for example. So "Subject" could be renamed "Title" by admins, but might remain "wf_Subject" behind the scenes. Kevin Quosig
Level 3
June 18, 2019
And I'd like to re-iterate and expand on what others have said - 1. This change should never have been implemented into the live environment, and it concerns me deeply that Vazgen, and presumably others have the ability to make this change without any further oversight, which should have stopped him when he proposed to deploy straight into live. What could have been the impact if this was a malicious insider attempting to damage the product? 2. What BT want (and it appears many others feel the same) is the ability to rename the Display name of ANY field to something which makes sense locally (we can do this in reports, so why not in forms) 3. Some method of generating an auto-created request name may be of use to some companies - but it must be optional and in control of the local administrator, as must the removal of the "Subject" field (or whatever the local admins have decided to call it in their instance) Most importantly I'd like to know urgently how Workfront are going to make sure this type of untested change cannot happen again Regards Bob Sleigh BT Group
Level 3
June 18, 2019
Hi All Just to add our take on this, we have now had an influx of requests that have used their actual name in the name field. Again our requestors have minimal/no training in order to put a request in to us so even a slight change like this causes us issues with the quality of information we receive. A custom label for this field is what we require if we have no control over changes like this, or a calculated field based on what we are asking to be filled out on the form. Glad to hear it is being changed back in the interim. Thanks Jonathan Thain BT Group
Angie_S
Level 3
June 17, 2019
I'm so glad to hear this is going to revert! Got my first request titled with someone's full (middle initial and everything!) name this morning, ha ha. Admittedly it's not someone that uses Workfront a ton but she is a repeat requestor so I find it interesting that she didn't question the field change and just charged ahead with entering her name. Happy Monday, everyone! Angie Simon CUNA Mutual Group
AileenTa
Level 5
June 14, 2019
I'm wondering why this didn't at least get posted to the Product Announcement section or posted as a product announcement? What is Workfronts process for notifying customers of changes? The last announcement I received was June 6th. > Aileen Taylor Cell Signaling Technology