-
Feature Request
-
Resolution: Unresolved
-
L3 - Default
-
None
-
None
-
None
Title: Improve use of job start and end events in spring
User Story (Required on creation):
As a developer i would like to provide the "business team" the possibility to cover e.g. the authentication at the beginning /end of an asynchronous job, so they can focus on the business logic.
Functional Requirements (Required before implementation):
I can currently use a CommandInterceptor to execute code (E.g. logging, system authentication) at the process starts and ends for a Camunda Engine embedded in a Spring Boot application.
Sending an Event JobStarted and JobFinished to the Spring Eventing Bridge, without plugins and interceptors, would be a more easily understandable implementation.
Limitations of Scope (Optional):
Hints (Optional):
This is the controller panel for Smart Panels app
[CAM-14073] Improve use of job start and end events in spring
Link | New: This issue is related to SUPPORT-10381 [ SUPPORT-10381 ] |
Mentioned Roles |
Mentioned Groups |
Description |
Original:
*Title:* Improve use of job start and end events in spring
*User Story (Required on creation):* As a developer i would like to provide the "business team" the possibility to cover e.g. the authentication at the beginning / end of a process, so they can focus on the business logic. *Functional Requirements (Required before implementation):* I can currently use a CommandInterceptor to execute code (E.g. logging, system authentication) at the process starts and ends for a Camunda Engine embedded in a Spring Boot application. Sending an Event JobStarted and JobFinished to the Spring Eventing Bridge, without plugins and interceptors, would be a more easily understandable implementation. *Limitations of Scope (Optional):* *Hints (Optional):* |
New:
*Title:* Improve use of job start and end events in spring
*User Story (Required on creation):* As a developer i would like to provide the "business team" the possibility to cover e.g. the authentication at the beginning /end of an {color:#172b4d}asynchronous job{color}, so they can focus on the business logic. *Functional Requirements (Required before implementation):* I can currently use a CommandInterceptor to execute code (E.g. logging, system authentication) at the process starts and ends for a Camunda Engine embedded in a Spring Boot application. Sending an Event JobStarted and JobFinished to the Spring Eventing Bridge, without plugins and interceptors, would be a more easily understandable implementation. *Limitations of Scope (Optional):* *Hints (Optional):* |
Mentioned Roles |
Mentioned Groups |
Labels | Original: PM async-continuation | New: PM async-continuation engine |
I would change
to
to be more clear.