Removing the Subject field from the Request form | Community
Skip to main content
E
Exp_-_VazgenBa
Level 6
May 23, 2019
Question

Removing the Subject field from the Request form

  • May 23, 2019
  • 76 replies
  • 10097 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!
    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

    76 replies

    Show previous replies
    S
    SusanPf
    Level 9
    June 19, 2019
    I just put a complaint into Marilyn and Sharleen. This should not take place directly into live environment. Susan
    K
    KatherineHa1
    Level 8
    June 19, 2019
    Love this William!!! Katherine Haven, PMP VP, Director, Business Technologies - PMO FCB
    E
    Exp_-_VazgenBaAuthor
    Level 6
    June 20, 2019
    Hi everyone, The changes have been reverted and the label "Subject" has returned. We will return to solving the confusion problem in the scope of a general initiative of enhancing Workfront intake solution. Thank you for taking time and providing feedback on the change! Thanks, Vazgen Babayan Product Manager Workfront
    Christina_Jarosz
    Christina_Jarosz
    Level 9
    September 23, 2019
    Hey Vic - can you tell me more about that API? Sounds interesting!
    V
    VicAl1
    Level 10
    September 23, 2019
    Hi Christina, Well, it's been magical �� . Not to exaggerate but it's really been suuuuuuuper helpful to us in many workflows. Renaming Requests is one of the easier ones. We've also moved data from the form to the Description of the Request so users don't have to open the form and Approvers (who aren't usually in WF) don't have to know where the form is. We're up to 139 workflows we've created with it such as: Converting a New Hire Request into a Project with many tasks (and removing the tasks that aren't needed based on what was selected in the form)). We just finished a Project "Hygiene" Score workflow that I might submit to speak about at Leap. Basically, it checks your plan for whatever things you want to flag (i.e. incomplete tasks with dates in the past, unpaid Expenses with dates in the past and so on). It allows our PMO to see if your project plan is up to date by just looking at a report. Then we'll write a job to automatically comment to the Project Owner that their Project Hygiene Score needs to be fixed. But it needs to be coded obviously. I'm fortunate enough to work in IT and have an awesome developer at my convenience. And they've coded it to be data driven so I can create jobs without them having to do coding changes all the time. But basically if I can dream it, they can make it happen (just depends on how long it might take depending on the complexity). Feel free to give me a call or email me directly if you want more info.
    B
    BobSl
    Level 3
    September 24, 2019
    And for those less fortunate than Vic, who don't have a tame developer at hand, there is always Fusion, which provides code-free API functionality which we are starting to create significant value with in similar areas such as renaming projects based on data entered on custom forms... Regards Bob
    Terms & ConditionsAccessibility statement

    Loading footer...