Add inbound boundary event to documentation

[mathias-vandaele]

Description

The description of inbound boundary event was undocumented.

This fixes it.

When should this change go live?

• This is a bug fix, security concern, or something that needs urgent release support.
• This is already available but undocumented and should be released within a week.
• This on a specific schedule and the assignee will coordinate a release with the DevEx team. (apply hold label or convert to draft PR)
• This is part of a scheduled alpha or minor. (apply alpha or minor label)
• There is no urgency with this change and can be released at any time.

PR Checklist

• My changes are for an already released minor and are in /versioned_docs directory.
• My changes are for the next minor and are in /docs directory (aka /next/).

• My changes require an Engineering review, and I've assigned the Engineering DRI or delegate.
• My changes require a technical writer review, and I've assigned @camunda/tech-writers as a reviewer.

[github-actions]

👋 🤖 ✅ Looks like the changes were ported across versions, nice job! 🎉

You can read more about the versioning within our docs in our documentation guidelines.

[sbuettner]

I think we should rather link to the marketplace than including the element template here.

[akeller]

Is this still an open topic?

[christinaausley]

Based on discussion with @mathias-vandaele and @sbuettner, I have added an admonition at the top of the page with a link to Marketplace. I have also backported this, though they may have additional changes based on casing for the elements in this PR.

[sbuettner]

The example is a little bit unclear as it doesnt contain any labels. I would also recommend to only use a single connector in the example. The one that is used for the boundary event. Please also describe how the Connector is used in this example like: Using Connectors as Boundary Events allows to receive messages while another activity is executing or waiting.

I would therefore recommend to model is with a user task which gets interrupted for example.

[akeller]

Does this need to be backported?

[mathias-vandaele]

@akeller Yes i think so, as it was missing from the documentation.

It can also be merged

[christinaausley]

@mathias-vandaele Can you resolve the comments from @sbuettner here, and I will backport and merge for you?

[mathias-vandaele]

@christinaausley I have made the modification in response to @sbuettner's second comment, concerning the first comment, which involves removing all the XML present in this file and eliminating the tab system for coherence. How should we then include the marketplace link?

[christinaausley]

@mathias-vandaele @sbuettner Per our discussion on Slack, I have added an admonition at the top of the page with a link to Marketplace. I have also backported this for you -- if you have any additional changes you can make these in this PR or a separate PR, but I am approving from a TW perspective.