Cannot See All Gateway Types

skayliu · July 12, 2022, 2:15pm

Hi,
1、In the Camunda Model 5.0 ,you can switch to the xml mode and change the bpmn:exclusiveGateway to bpmn:inclusiveGateway and you get the Inclusive Gateway.

2、There is a PR for the Inclusive Gateway,you can take a look first.

github.com/camunda/zeebe

Support BPMN Inclusive Gateways

opened 02:36AM - 16 Dec 20 UTC

ningdr

kind/feature blocker/stakeholder area/bpmn-support

**Is your feature request related to a problem? Please describe.** A clear and …concise description of what the problem is. Ex. I'm always frustrated when [...] **Describe the solution you'd like** A clear and concise description of what you want to happen. **Describe alternatives you've considered** A clear and concise description of any alternative solutions or features you've considered. **Additional context** Add any other context or screenshots about the feature request here.

github.com/camunda/zeebe

6018 support bpmn inclusive gateways

camunda:main ← skayliu:6018-support-bpmn-inclusive-gateways

opened 02:55AM - 10 Jul 22 UTC

skayliu

+1455 -15

## Description . As a user,i want to use the iclusvie gateway instead of us…ing a combination of parallel and exclusive gateways. . As the image show, we should fullfield this scenario first. ![image](https://user-images.githubusercontent.com/26370117/178129224-23eb4bb7-0733-4ed4-b4cc-3782e269078b.png) ## Related issues closes #6018  ## Definition of Done _Not all items need to be done depending on the issue and the pull request._ Code changes: * [x] The changes are backwards compatibility with previous versions * [ ] If it fixes a bug then PRs are created to [backport](https://github.com/camunda/zeebe/compare/stable/0.24...main?expand=1&template=backport_template.md&title=[Backport%200.24]) the fix to the last two minor versions. You can trigger a backport by assigning labels (e.g. `backport stable/1.3`) to the PR, in case that fails you need to create backports manually. Testing: * [x] There are unit/integration tests that verify all acceptance criterias of the issue * [x] New tests are written to ensure backwards compatibility with further versions * [x] The behavior is tested manually * [ ] The change has been verified by a QA run * [ ] The impact of the changes is verified by a benchmark Documentation: * [ ] The documentation is updated (e.g. BPMN reference, configuration, examples, get-started guides, etc.) * [ ] New content is added to the [release announcement](https://drive.google.com/drive/u/0/folders/1DTIeswnEEq-NggJ25rm2BsDjcCQpDape) * [x] If the PR changes how BPMN processes are validated (e.g. support new BPMN element) then the Camunda modeling team should be informed to adjust the BPMN linting. Please refer to our [review guidelines](https://github.com/camunda/zeebe/wiki/Pull-Requests-and-Code-Reviews#code-review-guidelines).