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

Create EscalationRecord and EscalationIntent #10762

Closed
Tracked by #10682
remcowesterhoud opened this issue Oct 19, 2022 · 2 comments · Fixed by #10780
Closed
Tracked by #10682

Create EscalationRecord and EscalationIntent #10762

remcowesterhoud opened this issue Oct 19, 2022 · 2 comments · Fixed by #10780
Assignees
@remcowesterhoud
Labels
kind/feature Categorizes an issue or PR as a feature, i.e. new behavior scope/broker Marks an issue or PR to appear in the broker section of the changelog 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

@remcowesterhoud
Copy link
Contributor

remcowesterhoud commented Oct 19, 2022 •
edited

Description

A new EscalationRecord and EscalationIntent need to be introduced.

Record

Refer to the developer handbook for instruction on how to add a record.

Properties:

  • processInstanceKey - The key of the process instance
  • escalationCode - The code of the escalation
  • throwElementId - The id of the escalation throw event
  • catchElementId - The id of the escalation catch event

Intent

Create the EscalationIntent enum. Possible values:

  • ESCALATED
  • NOT_ESCALATED
@remcowesterhoud remcowesterhoud mentioned this issue Oct 19, 2022
Closed
15 tasks
@remcowesterhoud remcowesterhoud added kind/feature Categorizes an issue or PR as a feature, i.e. new behavior scope/broker Marks an issue or PR to appear in the broker section of the changelog labels Oct 19, 2022
@remcowesterhoud remcowesterhoud mentioned this issue Oct 19, 2022
Closed
@remcowesterhoud
Copy link
Contributor Author

It's probably an easy win to do #10767 as part of this issue.

@lzgabel lzgabel mentioned this issue Oct 20, 2022
Merged
10 tasks
@remcowesterhoud remcowesterhoud self-assigned this Oct 21, 2022
@remcowesterhoud
Copy link
Contributor Author

Hi @lzgabel! As we've discussed earlier I've had a chat about the contents we need in this record. I have modified the issue, please have a look 🙂

@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

Labels
kind/feature Categorizes an issue or PR as a feature, i.e. new behavior scope/broker Marks an issue or PR to appear in the broker section of the changelog 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.

Add record and intent for escalation lzgabel/zeebe
3 participants
@npepinpe @korthout @remcowesterhoud