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

Allow to lock a certain external task by id

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Fixed
    • Icon: L3 - Default L3 - Default
    • 7.15.0-alpha3, 7.15.0
    • None
    • None
    • None

      AT:

      • It is possible to lock a certain external task (identified by id) for a workerId
      • In Java API and REST API
      • Java External Task Client

      Background:

      • Currently it is not possible to define any filters when doing fetchAndLock. The simplest workaround is to do an external-task query (existing) and then lock the tasks you are interested in one by one yourself.

        This is the controller panel for Smart Panels app

          1.
          		 The ExternalTaskService can lock a task by its id Sub-task Closed Unassigned
          2.
          		 An External Task Rest endpoint is available to lock a task by its id Sub-task Closed Nikola Koevski
          3.
          		 The External Task (Java) Client can lock a task by its id Sub-task Closed Unassigned
          4.
          		 The External Task (JS) Client can lock a task by its id Sub-task Closed Hariharan Parasuraman

            [CAM-7170] Allow to lock a certain external task by id

            Bernd Ruecker created issue -
            Thorben Lindhauer made changes -
            Workflow Original: camunda BPM [ 41279 ] New: Backup_camunda BPM [ 56124 ]
            Emma Pollum made changes -
            Assignee New: Emma Pollum [ emma.pollum ]
            Roman Smirnov made changes -
            Assignee Original: Emma Pollum [ emma.pollum ]
            Roman Smirnov made changes -
            Link New: This issue is related to SUPPORT-6655 [ SUPPORT-6655 ]
            Andre made changes -
            Labels New: Potential_for_7.15
            Andre made changes -
            Assignee New: Andre [ andre.bappert ]

            Claude Dumas added a comment - - edited

            Fully agree with that request. Sometimes we need to get the tasks and then decide thereafter which ones we want to lock, according to processing made on the task data. We need a way to separate the Fetch from the Lock.
            I propose to implement a Lock API (there is already an Unlock API !). It must of course handles gracefully the case where multiple Lock requests are made at the same time for the same task.

            Claude Dumas added a comment - - edited Fully agree with that request. Sometimes we need to get the tasks and then decide thereafter which ones we want to lock, according to processing made on the task data. We need a way to separate the Fetch from the Lock. I propose to implement a Lock API (there is already an Unlock API !). It must of course handles gracefully the case where multiple Lock requests are made at the same time for the same task.
            Claude Dumas made changes -
            Mentioned Roles
            Claude Dumas made changes -
            Mentioned Groups

              martin.stamm Martin Stamm
              ruecker Bernd Ruecker
              Votes:
              5 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: