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.

Sign up for GitHub

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

Jump to bottom

I can deploy a process definition with escalation event #10688

Closed
Tracked by #10682
lzgabel opened this issue Oct 12, 2022 · 0 comments · Fixed by #10714
Closed
Tracked by #10682

I can deploy a process definition with escalation event #10688

lzgabel opened this issue Oct 12, 2022 · 0 comments · Fixed by #10714
Assignees
@remcowesterhoud @lzgabel
Labels
kind/feature Categorizes an issue or PR as a feature, i.e. new behavior version:8.2.0-alpha1 Marks an issue as being completely or in parts released in 8.2.0-alpha1 version:8.2.0 Marks an issue as being completely or in parts released in 8.2.0

Comments

@lzgabel
Copy link
Contributor

lzgabel commented Oct 12, 2022

Is your feature request related to a problem? Please describe.
As a user I can deploy a process definition with escalation event.

Describe the solution you'd like
N/A

Describe alternatives you've considered
N/A

Additional context

Sample XML:

<bpmn:intermediateThrowEvent id="Event_05pvtq0">
  <bpmn:incoming>Flow_0zt0ojv</bpmn:incoming>
  <bpmn:outgoing>Flow_0ycgkcf</bpmn:outgoing>
  <bpmn:escalationEventDefinition id="EscalationEventDefinition_12gaahi" escalationRef="Escalation_3qb79g1" />
</bpmn:intermediateThrowEvent>
<bpmn:escalation id="Escalation_3qb79g1" name="Escalation_3qb79g1" escalationCode="escalationCode" />


<bpmn:endEvent id="Event_0vica91">
  <bpmn:incoming>Flow_0zt0ojv</bpmn:incoming>
  <bpmn:escalationEventDefinition id="EscalationEventDefinition_0w6r586" escalationRef="Escalation_3rhpl03" />
</bpmn:endEvent>
<bpmn:escalation id="Escalation_3rhpl03" name="Escalation_3rhpl03" escalationCode="escalationCode" />


<bpmn:boundaryEvent id="Event_169bq58" cancelActivity="false" attachedToRef="Activity_19g0rz4">
  <bpmn:outgoing>Flow_14kqcbl</bpmn:outgoing>
  <bpmn:escalationEventDefinition id="EscalationEventDefinition_0frw0v3" />
</bpmn:boundaryEvent>
@lzgabel lzgabel added the kind/feature Categorizes an issue or PR as a feature, i.e. new behavior label Oct 12, 2022
This was referenced Oct 12, 2022
Closed
Merged
@remcowesterhoud remcowesterhoud mentioned this issue Oct 19, 2022
Closed
zeebe-bors-camunda bot added a commit that referenced this issue Oct 20, 2022
@zeebe-bors-camunda @lzgabel
merge: #10714
f653ac5 
10714: feat(bpmn-model): support escalation events r=remcowesterhoud a=lzgabel

## Description
As a user I can deploy a process definition with escalation event.

## Related issues
closes #10688 

## Definition of Done

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
* [ ] 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)
* [ ] 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).


Co-authored-by: lzgabel <lz19960321lz@gmail.com>
@korthout korthout added the version:8.2.0-alpha1 Marks an issue as being completely or in parts released in 8.2.0-alpha1 label Nov 1, 2022
@npepinpe npepinpe added the version:8.2.0 Marks an issue as being completely or in parts released in 8.2.0 label Apr 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@remcowesterhoud remcowesterhoud

@lzgabel lzgabel

Labels
kind/feature Categorizes an issue or PR as a feature, i.e. new behavior version:8.2.0-alpha1 Marks an issue as being completely or in parts released in 8.2.0-alpha1 version:8.2.0 Marks an issue as being completely or in parts released in 8.2.0
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat(bpmn-model): support escalation events lzgabel/zeebe
4 participants
@npepinpe @korthout @remcowesterhoud @lzgabel