Hi
I am on the trial version of Camunda and I have started to play around with it. I can see some gateway types when I add one (Exclusive, Parallel and Event Based) but I dont see the Inclusive or Complex gateway. Is there a reason for this ?
Thank you in advance
Allan
eileen
April 21, 2022, 2:25pm
2
Hi,BPMN coverage | Camunda Platform 8
2 Likes
Niall
April 21, 2022, 2:40pm
3
Indeed, @eileen is correct - the Camunda 8 modeler only shows supported symbols so that people don’t end up creating a model that can’t be executed.
if you’re interested in modeling for diagrammatic purposes you can use Cawemo which has no such restriction.
Hi,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.
opened 02:36AM - 16 Dec 20 UTC
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.
camunda:main ← skayliu:6018-support-bpmn-inclusive-gateways
opened 02:55AM - 10 Jul 22 UTC
## 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.
## Related issues
closes #6018
<!-- Cut-off marker
_All lines under and including the cut-off marker will be removed from the merge commit message_
## Definition of Ready
Please check the items that apply, before requesting a review.
You can find more details about these items in our wiki page about [Pull Requests and Code Reviews](https://github.com/camunda/zeebe/wiki/Pull-Requests-and-Code-Reviews).
* [x] I've reviewed my own code
* [x] I've written a clear changelist description
* [x] I've narrowly scoped my changes
* [x] I've separated structural from behavioural changes
-->
## 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).
3 Likes
jwulf
July 12, 2022, 7:55pm
5
Fantastic work on implementing that gateway @skayliu !
