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

None end events calculation of output parameters #10613

Closed
hmeniz opened this issue Oct 5, 2022 · 2 comments · Fixed by #10618
Closed

None end events calculation of output parameters #10613

hmeniz opened this issue Oct 5, 2022 · 2 comments · Fixed by #10618
Assignees
@remcowesterhoud
Labels
good first issue Marks an issue as simple enough for first time contributors hacktoberfest Marks an issue as a candidate to be a Hacktoberfest contribution 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

@hmeniz
Copy link

hmeniz commented Oct 5, 2022 •
edited by saig0

Is your feature request related to a problem? Please describe.

Process does not calculate output parameters in “none end event”. Is there a chance to calculate these output parameters and put them in the process values without using the “message end event”?

Describe the solution you'd like

The process instance applies the output mappings when a none end event is reached. Similar to message end events.

image

Describe alternatives you've considered
For now, using "none throw event" or "message end event" for calculate output parameters are alternative solutions.

Additional context
We are using Camunda Platform 8 Self Managed and Desktop Modeler

Related camunda forum link: https://forum.camunda.io/t/camunda-8-end-event-output-parameters/40136

The following class controls the behavior of the event events: EndEventProcessor

New contributors could watch the video to learn more about how to extend the behavior of the end events.
@hmeniz hmeniz added the kind/feature Categorizes an issue or PR as a feature, i.e. new behavior label Oct 5, 2022
@saig0 saig0 added hacktoberfest Marks an issue as a candidate to be a Hacktoberfest contribution good first issue Marks an issue as simple enough for first time contributors labels Oct 6, 2022
@saig0
Copy link
Member

saig0 commented Oct 6, 2022

@hmeniz thank you for creating the issue. 👍

I see it as a valid use case. ✔️

@skayliu skayliu mentioned this issue Oct 6, 2022
Merged
10 tasks
@skayliu
Copy link
Contributor

skayliu commented Oct 6, 2022

Hi, @saig0, I've implemented this, please review it, thank you.

@remcowesterhoud remcowesterhoud self-assigned this Oct 10, 2022
zeebe-bors-camunda bot added a commit that referenced this issue Oct 10, 2022
@zeebe-bors-camunda @remcowesterhoud
@skayliu @deepthidevaki @dependabot
merge: #10609 #10618 #10629 #10649
dcb6a3a 
10609: Remove interrupted state on event subprocess activation r=remcowesterhoud a=remcowesterhoud

## Description

<!-- Please explain the changes you made here. -->
When an interrupting event sub process gets triggered it will terminate all active element in its flow scope and mark the flow scope as interrupted. With process instance modification it should be possible to re-activate element within the interrupted scope. Because of the interrupted state any activate commands get rejected, making this currently impossible.

With this change we will check if any of the activated elements is currently in an interrupted state. If this is the case we will remove this state, allowing elements within to be activated through a modification.

## Related issues

<!-- Which issues are closed by this PR or are related -->

closes #10477 



10618: feat(engine): Apply output mappings for none end events r=remcowesterhoud a=skayliu

## Description

<!-- Please explain the changes you made here. -->

Support none end event outputs.

## Related issues

<!-- Which issues are closed by this PR or are related -->

closes #10613 



10629: test(qa): verify backup when partition is replicated r=deepthidevaki a=deepthidevaki

## Description

- Verify backup when the partition is replicated.

## Related issues

closes #10387 


10649: deps(maven): bump aws-java-sdk-core from 1.12.318 to 1.12.319 r=oleschoenburg a=dependabot[bot]

Bumps [aws-java-sdk-core](https://github.com/aws/aws-sdk-java) from 1.12.318 to 1.12.319.
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a href="https://github.com/aws/aws-sdk-java/blob/master/CHANGELOG.md">aws-java-sdk-core's changelog</a>.</em></p>
<blockquote>
<h1><strong>1.12.319</strong> <strong>2022-10-07</strong></h1>
<h2><strong>AWS IoT Greengrass V2</strong></h2>
<ul>
<li>
<h3>Features</h3>
<ul>
<li>This release adds error status details for deployments and components that failed on a device and adds features to improve visibility into component installation.</li>
</ul>
</li>
</ul>
<h2><strong>Amazon CodeGuru Reviewer</strong></h2>
<ul>
<li>
<h3>Features</h3>
<ul>
<li>Documentation update to replace broken link.</li>
</ul>
</li>
</ul>
<h2><strong>Amazon QuickSight</strong></h2>
<ul>
<li>
<h3>Features</h3>
<ul>
<li>Amazon QuickSight now supports SecretsManager Secret ARN in place of CredentialPair for DataSource creation and update. This release also has some minor documentation updates and removes CountryCode as a required parameter in GeoSpatialColumnGroup</li>
</ul>
</li>
</ul>
<h2><strong>Elastic Load Balancing</strong></h2>
<ul>
<li>
<h3>Features</h3>
<ul>
<li>Gateway Load Balancer adds a new feature (target_failover) for customers to rebalance existing flows to a healthy target after marked unhealthy or deregistered. This allows graceful patching/upgrades of target appliances during maintenance windows, and helps reduce unhealthy target failover time.</li>
</ul>
</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/aws/aws-sdk-java/commit/e752d66f73b94f4c54d995b6bde56301ade507af"><code>e752d66</code></a> AWS SDK for Java 1.12.319</li>
<li><a href="https://github.com/aws/aws-sdk-java/commit/e176eb25613173ac59301716281018a837654589"><code>e176eb2</code></a> Update GitHub version number to 1.12.319-SNAPSHOT</li>
<li>See full diff in <a href="https://github.com/aws/aws-sdk-java/compare/1.12.318...1.12.319">compare view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=com.amazonaws:aws-java-sdk-core&package-manager=maven&previous-version=1.12.318&new-version=1.12.319)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting ``@dependabot` rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- ``@dependabot` rebase` will rebase this PR
- ``@dependabot` recreate` will recreate this PR, overwriting any edits that have been made to it
- ``@dependabot` merge` will merge this PR after your CI passes on it
- ``@dependabot` squash and merge` will squash and merge this PR after your CI passes on it
- ``@dependabot` cancel merge` will cancel a previously requested merge and block automerging
- ``@dependabot` reopen` will reopen this PR if it is closed
- ``@dependabot` close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- ``@dependabot` ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- ``@dependabot` ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- ``@dependabot` ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)


</details>

Co-authored-by: Remco Westerhoud <remco@westerhoud.nl>
Co-authored-by: skayliu <skay463@163.com>
Co-authored-by: Deepthi Devaki Akkoorath <deepthidevaki@gmail.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.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

Labels
good first issue Marks an issue as simple enough for first time contributors hacktoberfest Marks an issue as a candidate to be a Hacktoberfest contribution 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(engine): Apply output mappings for none end events skayliu/zeebe
6 participants
@npepinpe @korthout @saig0 @remcowesterhoud @skayliu @hmeniz