Workfront Planning - Request Form "Subject" Displayed in Record

[MLehman]

Workfront Planning Users - I need help! I have created a record type in Planning, and also created a request form for it. The required (not removeable) "Subject" field in the form, does not show up in the record when someone submits a new request. How do I get it to show up?

It's odd to me that there is a Name field that can't be removed from the record or mapped to the subject field, which also can't be removed from the request form, but also is not visible in the record. Anyone figured this out? 

Thanks!!

[kautuk_sahni]

@monicacardoso @_Manish_Singh @Lyndsy-Denk @Pan_Shahbazian @KristenS_WF Would love your thoughts on this question whenever you have a moment. Your perspective is always helpful!

[MLehman]

Thanks! I have discovered I CAN remove the subject field from the forms. But the question still remains, if you can't see it in the record, what is the purpose of its existence?

[Pan_Shahbazian]

Hi there! GREAT question - this is actually a common point of confusion with Workfront Planning request forms. The subject field behavior you're experiencing is actually documented functionality, not a bug (whether I'm a fan of this 'feature' is another thing entirely). 

In terms of why it exists... I think that'd be a good question for the product team, but in terms of the technical reasoning:

Workfront Planning request forms are built on top of Workfront's traditional request system. When someone submits a Planning request form, it actually creates TWO things:

1. A traditional Workfront request (which needs a Subject for identification in the Requests area)
2. A Planning record (which uses the Name field and other mapped fields)

[MLehman]

Oh, this is very interesting! If it creates a Workfront request, are those accessible? Where would I find them? I have created a couple Fusion scenarios to move a request from Planning into Workfront Core, but if we can access the Workfront record that's created automatically, it could eliminate the need for Fusion. Thanks for the response!