1. In DS Admin, locate the survey e.g. pizzaexpressfeedback.
2. Copy the questionnaire from DS Admin, creating a Legacy Version.
3. On Admin, go through each section, add, remove or update questions as needed.
4. Check analysis tags are added on relevant questions e.g. Age, Gender, Visit Frequency.
5. If the client has sections that are information only, ensure that all questions in this section have ‘Exclude from visit score’ ticked.
6. Double check work by viewing the questionnaire preview and ensuring that questions, display types, answer options and weightings are correct as per requested update.
7. Set the questionnaire Live.
8. In DS Admin, update the survey version using the ‘Update’ button.
9. Add any logic required.
10. Copy the JSON from Live to QA, or wait until following day for the changes to be reflected in QA.
11. Double check work by previewing survey on QA.
12. Send QA survey link to client for sign off, including survey version and any query strings needed e.g.
13. Once sign off received, test they survey on QA in full i.e. positive and negative pathways, plus a random pathway as minimum. Ensure to test any logic also.
14. Once tested, set the survey version Live immediately, or on the live date if requested.
15. Update any Performance Alerts that were associated with the previous survey version.
Related Articles
Menu Imports/Updates
All capabilities and processes of the Menus and Products pages on the Hive. Viewing a Menu - Click on the menu name in the Hive to view a menu version. - This will show you the menu details, including code, start date and end date. You also have the ...
Client Region & Area Updates
1. If client information is clear what the changes should be, action any branch updates in Hive> Branches> Groups. 2. If client has provided a full updated structure, download the Branches & Users report with the following columns: Branch Name, ...
Use ‘related question’ as well as same ‘legacy question’ to group questions
Where setting up a survey where answers, comments, dishes for one question may be stored against another question with the same legacy question (ID), then need to ‘Group’ questions by using the ‘Related Question’ option which tells the system that ...
Survey Branding
Survey Branding is unique to each client and a ticket for Dev is required to add/update any branding to surveys. Please see fields below for information required on the ticket: Client and Client ID: Survey questionnaire: Survey link: Client logo: ...
Dynamic Survey Validator
The validator triggers after every save. The severity of the error will be a different colour; red means this could be a breaking change, yellow means this could cause data loss, and blue is just for information. It will highlight the following ...