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
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.
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
here is the output tab
here are my a!saves
I hope my screen shots answered your questions,
yes I am saving into that pv either if I approved or rejected
Thanks guys!
it is late Friday... Have a great weekend ,
This all looks basically right unless I'm missing a subtle detail again. When on the form designer, can you confirm that clicking "approve" and "reject" sets the value of ri!userInformation as you're expecting? What does the value end up being when you view the PVs in the running instance after submitting?
my whole problem is that clicking the submit/ reject does not affect the PV's . I cannot understand why
I'm specifically asking you to confirm the values you see in the rule inputs panel when in the interface designer, though.
That should be the first place you test/troubleshoot.
so:
and ?
thanks for looking at this with me Have a great weekend! talk to you Monday
So in the Rule Inputs section (which you've pictured the left half of in your second screenshot), what is the value contained in ri!userInformaton after you click either button? That's where you should be looking first to make sure the saveIntos are working.
As Mike notes, please expand the userInformation variable in the Rule Inputs area to verify data is saving on the form, when you click your buttons in /design. Additionally, remove the "a!save(ri!userInformation,ri!userInformation)" in both submit buttons. Once we can confirm data is saving on the form we can move to monitoring the process instance to review variable updates in Process History.
Chris said:Additionally, remove the "a!save(ri!userInformation,ri!userInformation)" in both submit buttons.
Shoot, I missed the fact that that was still there - it was the first save previously i think, so wasn't looking at the end of the save list. luckily i think in this case it wouldn't be causing anyhing to get lost since the a!save()s are executed in order, so it would just be (redundantly) saving its current value back into itself.