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

I can query a historic task instance report via REST api

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Fixed
    • Icon: L3 - Default L3 - Default
    • 7.6.0, 7.6.0-alpha3
    • None
    • engine

      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

        This is the controller panel for Smart Panels app

            [CAM-6382] I can query a historic task instance report via REST api

            Stefan 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.

            Stefan 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.

            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?

            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?

            Christopher Kujawa 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

            Christopher Kujawa 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

            Christopher Kujawa 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.

            Christopher Kujawa 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.

              matthijs.burke Matthijs
              stefan.hentschel Stefan
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: