When the calculated field is updated, pubSub does not work

[OllegK]

SWE_PROP_BC_NOTI_NEW_RECORD_DATA is not honoured

[OllegK]

It was reported that pubSub does not work when just a new value is picked from the pick applet, and the record is saved (AK) (maybe this issue could be reproduced only with the not immediate post change field? ). As far as I remember, the cp was skipped because it was received when the mvg/pick applet "opened" on the not-committed record.

AK workaround

[ostgals]

Actually yesterday I faced an issue that Siebel can send several SWE_PROP_BC_NOTI_STATE_CHANGED notifications with 'cp' state set either to 0 and to 1 (within single notification session). As a result UI was updated like the record was already saved, while actually it wasn't. The issue raised in an applet with complicated series of calculation while creating new record, triggering its 'commit pending' state back and forth several times.
So I have reworked my workaround to trigger UI updating only once with the latest 'cp' value after SWE_PROP_BC_NOTI_END notification arrived.

[esneko]

@ostgals Please can you make a PR with the SWE_PROP_BC_NOTI_END workaround for the nexus-bridge, or does your implementation rely heavily on React?

[ostgals]

@esneko Yes, currently we have implemented this workaround as custom React hook. But I'll try to find time and to create PR to nexus-bridge next week.