Propagating input and correlation id from parent workflow to child workflow #6709
+51
−10
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…low to child workflow
Author
|
@dotnet-policy-service agree |
sfmskywalker
force-pushed
the
main
branch
2 times, most recently
from
4e58970 to
ae1bb77
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Input and correlation id is not propagated to child workflow from parent workflow. This PR fixes the ExecuteWorkflow activity to propagate the input and correlation id from parent workflow to child workflow.
If the ExecuteWorkflow activity exists to execute a child workflow, then it is reasonable to assume that the child workflow might be reused by other workflows as well and the input from parent workflows should be propagated to child workflows.
Correlation id is propagated for tracking purposes.
See this issue #6706.
The test is not pretty, it would be great to have guidelines on how to test things in Elsa. I tried to create test similar to other tests in Elsa.Workflows.IntegrationTests.Scenarios.RunAsynchronousActivityOutput namespace but it did not capture any text in activity execution records.
This change is