Hi,
Discussion posts and replies are publicly visible
Are you using an onSuccess save parameter to have the local form's data reflect anything about the data changed in the launched process?
Can you share your a!startProcess() code snippet here?
Hi Cedric,
Did you try using a!refresh Variable function on the data you are refreshing from DB?
Have you applied Channing in the process called under a!startprocess , please do the channing till the db update.
a!buttonArrayLayout( buttons: { a!buttonWidget( label: "Update", icon: "refresh-alt", saveInto: { a!startProcess( processModel: cons!AS_PM_HISTO, processParameters: { projetId: ri!projetId }, onSuccess: { a!save( local!history, rule!as_qe_getHistoryWithFilters( projectId: ri!projectId )[1] ), }, onError: { } ) }, style: "SECONDARY" ) },
Yes, I've tried but without success
yes, Komalj, as I've wrote all nodes are chained.
It is like if the interface does not succeed to get the fresh data from the Db.
Like a cache issue.
If I close the interface and then reopen it, the data are correct.
Does onSuccess() really executed after the last process node (on the end event) ?
I've finally found a solution:
Using pv!processInfo to get back the last updated data.(Calling the ER from onSuccess() event does not work)
cedric01 said:Calling the ER from onSuccess
Check your ER. If you have any local variables in it, they're probably not set to "refresh always", and therefore won't automatically re-execute even when you think it should (i.e. when called in your onSuccess parameter). One way I've gotten around this in the past is to pass a refresh counter into the ER itself, so it only refreshes when i want it to. That gives you the additional advantage wherein you can just have your onSuccess paramter increment your refresh counter, and use the initial query done in your variable declarations (when applicable).