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.

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

Support correlations for DataEntries in JPA-View #1001

Closed
MichaelVonB opened this issue Jun 17, 2024 · 0 comments · Fixed by #1006
Closed

Support correlations for DataEntries in JPA-View #1001

MichaelVonB opened this issue Jun 17, 2024 · 0 comments · Fixed by #1006
Assignees
Labels
Prio: Must This feature must be implemented in current milestone. Status: In progress Assignee is working on this issue. Type: breaking This is a breaking change. Take care while migrating. Type: enhancement New feature or request
Milestone

Comments

@MichaelVonB
Copy link
Contributor

Scenario

  • camunda-bpm-taskpool version: current
  • Camunda BPM version: current
  • Description of your use case: We want to correlate DataEntries to other DataEntries and Query with by payload attributes of correlated DataEntries

Current Behaviour

Currently the view api allows to specify correlations for DataEntries. However this field is ignored in the JPA-View.

Wanted Behaviour

  • Don't ignore Correlation in JPA
  • Support a configurable mechanism to control query behavior in JPA to query DataEntry correlated payload attributes.

Possible Workarounds

None

@MichaelVonB MichaelVonB added Type: enhancement New feature or request Status: In progress Assignee is working on this issue. Prio: Must This feature must be implemented in current milestone. Type: breaking This is a breaking change. Take care while migrating. labels Jun 17, 2024
@MichaelVonB MichaelVonB added this to the 4.1.7 milestone Jun 17, 2024
MichaelVonB pushed a commit that referenced this issue Jun 17, 2024
@MichaelVonB MichaelVonB linked a pull request Jun 18, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Prio: Must This feature must be implemented in current milestone. Status: In progress Assignee is working on this issue. Type: breaking This is a breaking change. Take care while migrating. Type: enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants