What is the point of People fields in request forms?
Why can't custom fields of type People be populated by responses in a request form? Any question you are allowed to use in a request form should be able to be mapped to a custom field.
Es sieht so aus, als hätten wir die übersetzte Seite, nach der Sie suchen, nicht, aber wir haben andere Inhalte auf Englisch und bieten Unterstützung in Englisch.
Wobei können wir Ihnen helfen?
Lernen. Teilen. Diskutieren.
Why can't custom fields of type People be populated by responses in a request form? Any question you are allowed to use in a request form should be able to be mapped to a custom field.
Folllowing List for Post: What is the point of People fields in request forms?
[this list is visible for admins and agents only]
Hey Chris DeFelice!
I just noticed your post and I hope I interpreted it the right way:
I just tested this and can confirm that if you have an Assignee question type in a Request Form, you can map it to a custom field - however, that custom field needs to be set up as a People-type field.
The configuration only reads users from the Account (vs. something like free text or single/multiple options), so it makes sense that the question type and custom field type need to match (in this case, they are called slightly different terms "People" vs. "Assignee").
Piece of product feedback based on this from myself would be to match the terminology so it's interpreted as the same ("People" custom field type does not match "Assignee" question type on Request Forms).
Ah ok so it does work. I guess it wasn't showing as an option for me thanks to visibility between spaces and custom items in one space with a request form in another space. Thanks!
Chris DeFelice no problem! I didn't test if it was a space-specific custom field and request form, I just tested it as account-level custom field and request form and it works that way so I guess just keep that in mind :)
Have a great weekend!