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

I can get history cleanup window configuration via REST

      When

      • I call "get history cleanup configuration" REST endpoint

      Then

      • I get historyCleanupBatchWindowStartTime and historyCleanupBatchWindowEndTime as datetime with timezone values, which represent current or next batch window

      Example:
      batch window is configured to 23:00 - 01:00
      now 07.09.2017 16:00 -> return 07.09.2017 23:00:00+0200 - 08.09.2017 01:00:00+0200
      now 07.09.2017 23:15 -> return 07.09.2017 23:00:00+0200 - 08.09.2017 01:00:00+0200
      now 08.09.2017 00:05 -> return 08.09.2017 23:00:00+0200 - 09.09.2017 01:00:00+0200
      now 08.09.2017 02:00 -> return 08.09.2017 23:00:00+0200 - 09.09.2017 01:00:00+0200

      Hints:

      • we should create some HistoryCleanupConfigurationDto, as may be in the future more data about history cleanup configuration will be needed in REST API
      • there are some related methods in HistoryCleanupHelper class, probably we can extend it with new methods

        This is the controller panel for Smart Panels app

            [CAM-8195] I can get history cleanup window configuration via REST

            Svetlana Dorokhova created issue -
            Svetlana Dorokhova made changes -
            Summary Original: I can get history cleanup configuration via REST New: I can get history cleanup window configuration via REST
            Svetlana Dorokhova made changes -
            Description Original: When
            * I call "get history cleanup configuration" REST endpoint

            Then
            * I get historyCleanupBatchWindowStartTime and historyCleanupBatchWindowTime as datetime with timezone values, date is not important (may be 01.01.1970), only time is meaningful

            Example:
            batch window is configured to 23:00 - 01:00 -> return 01.01.1970 23:00:00+0200 - 01.01.1970 01:00:00+0200

            Hints:
            * we should create some HistoryCleanupConfigurationDto, as may be in the future more data about history cleanup configuration will be needed in REST API
            New: When
            * I call "get history cleanup configuration" REST endpoint

            Then
            * I get historyCleanupBatchWindowStartTime and historyCleanupBatchWindowTime as datetime with timezone values, which represent current or next batch window

            Example:
            batch window is configured to 23:00 - 01:00
            now 07.09.2017 16:00 -> return 07.09.2017 23:00:00+0200 - 08.09.2017 01:00:00+0200
            now 07.09.2017 23:15 -> return 07.09.2017 23:00:00+0200 - 08.09.2017 01:00:00+0200
            now 08.09.2017 00:05 -> return 08.09.2017 23:00:00+0200 - 09.09.2017 01:00:00+0200
            now 08.09.2017 02:00 -> return 08.09.2017 23:00:00+0200 - 09.09.2017 01:00:00+0200

            Hints:
            * we should create some HistoryCleanupConfigurationDto, as may be in the future more data about history cleanup configuration will be needed in REST API
            * there are some related methods in {{HistoryCleanupHelper}} class, probably we can extend it with new methods
            Svetlana Dorokhova made changes -
            Fix Version/s New: 7.8.0 [ 14894 ]
            Roman Smirnov made changes -
            Assignee New: Anna [ anna.pazola ]
            Svetlana Dorokhova made changes -
            Description Original: When
            * I call "get history cleanup configuration" REST endpoint

            Then
            * I get historyCleanupBatchWindowStartTime and historyCleanupBatchWindowTime as datetime with timezone values, which represent current or next batch window

            Example:
            batch window is configured to 23:00 - 01:00
            now 07.09.2017 16:00 -> return 07.09.2017 23:00:00+0200 - 08.09.2017 01:00:00+0200
            now 07.09.2017 23:15 -> return 07.09.2017 23:00:00+0200 - 08.09.2017 01:00:00+0200
            now 08.09.2017 00:05 -> return 08.09.2017 23:00:00+0200 - 09.09.2017 01:00:00+0200
            now 08.09.2017 02:00 -> return 08.09.2017 23:00:00+0200 - 09.09.2017 01:00:00+0200

            Hints:
            * we should create some HistoryCleanupConfigurationDto, as may be in the future more data about history cleanup configuration will be needed in REST API
            * there are some related methods in {{HistoryCleanupHelper}} class, probably we can extend it with new methods
            New: When
            * I call "get history cleanup configuration" REST endpoint

            Then
            * I get historyCleanupBatchWindowStartTime and historyCleanupBatchWindowEndTime as datetime with timezone values, which represent current or next batch window

            Example:
            batch window is configured to 23:00 - 01:00
            now 07.09.2017 16:00 -> return 07.09.2017 23:00:00+0200 - 08.09.2017 01:00:00+0200
            now 07.09.2017 23:15 -> return 07.09.2017 23:00:00+0200 - 08.09.2017 01:00:00+0200
            now 08.09.2017 00:05 -> return 08.09.2017 23:00:00+0200 - 09.09.2017 01:00:00+0200
            now 08.09.2017 02:00 -> return 08.09.2017 23:00:00+0200 - 09.09.2017 01:00:00+0200

            Hints:
            * we should create some HistoryCleanupConfigurationDto, as may be in the future more data about history cleanup configuration will be needed in REST API
            * there are some related methods in {{HistoryCleanupHelper}} class, probably we can extend it with new methods
            Roman Smirnov made changes -
            Rank New: Ranked higher
            Seif made changes -
            Link New: This issue is depended on by CAM-7860 [ CAM-7860 ]

            Seif added a comment -

            svetlana.dorokhova Information is correct.

            Seif added a comment - svetlana.dorokhova Information is correct.
            Anna made changes -
            Status Original: Open [ 1 ] New: In Progress [ 3 ]

              svetlana.dorokhova Svetlana Dorokhova
              svetlana.dorokhova Svetlana Dorokhova
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: