Uploaded image for project: 'camunda BPM'
  1. camunda BPM
  2. CAM-14073

Improve use of job start and end events in spring

    • Icon: Feature Request Feature Request
    • Resolution: Unresolved
    • Icon: L3 - Default 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

            Tobias Conz created issue -
            Tobias Conz made changes -
            Link New: This issue is related to SUPPORT-10381 [ SUPPORT-10381 ]

            I would change

             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.

            to

             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.

            to be more clear.

            Marc Dörflinger added a comment - I would change  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. to  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. to be more clear.
            Marc Dörflinger made changes -
            Mentioned Roles
            Marc Dörflinger made changes -
            Mentioned Groups
            Tobias Conz made changes -
            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):*
            Tobias Conz made changes -
            Mentioned Roles
            Tobias Conz made changes -
            Mentioned Groups
            Tobias Conz made changes -
            Labels Original: PM async-continuation New: PM async-continuation engine

            This ticket was migrated to github: https://github.com/camunda/camunda-bpm-platform/issues/2722. Please use this link for any future references and continue any discussion there.

            Thorben Lindhauer added a comment - This ticket was migrated to github: https://github.com/camunda/camunda-bpm-platform/issues/2722 . Please use this link for any future references and continue any discussion there.

              Unassigned Unassigned
              tobias.conz Tobias Conz
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: