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

Message properties are not reused when a message event template is applied #4851

Open
barmac opened this issue Feb 25, 2025 · 1 comment
Open
Labels
bug Something isn't working channel:support ready Ready to be worked on spring cleaning Could be cleaned up one day

Comments

@barmac
Copy link
Collaborator

barmac commented Feb 25, 2025

Describe the bug

When I apply a message event template to an element linked to a message with a defined subscription correlation key, the newly created message does not get the old value.

This is contrary to the expectations that we built in other parts of element templates, e.g. input/output:

Screen.Recording.2025-02-25.at.10.42.55.mov

Steps to reproduce

Screen.Recording.2025-02-25.at.08.24.09.mov

Expected behavior

Subscription correlation key is reused.

Environment

  • OS: [e.g. MacOS 10.2, Windows 10]
  • Camunda Modeler Version: any with message event templates
  • Execution Platform: C8
  • Installed plug-ins: [...]

Additional context

SUPPORT-25972

@barmac barmac added bug Something isn't working channel:support backlog Queued in backlog spring cleaning Could be cleaned up one day labels Feb 25, 2025
@barmac
Copy link
Collaborator Author

barmac commented Feb 25, 2025

This needs to be fixed in bpmn-io/bpmn-js-element-templates

@barmac barmac added the ready Ready to be worked on label Feb 25, 2025 — with bpmn-io-tasks
@barmac barmac removed the backlog Queued in backlog label Feb 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working channel:support ready Ready to be worked on spring cleaning Could be cleaned up one day
Projects
None yet
Development

No branches or pull requests

1 participant