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

BPMN - Change from interrupting escalation boundary event to non-interrupting escalation boundary event properties lost #678

Closed
felix-mueller opened this issue Oct 2, 2017 · 1 comment
Labels
BPMN bug Something isn't working modeling
Milestone

Comments

@felix-mueller
Copy link
Member

Reproduce:

  1. Model Task
  2. Place Interrupting Escalation Boundary Event on Task
  3. Add Escalation Name & Code
  4. Change to Non-Interrupting Escalation Boundary Event
  5. Notice that all properties are gone

Expected:

  1. Model Task
  2. Place Interrupting Escalation Boundary Event on Task
  3. Add Escalation Name & Code
  4. Change to Non-Interrupting Escalation Boundary Event
  5. Notice that all properties are still there
@nikku
Copy link
Member

nikku commented Aug 12, 2019

This has been substantially improved via 2415cf9 / bpmn-js@5.0.0-beta. All properties are now kept as expected.

Two related problems remain, I've created separate issues for them: #1463, #1464.

@nikku nikku closed this as completed Aug 12, 2019
@bpmn-io-tasks bpmn-io-tasks bot removed the backlog Queued in backlog label Aug 12, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
BPMN bug Something isn't working modeling
Projects
None yet
Development

No branches or pull requests

2 participants