setOutputValue in after saving contact trigger

Marc Eberhard 13 Jan 2022

Hi

Ever since deployment of configurable screens the function EventData.setOutputValue seems to have no effect in after saving contact (person) and after saving company trigger: the browser displays the state, as if the trigger was not active.
Attempts to refresh browser by using "soprotocol:person" inside the trigger do not work either:

ed.setNavigateTo("soprotocol:person.main[refresh=true]");

The only workaround I found is to manually refresh the browser using F5.

Is there a way to force SuperOffice to refresh the display, from inside a trigger?

Or is the lack of effect of setOutputValue a bug?

Best regards
Marc


RE: setOutputValue in after saving contact trigger

Tony Yates 14 Jan 2022

RE: setOutputValue in after saving contact trigger

Marc Eberhard 14 Jan 2022

RE: setOutputValue in after saving contact trigger

Michel Krohn-Dale 17 Jan 2022

RE: setOutputValue in after saving contact trigger

Marc Eberhard 18 Jan 2022

Michel Krohn-Dale
20 Jan 2022
We are still investigating issue with refresh and hopefully we will find a solution for this and correct the behaviour
/Michel

RE: setOutputValue in after saving contact trigger

Espen Steen 24 Mar 2022

RE: setOutputValue in after saving contact trigger

Michel Krohn-Dale 24 Mar 2022

RE: setOutputValue in after saving contact trigger

Espen Steen 24 Mar 2022

RE: setOutputValue in after saving contact trigger

Michel Krohn-Dale 24 Mar 2022

Espen Steen
24 Mar 2022
Hi Michel
Ah, thanks a lot. That works a lot better. And sorry I was mixing up issues here.

RE: setOutputValue in after saving contact trigger

Frode Lillerud 31 Mar 2022

Tony Yates
1 Apr 2022
Added as bug 26878.