[workflow] Defining multiple events in eventsActions expression and state data integrity about wg-serverless HOT 3 CLOSED

AFAICS, parallelstate and parallel-mode eventactions have the same problem but would solve it with actiondatafilter. Would eventdatafilter for each received event also solve it?

from wg-serverless.

As of now, there is only a single eventdatafilter in an eventaction definition that would be applied to all events collected, correct? that makes absolutely no sense :)
IMHO each incoming event would need a separate eventdatafilter to achieve conflict-free merging.

Additionally, an event state may get incoming data from a previous state in case it is transitioned to. Because, IIUC, the behaviour of event state is different when a workflow starts with an event state (in which case the event triggering the workflow is being evaluated in the eventaction expression) or whether a workflow transitions into an event state (in which case the passed input [event] is not evaluated against the expression). So conflict-free data merging can become extra complicated.

Furthermore, if I wanted to loop in order to collect a batch of events, I might need to retain more data from the first occurence than from subsequent events. Or have the last occurence overwrite some of the data of the first occurence (as in latest timestamp) or batch the entire set of events altogether to not loose any of the details.

I'm not sure anymore if an eventdatafilter per referred event would be enough. it would also require some dataOutputPath to decide where to inject the received data. This somehow conflicts with the alternate behaviour of the event state.

from wg-serverless.

Will move to new repo

from wg-serverless.