-
Feature Request
-
Resolution: Fixed
-
L3 - Default
-
None
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
Summary | Original: I can get history cleanup configuration via REST | New: I can get history cleanup window configuration via REST |
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 |
Fix Version/s | New: 7.8.0 [ 14894 ] |
Assignee | New: Anna [ anna.pazola ] |
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 |
Rank | New: Ranked higher |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
svetlana.dorokhova Information is correct.