Mapping Responses in Request Forms
|
Availability: Legacy Business, Legacy Enterprise.; Unavailability: Legacy Free, Legacy Professional.; |
|
Availability: Team, Business, Enterprise, Pinnacle. ; Unavailability: Free; |
Space admins can manage request forms in their spaces. Account admins and owners can manage account-level request forms. On Enterprise accounts, this right can be revoked from account admins.
When you map responses, you tell Wrike where an answer should be displayed in the created task or project. For example, if you add a short answer field and map it to the title, then responses in that field are used as the task or project's title.
Answers from request forms can be mapped to:
-
Titles
-
Descriptions
-
Start/end date
-
Attachments
-
Importance
-
Custom fields. By default, space forms can only use custom fields from the same space and/or the account-level custom fields. If you choose additional spaces in the "Other spaces" in space form settings, this will allow you to use custom fields from those spaces. The form would still belong to the original space.
-
Add a question.
-
The question is mapped to Description by default (unless it's an attachment or importance question).
Note
File attachment and importance questions are mapped to attachment and importance fields respectively, and those mapping options can't be changed.
-
Click the dropdown next to Add answer to to see other mapping options.
-
Toggle one or more appropriate options.
In Single answer and Multiple answers questions you can quickly map responses to single-select or multiple-select custom fields respectively using the Use custom fields as options button. The options are based on the custom field, so to change them, you would need to edit the custom field options. Alternatively, the options can be created manually.
|
Question type |
Mapping options |
|---|---|
|
Single line text Paragraph |
Title, description, or text-type custom fields |
|
Single answer |
Title, description, single-select-type custom fields, or link to database custom fields. ImportantOnly single-select fields can be mapped to a single answer. |
|
Multiple answers |
Title, description, multiple-select-type custom fields, or link to database custom fields. ImportantOnly multi-select fields can be mapped to a multiple answer. |
|
Number |
Title, description, or number-, percent-, or currency-type custom fields |
|
Date |
Title, description, start date, end date, or date-type custom fields |
|
Assignee |
Title, description, assignees/owners, or people-type custom fields |
|
Attachment |
Attachments |
|
Importance |
Importance |
Note
If nothing is mapped to a title then it'll be the task or project ID followed by the request form's name.
The task or project ID is contained in the permalink. You can use this ID to search for the item in the account via the search bar.
If a response is mapped to the title, the ID will no longer show up in the title, but you can always find the unique ID in the permalink of the item.
If multiple responses are mapped to the title, then responses are separated by a - in the title.
If a Custom Field is applied to Projects, or to Projects and Folders, it won't be available for mapping if the Request Form creates a task.You can edit the Custom Field settings to make sure it applies to tasks as well.
You should check the type of question that is added to your request form. If a Number type of question is used and it is mapped to Title or Description, the system will remove any leading zero's, extra spaces and add thousands separator (commas, dots or spacing). Responses mapped to a Number type of custom field follow custom field settings to add thousands separator.
e.g. a phone number entered like this 0433 167 614 will be saved in Wrike as this number: 433,167,614
In order to preserve the original format and spacing of the response, you should create a single line text type of question and map it to a text type of custom field.