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

I can query a historic task instance report via REST api

    Details

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

      Description

      AT:

      – there is a rest endpoint '/history/task/report'
      – There are parameters called 'finishedBefore' and 'finishedAfter'
      – The parameters allows a more specific granulation for tasks
      – the dateformat is: yyyy-MM-dd'T'HH:mm:ss

        Issue Links

          Activity

          Hide
          stefan.hentschel Stefan Hentschel added a comment -

          After a short discussion with Christopher Zell we decided:

          • HistoricTaskInstanceReportResultDto is needed for the rest api.
          • The overhead of implementing an enum for groupBy is greater than the use so we only converted the groupBy check into a static string variable.
          Show
          stefan.hentschel Stefan Hentschel added a comment - After a short discussion with Christopher Zell we decided: HistoricTaskInstanceReportResultDto is needed for the rest api. The overhead of implementing an enum for groupBy is greater than the use so we only converted the groupBy check into a static string variable.
          Hide
          meyer Daniel Meyer added a comment -

          Christopher Zell the completedAfter / before methods are named "completed" because they restrict on the end time / completion time. Does that make sense to you?

          Show
          meyer Daniel Meyer added a comment - Christopher Zell the completedAfter / before methods are named "completed" because they restrict on the end time / completion time. Does that make sense to you?
          Hide
          christopher.zell Christopher Zell added a comment -

          Hey Stefan Hentschel,

          i added some more test cases.
          Please update the documentation (remove subresource etc.).
          Also add more information to the Resource not only `Query for a historic task report.`

          Cheers,
          Chris

          Show
          christopher.zell Christopher Zell added a comment - Hey Stefan Hentschel , i added some more test cases. Please update the documentation (remove subresource etc.). Also add more information to the Resource not only `Query for a historic task report.` Cheers, Chris
          Hide
          christopher.zell Christopher Zell added a comment -

          Stefan Hentschel I would suggest to merge both pages together. So if a new report type is added only the page have to be edit and not a hole page created.
          Also the other resources are documented the same way. For example external task,
          Activity Instance , etc.

          Show
          christopher.zell Christopher Zell added a comment - Stefan Hentschel I would suggest to merge both pages together. So if a new report type is added only the page have to be edit and not a hole page created. Also the other resources are documented the same way. For example external task , Activity Instance , etc.

            People

            • Assignee:
              matthijs.burke Matthijs Burke
              Reporter:
              stefan.hentschel Stefan Hentschel
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development