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

Non-interrupting start events missing in create anything list #4

Open
nikku opened this issue Feb 10, 2023 · 5 comments
Open

Non-interrupting start events missing in create anything list #4

nikku opened this issue Feb 10, 2023 · 5 comments
Labels
backlog Queued in backlog bug Something isn't working spring cleaning Could be cleaned up one day

Comments

@nikku
Copy link
Member

nikku commented Feb 10, 2023

Describe the Bug

As a user I want to create a non interrupting message start event in an event sub-process, but I cannot find it.

image

Steps to Reproduce

  1. Trigger create menu
  2. Search for non
  3. Non interrupting start events do not appear in the list

Expected Behavior

Non interrupting start events appear once searched for. I don't think it is strictly necessary to show them all the time.

Environment

  • Browser: Any
  • OS: Any
  • Library version: 11.3.0
@nikku nikku added the bug Something isn't working label Feb 10, 2023
@nikku
Copy link
Member Author

nikku commented Feb 10, 2023

CC @smbea

@barmac
Copy link
Member

barmac commented Feb 10, 2023

There is a hard-coded check which removes Participants and Start Events from append menu.

@nikku
Copy link
Member Author

nikku commented Feb 10, 2023

Instead of doing that we could hide them initially (rank=-1). We also allow "appending" of event sub-processes.

However this issue specifically is about the create menu, where these entries are not available, too.

@smbea
Copy link
Contributor

smbea commented Feb 10, 2023

Yes the non interrupting start event is missing completely from the options list

@smbea
Copy link
Contributor

smbea commented Feb 17, 2023

I started looking at this. All the non-interrupting start events are missing.

With the current rules, these events are changed into default start events when not placed in an event sub process:

Screen.Recording.2023-02-17.at.16.15.19.mov

In my opinion, I think it makes sense to instead block the shape placement like we do for the non-interrupting boundary events. Demo:

Screen.Recording.2023-02-17.at.16.23.39.mov

Wdyt?

@smbea smbea transferred this issue from bpmn-io/bpmn-js Mar 23, 2023
@smbea smbea added the backlog Queued in backlog label Mar 23, 2023
@nikku nikku added the spring cleaning Could be cleaned up one day label Sep 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backlog Queued in backlog bug Something isn't working spring cleaning Could be cleaned up one day
Projects
None yet
Development

No branches or pull requests

3 participants