Survey tasks

Use survey tasks to record question responses in workflows. Note that this feature is in early access testing. Let us know if you'd like to be added to early access!

Overview

Survey tasks can be used to collect responses to questions in Blissfully workflows. All workflows can include Survey tasks and they can be used to capture any responses, status, or approval that is required in a given workflow. To add a Survey task to a workflow plan, select the "+ Add Task" button when configuring a workflow plan.

Adding a Survey task to a workflow plan

Adding questions to a Survey task

Questions can be added to Survey tasks in two ways: Standard questions or Property-linked questions. Any number of questions can be included in a survey task and you can add both Standard and Property-linked questions to a single survey task.

Standard questions

Standard questions can be added to survey task for the task assignee to respond to within the workflow. These survey responses will NOT be automatically linked with any data property in Blissfully. To add a standard question to a survey task, select the "Add question" option.

Add questions to survey tasks

When adding a standard question, you can specify the desired data format for the response. Options include:

  • Section header - Not a response format, but can be used to create sections in the survey to organize/group other questions

  • Person - Select a person from anyone that has a Person record in Blissfully (e.g., other employees)

  • Document - Upload a single document

  • Yes/No - Yes or No boolean

  • Short answer - Single line, free form text

  • Long answer - Multi-line, free form text

  • Multiple choice - Select one choice from a predefined list

  • Choose all that apply - Select multiple choices from a predefined list

  • Date - Calendar date format

  • Number - Number format

Property-linked questions

Property-linked questions can currently only be added to Vendor/App workflows. To add a Property-linked question to a survey task, select the "App Property" option. When selecting an App Property, any responses are that are submitted by the task assignee will automatically get pushed to the corresponding custom property value for that app.

Property-linked questions

For example, if you created a custom app property for "Department Owner" and added it to a survey task as a Property-linked question, any response that is submitted to that question would populate the "Department Owner" value for that app. The data format for any Property-linked questions will be the format of the linked custom property as defined in the General Settings. This allows you to ensure that the information you're tracking for your applications remains up to date, as you can assign questions to key stakeholders across the organization without having to give them full access to Blissfully.

Configuring a Survey task

In addition to the survey questions, Survey tasks have a few additional configuration requirements:

  1. Task Title (Required) - Name and summary of the survey task

  2. Assigned to (Required) - simple tasks can be assigned to different named roles

    1. Team Lead - the person set as the team lead for the current team's onboarding plan

    2. IT Lead - the person defined as the IT Lead on Blissfully's General Settings page

    3. Specific Person - a specific person at your organization

    4. Specific Team - a specific team that is defined in Blissfully

    5. Workflow Initiator - the Blissfully user who launches the onboarding workflow

    6. App IT Admin - the person defined as the selected app's IT Admin on the Apps page or the app's Detail page (Vendor workflows only)

    7. App Owner - the person defined as the selected app's Owner on the Apps page or the app's Detail page (Vendor workflows only)

    8. Onboardee - the person being onboarded (Onboarding workflows only)

  3. Blockers (Optional) - you can set a task to be "blocked" by other tasks so that it can only be completed once its prerequisites are completed

  4. Start after date (Optional) - you can set a task to start after and only become completable after a certain time

  5. Due date (Optional) - you can set a task to be due by a certain number of days after the workflow launches or the employee's start date