{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":4315,"path":"build-workflows/workflow-studio/questionnaire-activity.md","title":"Questionnaire activity","bundle":null,"doc_type":null,"release":"australia","body":"\n# Questionnaire activity\n\nCollects inputs from a user during a playbook run to use later in the playbook.\n\nThe questionnaire activity replaces the Collect User Data activity, but does not require you to create a data definition. Use the questionnaire activity if:\n\n-   You don't have a table already,\n-   You don't need to run reports on the collected data,\n-   And you don't need to use the data outside of the playbook.\n\nIf you already have a table to store the collected data, use the [User Form activity](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/build-workflows/workflow-studio/user-form-activity.md).\n\n## Roles and availability\n\nThis activity is available as a common activity. Users with the admin, playbook.admin, or pd\\_author can add this activity to a playbook.\n\nDuring a playbook run, you can use data definitions to potentially:\n\n-   Collect a shipping address, then reference the address when generating a shipping label.\n-   Ask the user \"yes\" or \"no\" questions, and determine subsequent activities based on the user's responses.\n\n## Common properties\n\nThese properties are common to all to activities in Playbooks.\n\nOpen the activity properties panel and configure your activity to add values for the following inputs. If the input value varies, use the pill-picker to show where to get the value. To learn more about the pill-picker, see [Dot-walking examples](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-user-interface/dot-walking-examples.md).\n\n<table id=\"table_ajt_sr3_plb\"><thead><tr><th>\n\nInput\n\n</th><th>\n\nType\n\n</th><th>\n\nDescription\n\n</th></tr></thead><tbody><tr><td>\n\nLabel\n\n</td><td>\n\nString\n\n</td><td>\n\nTitle to display as activity and playbook card.\n\n</td></tr><tr><td>\n\nDescription\n\n</td><td>\n\nString\n\n</td><td>\n\nInformation to display about activity usage or outcome.\n\n</td></tr><tr><td>\n\nRun condition\n\n</td><td>\n\nCondition Builder\n\n</td><td>\n\nConditions that must be met to run an activity or stage. You can use data from prior activities to build conditions.**Note:** Select **Show additional options** to see this field.\n\n</td></tr><tr><td>\n\nStart Rule\n\n</td><td>\n\nChoice\n\n</td><td>\n\nUnder **Schedule** &gt; **Start Rule**, select a start rule for when your stage should start running:-   **When process starts**: Your stage starts running as soon as the playbook starts.\n-   **After specific stages**: Your stage starts running after specified stage\\(s\\) have finished running.\n\nUnder Schedule &gt; Start Rule, select a start rule for when your activity should start running:-   **When stage starts**: Your activity starts running as soon as its stage starts running. Your stage starts running when your playbook is triggered.\n-   **After specific activities**: Your activity starts running after specified activities have finished running.\n\n</td></tr><tr><td>\n\nStart with delay\n\n</td><td>\n\nTrue/False\n\n</td><td>\n\nOption to wait for a duration of time before running an activity or stage. When enabled, this input displays the [Start with delay input properties](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/build-workflows/workflow-studio/start-with-delay-properties.md).**Note:** Select **Show additional options** to see this field.\n\n</td></tr></tbody>\n</table>## Questionnaire\n\nIn the **Questionnaire** tab, you can:\n\n-   Add questions for agents to respond to,\n-   Edit existing questionnaires.\n\nTo learn more about adding or configuring questions, see [Create a new questionnaire](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/build-workflows/workflow-studio/create-questionnaire.md).\n\n## Inputs\n\nMany of these inputs are common to activities in Playbooks.\n\nAfter configuring the required inputs for your activity, you can also choose to configure additional inputs. In the side panel, select **Show additional options** to display these advanced inputs. For more information, see [Activity experience](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/build-workflows/workflow-studio/activity-definitions.md).\n\n<table><thead><tr><th>\n\nInput\n\n</th><th>\n\nType\n\n</th><th>\n\nDescription\n\n</th></tr></thead><tbody><tr><td>\n\nAssignment Group for this Process Step\n\n</td><td>\n\nReference.Group \\[sys\\_user\\_group\\]\n\n</td><td>\n\nAssignment group allowed to perform this playbook activity. If you don't set any values for **Assignment Group** or **Assigned To**, any user can read and edit the collected data. The Assignment group and Assigned to fields limit who has access to do so. To specify only individual users, use the **Assigned To** field. The same users do not need to be specified in both fields.**Note:** By default, these fields are mapped to the **Assignment Group** and **Assigned To** fields of the trigger record. This means that users assigned to work on the parent record have access to submit, view and edit the collected data by default.\n\n</td></tr><tr><td>\n\nAssigned to this Process Step\n\n</td><td>\n\nReference.User \\[sys\\_user\\]\n\n</td><td>\n\nUser allowed to perform this playbook activity. If you don't set any values for **Assignment Group** or **Assigned To**, any user can read and edit the collected data. The Assignment group and Assigned to fields limit who has access to do so. To specify only individual users, use the **Assigned To** field. The same users do not need to be specified in both fields.**Note:** By default, these fields are mapped to the **Assignment Group** and **Assigned To** fields of the trigger record. This means that users assigned to work on the parent record have access to submit, view and edit the collected data by default.\n\n</td></tr></tbody>\n</table>## Outputs\n\nThese outputs can provide data to other activities in your playbook. You can access this data as activity inputs when you configure your activity:\n\n|Output|Type|Description|\n|------|----|-----------|\n|Record|Reference.Flow Data|Reference to record containing collected data. Use the pill-picker to dot-walk to **Outputs** &gt; **Record** &gt; **Vars** to see all collected data. To learn more about the pill-picker, see [Dot-walking examples](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-user-interface/dot-walking-examples.md).|\n\n-   **[Create a questionnaire](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/build-workflows/workflow-studio/create-questionnaire.md)**  \nCreate and insert a new questionnaire for agents to respond to.\n\n**Parent Topic:**[Stages and activities](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/build-workflows/workflow-studio/process-automation-designer-lanes-activities.md)\n\n"}}