Mapping Responses in Request Forms
|
Availability: Legacy Business, Legacy Enterprise.; Unavailability: Legacy Free, Legacy Professional.; |
|
Availability: Business, Enterprise, Pinnacle. ; Unavailability: Free, Team; |
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.
Note
If your account has disabled attaching files from local storage, you can still add a "file attachments" question to your request form. Users can select files from their computer and add them to the form, but after submission, those files won’t be accessible in the created task or project. Instead, you’ll see the file names listed in the description field. This also applies to external request forms. All attachments are added by Wrike Bot after a form is submitted.
|
Question type |
Mapping options |
|---|---|
|
Single line text |
Title, description, text-type custom fields, single-select-type custom fields with "Allow others to add custom labels" option enabled. ImportantIf mapped to the item title, the limit is 100 characters. There’s no limit when mapped to the description field. |
|
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 ImportantAssignee-type questions are available in internal request forms only. This is a privacy and security measure to prevent exposing the account’s user list to anyone with the request form link. If a request form has a public link enabled, the assignee-type question will be greyed out. |
|
Attachment |
Attachments ImportantAttachments can be added only from computer or from Box. Attaching files from other cloud storage apps (Google Drive, OneDrive, SharePoint, or Dropbox) is not supported in request forms. |
|
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.
When you map a date-type or number-type question from a request form to a title or description, how it looks depends on two things:
-
If you’re adding it to a task or project title/description.
-
The date format you’ve selected in your profile settings.
Dates and Numbers in Project Titles
-
Dates use a dash "-" as the separator, with the format YYYY-MM-DD.
-
Numbers use a space for the thousands separator and a dot "." for the decimal symbol.
Dates and Numbers in Tasks and Projects Descriptions and Task Titles
-
Dates use a dash "-" as the separator, with the format YYYY-MM-DD.
-
Numbers use a space for the thousands separator and a comma "," for the decimal separator.
|
Location \ date format in the profile settings |
dd/mm/yyyy |
mm/dd/yyyy |
yyyy/mm/dd |
|---|---|---|---|
|
Task title |
1 234,56 |
1 234,56 |
1 234,56 |
|
Task description |
1 234,56 |
1 234,56 |
1 234,56 |
|
Project title |
1 234.56 |
1 234.56 |
1 234.56 |
|
Project description |
1 234,56 |
1 234,56 |
1 234,56 |
It is possible to map date-type questions in the request forms to start and end date of a task or a project that is created from the request.
Mapping a Request Form Only to the Start Date
Request form that trigger task creation:
-
If the question is answered then the task is created as 1-day task with a specified start date.
-
If the question is not answered the task is created as Backlogged.
Request forms that trigger project creation:
-
If the question is answered then the project is created with a specified start date, finish date stays empty.
-
If the question is not answered the project dates are empty.
Mapping a Request Form Only to the End Date
Request form that trigger task creation:
-
If the question is answered then the task is created as a Milestone with a specified finish date.
-
If the question is not answered the task is created as Backlogged.
Request forms that trigger project creation:
-
If the question is answered then the project is created with a specified finish date, start date stays empty.
-
If the question is not answered the project dates are empty.
Mapping a Request Form to Both Start and End Dates
Request forms that trigger task creation:
-
If both questions are answered then the task is scheduled for specified dates. But if start date is later than end date then the task is backlogged and answers are added in the description.
-
If one question is answered and another isn't then a 1-day task is created for the start or end date submitted.
-
If both questions aren't answered then the task is backlogged.
Request forms that trigger project creation:
-
If both questions are answered then the project's dates are filled in with the answers. But if start date is later than end date the project dates are empty and answers are added in the description.
-
If one question is answered and another isn't then the entered date is added to the project start or finish date (depending on which question is answered) and another date stays empty.
-
If both questions aren't answered then both project dates stay empty.
You can set up a request form to add a prefix to new projects, duplicated projects, or projects created from blueprints.
If you use a checkbox-type question as the prefix, every option a requester selects will show up in the project prefix, separated by a dash.
For example: If you've selected a checkbox question with 3 possible options: A, B, and C as a prefix. When a user submits the request they select options A and B. Then the prefix will look like this: [A - B]. This makes it easy to identify projects based on the choices made in the form.
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.