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

Tasklist: Claim history does not work with REST API

XMLWordPrintable

    • Icon: Bug Report Bug Report
    • Resolution: Won't Do
    • Icon: L3 - Default L3 - Default
    • None
    • 7.16.0
    • tasklist
    • None

      Environment (Required on creation): 7.16.0

      Description (Required on creation; please attach any relevant screenshots, stacktraces, log files, etc. to the ticket):

       

      1. instantiate a process, advance token to a user task
      2. log in to tasklist, note the task
      3. Use the REST API to claim it, then refresh the tasklist UI
      4. notice that it is now claimed, but now click the "History" tab in the task UI.  Notice that there is no entry.

      Steps to reproduce (Required on creation):

      I recorded a quick video to show you.

      https://drive.google.com/file/d/1bp120QIKBKYVXTZInkm2AQAYjyyumqef/view?usp=sharing 

      Observed Behavior (Required on creation):

      Expected behavior (Required on creation):

      Root Cause (Required on prioritization):

      Solution Ideas (Optional):

      Hints (optional):

       

      Please advise if I made a mistake that I can pass on to the partner that made me aware of this (Ernst and Young).

        This is the controller panel for Smart Panels app

          1. image-2021-10-25-12-27-44-454.png
            image-2021-10-25-12-27-44-454.png
            111 kB

            [CAM-14037] Tasklist: Claim history does not work with REST API

            Chris Allen added a comment -

            Looks like the partner figured out the root cause.  See below.  You can choose what to do with the ticket, but I am no longer blocked.

            Chris Allen added a comment - Looks like the partner figured out the root cause.  See below.  You can choose what to do with the ticket, but I am no longer blocked.

            Tobias Metzke-Bernstein added a comment -

            Hey chris.allen,

            thanks for bringing this up.

            The customer figured it out already and that behavior is actually also expected.
            Note that you can also disable restrictUserOperationLogToAuthenticatedUsers, which should log those actions in the operation log as well for unauthenticated REST API calls.

            I will close this since the behavior is expected.
            Let us know if you have further questions or think the ticket should be reopenend.

            Best,
            Tobias

            Tobias Metzke-Bernstein added a comment - Hey chris.allen , thanks for bringing this up. The customer figured it out already and that behavior is actually also expected. Note that you can also disable restrictUserOperationLogToAuthenticatedUsers , which should log those actions in the operation log as well for unauthenticated REST API calls. I will close this since the behavior is expected. Let us know if you have further questions or think the ticket should be reopenend. Best, Tobias

              Unassigned Unassigned
              chris.allen Chris Allen
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: