So I have a process model that has a sub process that basically will send them a email to have them fill out a survey response. Once they go to the survey appian site link and submit their response, we would capture their response for their corresponding application.
However, for some reason when the user submits the survey, Appian generates a new row to capture the survey instead of appending it onto the original application record on 61.
Anyone have any ideas on what may be going on?
Discussion posts and replies are publicly visible
When you originally write to the database, your data will get assigned a primary key. I recommend checking the 'output' subtab on the 'Data' tab of your 'Write to Data Store' smart service and make sure you save the storedValue back into the process variable. This will ensure that any new writes to the database use the same primary key instead of creating a new one. Another way to verify this is happening is to view the 'process history' section when monitoring a process.
yeah for some reason I am not able to get the separate survey to link to the primary key in my main process model. I have a start event that is triggered by them filling out the survey in the link that we send them. But it doesn't seem to recognizing the parent key. I do have the outputs saved as well in the output tab on the write to data source.
Is there maybe something I need to do on the survey itself to link back to the parent?
Based on your original images it looks like your survey sub-process is using a start form. Start forms are great because they don't kick off a process until the form is submitted however they are unable to be access when using in a sub-process. If you need to have one or multiple tasks assigned to users, you will need to use a User Input Task smart service.
I think it's something wrong there too because for some reason when i'm debugging, the process still runs without the form being submitted.
What danny was saying is that start forms are completely ignored when the process model in question is used as a subprocess. If you need to require the user to take action prior to the WTDS node in this screenshot, you will need to add a user input task instead of the start form (you might be able to use the existing interface though).