We are storing links to a response summary (survey questions & given answeres) in our CRM system. Until now, we are using the old Report.php links like:
https://fra1.qualtrics.com/CP/Report.php?SID=[SurveyId]&R=[ResponseId]&ResponseSummary=True
There are two issues with those kind of links. QX mentioned to us that those links are not supported anymore. They will not be shut down, however, there is no support in case of any issues. Furthermore, the questions can not be displayed in the language of the customer but they are displayed in the base language of the survey. We have surveys that are used by a whole market/country (like Switzerland). If we would make german for example as base language, this would not help the employees from some Italian speaking part. Instead, if it was translated to the language of the customer, this would fit in most cases.
That's why we would like to find some alternative. The relativly new piped text "SingleResponseReportLink" (Response Link) generates a link that provides a response report with questions in the language of the customer. However, this piped text is only accessible in a workflow when a new response was created. We need to prepare the link a bit before the customer actually completes the survey. With the old Report.php links this is possible because we can just concatenate the links. For the SingleResponseReportLink links this is not possible because they have some generated URL. You can not just add URL parameters with the survey and response IDs. We would need this piped text in the survey flow so that we can hand it over to some JSON event. Unfortunatelly, this is probably not possible.
Do you have any ideas that could help us with this situation?
Page 1 / 1
chackbusch - How about handling both elements using survey flow? There could be a response event-based workflow with a Web service task that triggers the JSON event URL. The SingleResponseReportLink can be a body parameter that you pass to the JSON event.
https://community.qualtrics.com/XMcommunity/discussion/comment/47537#Comment_47537Hi Mishraji,
thanks for your input. Technically this would work but in our setup this is unfortunately no good solution. Let me explain the disadvantages for us:
- We add the link to some CRM ticket. This ticket is created based on a given answer in the survey flow. We noticed that few customers answer the question so that a ticket should be created, however, they do not completely finish the survey. The workflow would never be triggered. That's why we currently call a JSON event from the survey flow right after the question was answered. We do not want this to happen with the trigger "new response created".
- We have around 20 similar surveys (one for each market, slightly differ). All of those surveys have added the same reference survey in the flow. This reference survey contains the webservice call (create ticket) in it's flow. This means that the webservice call is only implemented once and all market surveys just reuse the reference survey. Implementing the call of the JSON event in all market surveys (trigger "new response created") would mean quite an effort. Furthermore, in case a change of the webservice request is required in the future, we would need to adapt it 20 times instead of once...
Quite a complex setup in our case. Hope this helps to understand it a little bit...
BR
Christian
Leave a Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.