Details

      Description

      AT:

      • historic identity link logs have been imported
      • user task in the process instance index is enriched with candidate groups, candidate users and assingees
      • for candidate groups and users only those groups/users are being kept that were still assigned when the task has been completed
      • for assignee only the last assignee is being kept
      • in case there has been no assingee the field is null
      • in case there has been no candidate user/group those entries correspond to an emtpy list in the Elasticsearch index
      • update script is adjusted accordingly, so that it adds the three new fields to the process instance index
      • add the new max page size config to the configuration documentation in the technical guide
      • add the historic identity links to the list of imported entities in the technical guide

      Context:
      We need the historic identity link logs to find out which were the assigned candidate users/groups + assginee for the each user task.

      Hint:
      With CAM-10264 a new Optimize Endpoint has been added to the engine to retrieve the historic link information.

        Activity

        johannes.heinemann Johannes Heinemann created issue -
        johannes.heinemann Johannes Heinemann made changes -
        Field Original Value New Value
        Status Open [ 1 ] In Specification [ 10000 ]
        johannes.heinemann Johannes Heinemann made changes -
        Description *AT:*
        * historic identity link logs have been imported
        * user task in the process instance index is enriched with candidate groups, candidate users and assingees
        * for candidate groups and users only those groups/users are being kept that were still assigned when the task has been completed
        * for assignee only the last assignee is being kept
        * update script is adjusted accordingly, so that it adds the three new fields to the process instance index
        *AT:*
        * historic identity link logs have been imported
        * user task in the process instance index is enriched with candidate groups, candidate users and assingees
        * for candidate groups and users only those groups/users are being kept that were still assigned when the task has been completed
        * for assignee only the last assignee is being kept
        * update script is adjusted accordingly, so that it adds the three new fields to the process instance index

        *Hint:*
        With CAM-10264 a new Optimize Endpoint has been added to the engine to retrieve the historic link information.
        johannes.heinemann Johannes Heinemann made changes -
        Description *AT:*
        * historic identity link logs have been imported
        * user task in the process instance index is enriched with candidate groups, candidate users and assingees
        * for candidate groups and users only those groups/users are being kept that were still assigned when the task has been completed
        * for assignee only the last assignee is being kept
        * update script is adjusted accordingly, so that it adds the three new fields to the process instance index

        *Hint:*
        With CAM-10264 a new Optimize Endpoint has been added to the engine to retrieve the historic link information.
        *AT:*
        * historic identity link logs have been imported
        * user task in the process instance index is enriched with candidate groups, candidate users and assingees
        * for candidate groups and users only those groups/users are being kept that were still assigned when the task has been completed
        * for assignee only the last assignee is being kept
        * in case there has been no assingee the field is null
        * in case there has been no candidate user/group those entries correspond to an emtpy list in the Elasticsearch index
        * update script is adjusted accordingly, so that it adds the three new fields to the process instance index

        *Context:*
        We need the historic identity link logs to find out which were the assigned candidate users/groups + assginee for the each user task.

        *Hint:*
        With CAM-10264 a new Optimize Endpoint has been added to the engine to retrieve the historic link information.
        johannes.heinemann Johannes Heinemann made changes -
        Status In Specification [ 10000 ] In Development [ 10312 ]
        johannes.heinemann Johannes Heinemann made changes -
        Status In Development [ 10312 ] In Specification [ 10000 ]
        johannes.heinemann Johannes Heinemann made changes -
        Status In Specification [ 10000 ] In Development [ 10312 ]
        johannes.heinemann Johannes Heinemann made changes -
        Description *AT:*
        * historic identity link logs have been imported
        * user task in the process instance index is enriched with candidate groups, candidate users and assingees
        * for candidate groups and users only those groups/users are being kept that were still assigned when the task has been completed
        * for assignee only the last assignee is being kept
        * in case there has been no assingee the field is null
        * in case there has been no candidate user/group those entries correspond to an emtpy list in the Elasticsearch index
        * update script is adjusted accordingly, so that it adds the three new fields to the process instance index

        *Context:*
        We need the historic identity link logs to find out which were the assigned candidate users/groups + assginee for the each user task.

        *Hint:*
        With CAM-10264 a new Optimize Endpoint has been added to the engine to retrieve the historic link information.
        *AT:*
        * historic identity link logs have been imported
        * user task in the process instance index is enriched with candidate groups, candidate users and assingees
        * for candidate groups and users only those groups/users are being kept that were still assigned when the task has been completed
        * for assignee only the last assignee is being kept
        * in case there has been no assingee the field is null
        * in case there has been no candidate user/group those entries correspond to an emtpy list in the Elasticsearch index
        * update script is adjusted accordingly, so that it adds the three new fields to the process instance index
        * add the new max page size config to the configuration documentation in the technical guide
        * add the historic identity links to the list of imported entities in the technical guide

        *Context:*
        We need the historic identity link logs to find out which were the assigned candidate users/groups + assginee for the each user task.

        *Hint:*
        With CAM-10264 a new Optimize Endpoint has been added to the engine to retrieve the historic link information.
        johannes.heinemann Johannes Heinemann made changes -
        Status In Development [ 10312 ] In Review [ 10212 ]
        Assignee Johannes Heinemann [ johannes.heinemann ] Sebastian Bathke [ sebastian.bathke ]
        sebastian.bathke Sebastian Bathke made changes -
        Assignee Sebastian Bathke [ sebastian.bathke ] Michael Wagner [ michael.wagner ]
        michael.wagner Michael Wagner made changes -
        Assignee Michael Wagner [ michael.wagner ]
        Status In Review [ 10212 ] Done [ 10010 ]
        Resolution Done [ 10000 ]
        sebastian.stamm Sebastian Stamm made changes -
        Fix Version/s 2.5.0 [ 15385 ]

          People

          • Assignee:
            Unassigned
            Reporter:
            johannes.heinemann Johannes Heinemann
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: