Skip to content
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

fix(asyncInstanceModification): respect ancestor during startBefore/after cmd execution #4829

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

PHWaechtler
Copy link
Contributor

related to #4507

@PHWaechtler PHWaechtler force-pushed the 4507-startafter-startbefore-ignore-ancestor-field branch from 45ea27d to 30a3ea4 Compare December 3, 2024 13:30
Comment on lines +89 to +95
public String getAncestorActivityInstanceId() {
return ancestorActivityInstanceId;
}

public void setAncestorActivityInstanceId(String ancestorActivityInstanceId) {
this.ancestorActivityInstanceId = ancestorActivityInstanceId;
}
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Q:
I noticed this ancestorID field also exists in TransitionInstantiationCmd and it is also not set during serialization and deserialistion of this command. I had a look at some of the tests for TransitionInstantiationCmd, but I do not have enough context for how this command is used by the user and what the expected behaviour is to be able to judge if the same issue exists here. I also saw no support tickets with an edge case for this specific command.
Suggestion:
I open a follow up ticket for further investigation and potential fix of TransitionInstantiationCmd (if required).
Wdyt?

@PHWaechtler PHWaechtler self-assigned this Dec 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant