Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
feat(workflow): add inputPorts, outputPorts, glossaryTerms as WorkflowTriggerFields #28120
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Uh oh!
There was an error while loading. Please reload this page.
feat(workflow): add inputPorts, outputPorts, glossaryTerms as WorkflowTriggerFields #28120
Changes from all commits
f471fd9b91468edc0157ee1fe7ea5658caeFile filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In
executeBulkPortsOperation, theChangeEventat line 397 is constructed with the originaldataProductobject which has not been refreshed after relationships were added. ItsupdatedBystill reflects the previous updater (not the current user), and itsversionis never incremented. The fresh entity fetched at line 399 getssetUpdatedBy(updatedBy)andsetChangeDescription(change)but is only used forstoreEntity— the ChangeEvent sent to subscribers contains the stale snapshot.This means:
WorkflowEventConsumer) see an entity snapshot with the wrongupdatedByinside the event payload.storeEntity, so consecutive port operations produce change events with identicalpreviousVersion, which may confuse version-tracking logic.Consider either (a) re-fetching the entity before constructing the ChangeEvent and using that for both, or (b) incrementing the version explicitly (similar to how
bulkAssetsOperationin the same file delegates to the updater path).Re-fetch entity before building ChangeEvent, increment version, and use the fresh entity in the event payload so subscribers see consistent state.:
Was this helpful? React with 👍 / 👎
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.