FRW-10501 Improve publish product logic based on timestamps.

[vol4onok]

• Developer(s): @vol4onok

• Ticket: https://spryker.atlassian.net/browse/FRW-10501

• Release Group: https://release.spryker.com/release-groups/view/6017

• merge: merge

Release Table

Module	Release Type	Constraint Updates
EventBehavior	minor

---

Module EventBehavior

Change log

Improvements

• Introduced HydrateEventsRequest transfer.
• Introduced HydrateEventsResponse transfer.
• Introduced EventBehaviorFacadeInterface::hydrateEventDataTransfer() facade method to get event data with timestamp.

[snyk-spryker]

🎉 Snyk checks have passed. No issues have been found so far.

✅ code/snyk check is complete. No issues have been found. (View Details)

[vol4onok]

| Dependency violations in Spryker.EventBehavior |
+-------------------------+-----------------------------------------------------------+
| spryker/transfer | Dependency listed in composer require not found in source |
+-------------------------+-----------------------------------------------------------+
In suite. Spryker CV can be ignored

[stereomon]

When CI is green, it's fine for me.

[gechetspr]

so, if we go with the easiest flow that we can check. E.g. I've updating some big form on backoffice that have more than 1 entity in it. I put new data in it and it will trigger n+1 different events. There are not a 0 chance that those events will have the same id. With this approach we are going to loose some of the events.

The same goes for other similar methods

[vol4onok]

As you see, we use the last one for a specific (unique) entity. It's part of the improvement

[gechetspr]

ok. I still have my doubts, but please double check it on QA

[gechetspr]

so we just set time from now, but we need to compare it with the time from the message. This is not according AC

[gechetspr]

are those changes mentioned in the changelogs?

[vol4onok]

yes, it's enough here because we publish specific entities, we don't modify them.

[gechetspr]

Code is ok. Looks like are skipping older events on publish phase as stated in AC