Any suggestions on how to collect input from multiple individuals at the same ti

Certified Senior Developer
Any suggestions on how to collect input from multiple individuals at the same time? I have a process that includes a 'survey' type step. I'd like to send a task to a group (at the same time) and have them provide input individually (same input form but each person in the group would be tasked to complete it - and membership could vary). When all (or a set number) have submitted their input (i.e., tasks have been completed) - the process would continue. I'm using the getdistinctusers(topeople(pv!group)) function to assign the task to everyone in a specific group. That seems to work but I get 2 tasks for every person in the group (not sure why). In the 'Other' tab, I selected 'Run one instance for each assignee' at the same time. Each form collects the 'vote' (Y or N) and any feedback (text) in a CDT that is set up as a 'multiple'. When I test it - I get the multiple tasks/assignee but the data saved is just the last data entered. How do I get all re...

OriginalPostID-194377

OriginalPostID-194377

  Discussion posts and replies are publicly visible

Parents
  • Try putting your input task (the survery) into a subprocess configured to MNI. Map the output of the subprocess to a pv called singleSurveyResult in the main process. Configure an event listener to listen for a change to pv!singleSurveryResult, when that happens kick off a script task which appends pv!singleSurveyResult to a pv!surveryAllResults which would be an array of your results. Make sure the event listener gets kicked off for every change to the pv!singleSurveyResult and not just once. Also make sure the script tasks deletes previous completed instances. If not you will run into the issue of too many instances of that node if you scale up with the number of users surveyed. Hope this helps!
Reply
  • Try putting your input task (the survery) into a subprocess configured to MNI. Map the output of the subprocess to a pv called singleSurveyResult in the main process. Configure an event listener to listen for a change to pv!singleSurveryResult, when that happens kick off a script task which appends pv!singleSurveyResult to a pv!surveryAllResults which would be an array of your results. Make sure the event listener gets kicked off for every change to the pv!singleSurveyResult and not just once. Also make sure the script tasks deletes previous completed instances. If not you will run into the issue of too many instances of that node if you scale up with the number of users surveyed. Hope this helps!
Children
No Data