Desktop modeler start form

[MrGussio]

Proposed Changes

Closes #1196 by enabling the "Form" group property in case the element is either a user task, or a start event (but not if the start event is part of a sub process)

This is in line with the cloud/platform providers in this repository.

Screenshot in desktop modeler:

Screenshot from this repo's npm run start:

To try out:

1. Run npm run start
2. Click on a start event
3. See that there is now a section where you can specify the form to use upon starting a form

Checklist

Ensure you provide everything we need to review your contribution:

• Contribution meets our definition of done
• Pull request establishes context
  • Link to related issue(s), i.e. Closes {LINK_TO_ISSUE} or Related to {LINK_TO_ISSUE}
  • Brief textual description of the changes
  • Screenshots or short videos showing UI/UX changes
  • Steps to try out, i.e. using the @bpmn-io/sr tool

[CLAassistant]

All committers have signed the CLA.

[Copilot]

Pull request overview

Enables the Zeebe “Form” properties group for process-level start events (excluding start events inside subprocesses), aligning Desktop Modeler behavior with other providers in the repository and addressing #1196.

Changes:

• Add isFormSupported utility to allow forms for bpmn:UserTask and top-level bpmn:StartEvent.
• Update Zeebe FormProps to use isFormSupported instead of restricting to user tasks only.
• Extend the Zeebe Forms test fixture BPMN and add start-event-related specs.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 4 comments.

File	Description
test/spec/provider/zeebe/Forms.spec.js	Adds start event form tests, but currently contains a duplicated full “user tasks” test suite.
test/spec/provider/zeebe/Forms.bpmn	Extends the BPMN fixture with additional zeebe:userTaskForm entries and start events for testing.
src/provider/zeebe/utils/FormUtil.js	Introduces isFormSupported (user tasks + process-level start events).
src/provider/zeebe/properties/FormProps.js	Uses isFormSupported to determine whether to show form entries.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The entire describe('user tasks' ...) test suite appears duplicated: one block ends around line 832 and another starts again at line 834. This adds a lot of redundant test execution and makes the spec harder to maintain; please remove the duplicate block (keep a single copy).

[barmac]

Hi,
Thanks for opening the pull request. While this moves the topic forward, we cannot merge it as is for a couple of reasons:

1. Start event forms don't support binding property yet. The support needs to be added in Camunda yet.
2. We don't want to embrace embedded forms as it's a legacy pattern. So only linked forms should be allowed.

Since there is a Camunda dependency, we will need to postpone this PR. However, the feature request is tracked, so we should get back to it soon.

[barmac]

Related comment: camunda/camunda-modeler#4672 (comment)

[MrGussio]

@barmac Thanks for your reply. Hmm, never noticed this, but not only Tasklist but the entire API endpoint behind it does not take form versions into account, but always retrieves the latest form instead.

Found this issue in the Camunda backlog which I think describes the required feature. Linking it here for reference: camunda/camunda#20067