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

Jobs are pushed from relevant processors #12541

Closed
6 tasks done
Tracked by #11711
koevskinikola opened this issue Apr 24, 2023 · 0 comments · Fixed by #12741
Closed
6 tasks done
Tracked by #11711

Jobs are pushed from relevant processors #12541

koevskinikola opened this issue Apr 24, 2023 · 0 comments · Fixed by #12741
Assignees
@koevskinikola @berkaycanbc
Labels
component/engine kind/feature Categorizes an issue or PR as a feature, i.e. new behavior version:8.3.0-alpha2 Marks an issue as being completely or in parts released in 8.3.0-alpha2 version:8.3.0 Marks an issue as being completely or in parts released in 8.3.0

Comments

@koevskinikola
Copy link
Member

koevskinikola commented Apr 24, 2023 •
edited

Is your feature request related to a problem? Please describe.
The following Processor classes are able to push an activated job to a client.

Describe the solution you'd like
The BpmnJobActivationBehavior class is able to use the JobStreamer API to push jobs. The following steps need to be performed:

  • For an available JobStream get JobActivationProperties
  • Set deadline for JobRecord (using JobActivationProperties)
  • Set variables for JobRecord (using JobActivationProperties)
  • Set worker for JobRecord (using JobActivationProperties)
  • Activate job using a JobBatchRecord/JobBatchIntent.ACTIVATE
  • Push JobRecord on the JobStream through a SideEffectProducer

Describe alternatives you've considered
/

Additional context
Blocked by:
@koevskinikola koevskinikola added kind/feature Categorizes an issue or PR as a feature, i.e. new behavior component/engine labels Apr 24, 2023
@koevskinikola koevskinikola self-assigned this Apr 24, 2023
This was referenced Apr 24, 2023
Closed
Closed
Closed
Closed
Closed
Closed
Closed
@koevskinikola koevskinikola mentioned this issue May 11, 2023
Merged
14 tasks
@berkaycanbc berkaycanbc mentioned this issue May 22, 2023
Closed
@lenaschoenburg lenaschoenburg added the version:8.3.0-alpha2 Marks an issue as being completely or in parts released in 8.3.0-alpha2 label Jun 7, 2023
@megglos megglos added the version:8.3.0 Marks an issue as being completely or in parts released in 8.3.0 label Oct 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@koevskinikola koevskinikola

@berkaycanbc berkaycanbc

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

Successfully merging a pull request may close this issue.

Enable job pushing through job-related processors camunda/camunda
4 participants
@megglos @lenaschoenburg @koevskinikola @berkaycanbc