Question about webforms

Historically, we have created webform templates and added them individually to course outlines. We recently discovered that, for a series (parent/child courses, not RSS), we can add the webform template to the first session and then reference that same webform in subsequent sessions. This allows us to use a single linked webform across all sessions, with responses accumulating in one place.

Has anyone else used this approach? Are there any potential issues or limitations we should be aware of?
Any feedback this group has is appreciated. Thank you.

I’m curious about this, too! If anyone has done this, is there anything in the data export that shows which child the response is linked to?

I do this for one of our activities (currently over 33000 responses).

The results will not tell you which activity specifically they completed it for, however, you could set up a question that ask, this way when pulling the results you could group by their selection.

I tested this out and it pulls the course title that the webform is attached to. I have a couple of test courses in our system and completed the webform in each (see screenshot).

We have multiple ECHO series where this kind of set up would be ideal. The ECHO program sets up each session with the series title, session topic and the date that it is taking place. We had been using the webform settings and naming the session webform “post evaluation - 11/12/2026” as an example. Given that the course name with the date will populate in the “Course title” I think we could move to using the same webform within the series and give it a generic name, ie ECHO [INSERT SERIES NAME] YEAR OF SERIES… or something like that.

Again, would be interested to know if anyone else does this. And even though we do not set up our ECHO series using RSS (we use RSS for other series), the same set-up could apply.
image

Heather, when a learner is presented with that webform for a second time, does the system message cause confusion about previous submissions? And have you tested how the second encounter handles a required submission? I believe EthosCE will count a submission from a previous session when evaluating if a required course object has been completed.

When I tested this, I did have to change the setting for “Limit each user…” to “Unlimited” (see screenshot). There is risk that you could receive multiple responses for a session*. Completion of the object though does not seem to have an impact.

Heather has practiced experience though so I will be interested to have her weigh in.

  • This relates to a support ticket I previously submitted regarding reminder emails. Ideally, the reminder email settings would allow us to trigger reminders based on whether a learner has not yet completed an evaluation.

Under the current reminder email workflow, learners who have already completed the evaluation continue to receive reminders, resulting in unnecessary emails and potential confusion.

In the scenario described above, I believe the risk of duplicate evaluation submissions could be significantly reduced if reminder emails could be configured to send only to learners who have not completed the required evaluation.

If you have the feature on to notify them of a previous submission, it will display. We ended up turning this off. Within the 33k submissions, at least a few hundred have completed for a 2nd or even 3rd time.

The reminders, I still struggle with making sure to select the correct one.

For the webform, if you build it within each session and/or course page, the reminders will be triggered within that area, not at the parent or series level.