Survey triggered from sc_task - Unable to display fields and variables from task

[Chris Dea1]

Hi all,

I am in the middle of creating a new custom survey for a new department.  In the past other groups have used a survey with trigger on sc_request table. For this new custom survey I am triggering from sc_task table. I noticed in testing that when the survey is triggered on sc_task and the user is sent a link to the survey. if the user clicks on the task number (next to "This survey is in regards to Task: ") the window that appears does not show fields and variables present on task. (See screenshot attached with red arrow.) However, if I change the trigger to be on the sc_req_item table instead, when the user receives a survey and clicks link to RITM, then fields from the RITM and variabless are shown. (See screenshot with green arrows).  Also attaching a screenshot of the trigger on sc_task.

Can you tell me how to set things to display fields and variables from the task when user clicks Task number on link next to "This survey is in regards to Task:"?  We have many types of users who will utilize the survey, most are non-itil users without any role in SN.  Example screenshots were when clicking link to task/ritm on survey as user without any role.

I did a test just now and it seems ITIL users can see fields/variables when clicking link to task from Survey.  See screenshot added.  Do I need to tweak some ACL or UI policy to allow users without role to see fields/variables on a task when clicking the link (to task number) from survey?

Thanks for any help,

Chris

[Dr Atul G- LNG]

Hi @Chris Dea1 

Greetings!

Hope you are doing well. Truly speaking I have answer for this problem but I am curious to know why you want to trigger the survey on sc_task table? 

- A user is never interested or know how many task get generated in background?

- also if you send 5 survey to same users , we may not get the correct survey because filling the survey is always a boring work for user.

- Also survey task will not tell you the overall satisfaction of REQ? so tough to drive the KPI.

My thought , instead of sc_task keep it on REQ level or RITM only.