Product Update Version 2.0.22 - Released 20-Nov-2024

In this release, we fixed three defects. The first defect was a problem when participants were imported or created via survey, a specific field was not getting updated and therefore the number of participants in reports were understated. The second issue was a processing problem in which surveys were getting stuck on the loading screen. Lastly, we addressed a situation in which participants wereBoth have been resolved with 2.0.22

 

Unable to Report on Participants Created by a Specific User

When participants are created via survey completion or import, their InsertedBy fields are not being assigned. As a result, you cannot run an accurate report on participants created by a specific user. This has been addressed, and the InsertedBy fields are now assigned during survey completion and participant import resulting in proper reporting by the user.

 

Screen Stuck on Loading when Surveys are Completed

The issue with external surveys getting stuck on the loading screen after pressing the 'Complete' button has been resolved. Previously, the form would save but remain on the loading screen, causing multiple submissions. Additionally, clicking 'Complete' sometimes resulted in the survey saving twice, causing forms to disappear from the 'Forms' tab until the screen was refreshed. With the resolution, surveys now process correctly and efficiently.

 

Participants Incorrectly Assigned Additional Status via Survey

Participants added to Ripple via surveys are getting added to a default status (like 'Intake') as well as the status specified in the survey. As a result of this, events associated with the additional status were being added to the participant profile when they should not have been. This has been fixed, so participant profiles only display the status assigned via survey.

Was this article helpful?0 out of 0 found this helpful