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

I can retrieve Identitylinks from History

    Details

    • Type: Feature Request
    • Status: Closed
    • Priority: L3 - Default
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 7.5.0, 7.5.0-alpha4
    • Component/s: engine
    • Labels:
    • Title Keywords:
      Identitylink HistroicTaskInstanceQuery

      Description

      AT:

      • Adding and deleting an identity link is logged to history (for both task and process instance identity links) as HistoricIdentityLinkLogs
      • When a task is assigned to a user, a historic identity link of type "ASSIGNEE" and history event type "add" is created
      • When a task is un-assigned to a user, a historic identity link of type "ASSIGNEE" and history event type "delete" is created
      • When a task is set as the owner of a user, a historic identity link of type "OWNER" and history event type "add" is created
      • When a user is unset as the owner of a task, a historic identity link of type "OWNER" and history event type "delete" is created
      • I can query for HistoricIndentityLogs using the history service
      • When performing a historic task query I can restrict on the historic identity links of any type (.taskInvolvedUser(...) and .taskInvolvedGroup()). This will return all the tasks for which an identity link pointing to that user id / group id exists
      • When performing a historic task query I can restrict on the historic identity of type "candidate" links (.taskHadCandidateUser(...) and .taskHadCandidateGroup())

      OLD DESCRIPTION

      We are currently migrating our Activiti Engine to the Camunda Engine.

      But Camunda misses an essential Activiti-feature we are using.
      In Activiti 5.16+ we were able to get call the method .taskInvoledUser() on an HistoricTaskInstanceQuery. In Camunda we can call it on TaskQuery only.
      (Since 5.17 Activiti moved this method to the superclass TaskInfoQuery)
      http://activiti.org/javadocs/org/activiti/engine/task/TaskInfoQuery.html#taskInvolvedUser(java.lang.String)

      Before we can switch to Camunda completly and start getting enterprise support we need to get the information Activiti provides us with this method.

        Issue Links

          Activity

          Hide
          meyer Daniel Meyer added a comment -

          Hi Niklas,

          thank you for this request. The next version of Camunda is 7.4 and it will be released end of this month.
          We will not be able to incorporate this feature request in that version.

          You mention that you are currently in discssions with an account manager at camunda.
          You should address this with him so that he can take care that this issue gets the necessary attention.

          Thanks!
          Daniel

          Show
          meyer Daniel Meyer added a comment - Hi Niklas, thank you for this request. The next version of Camunda is 7.4 and it will be released end of this month. We will not be able to incorporate this feature request in that version. You mention that you are currently in discssions with an account manager at camunda. You should address this with him so that he can take care that this issue gets the necessary attention. Thanks! Daniel
          Hide
          mabertran Manu Bertran added a comment -
          • I think would be great to implement methods .taskInvolvedGroupIn(List<String> user) and .taskHadCandidateGroupIn(List<String> groups) as well
          • Another feature I think would be very useful would be to have methods HistoricTaskQuery.taskHadCandidateUserOrCandidateGroupIn(String user, List<String> groups). As this exceeds the scope of this issue, I created a new one: CAM-5698
            • Finally, the twin method in TaskQuery would be very useful (TaskQuery.taskCandidateUserOrCandidateGroupIn(String user, List<String> groups). (I also included this feature in CAM-5698.
          Show
          mabertran Manu Bertran added a comment - I think would be great to implement methods .taskInvolvedGroupIn(List<String> user) and .taskHadCandidateGroupIn(List<String> groups) as well Another feature I think would be very useful would be to have methods HistoricTaskQuery.taskHadCandidateUserOrCandidateGroupIn(String user, List<String> groups). As this exceeds the scope of this issue, I created a new one: CAM-5698 Finally, the twin method in TaskQuery would be very useful (TaskQuery.taskCandidateUserOrCandidateGroupIn(String user, List<String> groups). (I also included this feature in CAM-5698 .

            People

            • Assignee:
              roman.smirnov Smirnov Roman
              Reporter:
              niklasm Niklas Mohrdieck
            • Votes:
              1 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development