Pretty much. Survey management has its own architecture, and it actually uses several tables that are related to each other. It is worth understanding what the different tables are used for, so you crate the reports you need.
Here's a screenshot of a schema map with the Assessment Instance table in center (this table is basically an instance of a survey that is generated and assigned to a particular user):
As you can see, the table has a task_id field which references the Task table, thereby linking to the recording in question, e.g. incident.
At the end you'll probably want to report on the Metric Result table, i.e. asmt_metric_result, which does not have a column linking to the task, but only a link to the Assessment Instance, which, as described above, can link to the task.
You can find some out of the box surveys in the system to get you started - I recommend taking a look at them. For starters, take a look at the 'Short Customer Satisfaction Survey using Smiley Face' under Survey > View Surveys. You will see it has a Trigger Condition configured on the incident table, for every incident that gets closed and is not a Universal Request, with a repeat interval of 30 days, which means the 'Caller' of the incident would only receive the survey invitation, if they were not assigned another instance of this same survey within the last 30 days (so in this case, they will not necessary receive it for every incident, in order to not spam them). You can easily tailor this to your organization's needs.
