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

For a variable change, I can determine the user who caused it

    Details

    • Type: Feature Request
    • Status: Closed
    • Priority: L3 - Default
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 7.7.0, 7.7.0-alpha2
    • Component/s: engine
    • Labels:

      Description

      AT:

      • when a variable is set through API (Task API / Runtime API), a user operation log entry is written

      ====

      Currently this variable change information resides in the table ACT_HI_DETAIL.

      Solution possibilities:

      1. link historic details to user operation log entries
      2. add a USER_ID_ column to ACT_HI_DETAIL. Might be either to implement than option one, but it is also less clear when the field should be populated (only when a variable is set via API, as with user operation logs, or whenever a historic detail is written in the context of a logged in user, e.g. by a java delegate, etc.)

        Activity

        Hide
        svetlana.dorokhova Svetlana Dorokhova added a comment -

        What was done:

        1. ACT_HI_DETAIL was extended with operationId column, which "references" semantically to operationId column in ACT_HI_OP_LOG table.
        2. Additional filtering field was added to GET /history/detail request. So the sequence of actions can be:
          • GET /history/user-operation with needed filtering - > returns operationId for each operation log record.
          • Use operationId value to request for history details -> will return all variable changes within the requested operation
        Show
        svetlana.dorokhova Svetlana Dorokhova added a comment - What was done: ACT_HI_DETAIL was extended with operationId column, which "references" semantically to operationId column in ACT_HI_OP_LOG table. Additional filtering field was added to GET /history/detail request. So the sequence of actions can be: GET /history/user-operation with needed filtering - > returns operationId for each operation log record. Use operationId value to request for history details -> will return all variable changes within the requested operation

          People

          • Assignee:
            thorben.lindhauer Thorben Lindhauer
            Reporter:
            thorben.lindhauer Thorben Lindhauer
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development