primaryButtons: { a!buttonWidget( label: "Approve", icon: "check", value: true(), saveInto: { a!save(ri!GFIM_User_Access_User_Information,ri!GFIM_User_Access_User_Information), a!save(ri!GFIM_User_Access_User_Information.supervisorsDecisionDate,now()), a!save(ri!GFIM_User_Access_User_Information.supervisorDecision,true) }, submit: true, style: "PRIMARY" ) },
Discussion posts and replies are publicly visible
A few redundancies here.
The first line of your saveInto does literally nothing. It saves the current RI value back into itself - which will have net zero effect. You can remove this as far as I can tell. Keep lines 2 and 3, these should work correctly for what you're seemingly trying to do.
You save the value from the node Inputs tab into a PV, and then you save it into a PV in the Outputs tab. This is also unnecessary - you only need to do it in one place or the other. Usually in cases like this it's easiest to just do it from the Inputs tab, unless you need to do some sort of transformation to the CDT upon form submission, in which case you should only use the Outputs tab (i don't think this applies to you though). NOTE: per what Chris pointed out below, even if you did want to save the CDT value in the Output tab, the data output should reference ac!User_Data instead of pv!User_Data.
Your Write to Data Store is configured correctly.
What exactly is the issue you're having? Despite the redundancies I noted, I don't spot any errors that would (necessarily) prevent proper function.
Thanks for the reply Mike,
I am unable to see any of the values that I was populating in that form.
It seems like the write to data store is not functioning at all.
In this case your Interface Output save for pv!User_Data is overwriting your interface updates. Only the Save Into from the Input tab is correct, you will want to delete the Output Save Into, as this is overwriting with the pv! value (what the variable was set at prior to the form save). If you had used ac!User_Data in the output this would function correctly but be redundant.
kevinr0001 said:I am unable to see any of the values that I was populating in that form.
Can you expand on this? Under what circumstances are you trying / expecting to see values that you populated in that form? Are you saying you don't see the values getting written to the DB table after the process completes, or something else?
Oh yeah, good catch - I didn't even notice the interface output node was referencing the PV in saving the PV back into itself. That said I'm not clear (without testing) whether the save-out to the PV from the Input tab would happen before or after the Output save executes... but in any case there's no need for such confusion since there's a potential overwrite and/or race condition.
Yep! From overwriting my own data on a few occasions, I can confirm the Output expressions fire last and will essentially reset any of the Inputs if there is a conflict. Been there, done that! :)
I am unable to see any of the variables in the process that I was changing in the form.
Specifically it is an approval form and it does not change the boolean to true. when I hit the submit button
The first thing you should do is resolve the issue Chris pointed out below. After that, let us know whether you're still not seeing changes within the PV - i'm guessing this was the primary issue.
thanks I removed it and the other redundant things but it still does not save anything.
like there is no difference to the variables before and after
here is my process now
thanks for sticking with me Mike, I am still not seeing any changes to my PV