(OO) Support Tip: How to purge data for executions of a specific flow

Since OO 10.51, it has been possible to purge flow execution data of a specific flow by calling the /executions REST API. For example, sending a DELETE http request like below to your Central purges flow execution data of the flow with UUID 79e6def8-435a-4238-8c92-b168d82f24ed which ended before 2018-08-29 6:38:39 360 UTC.

  /oo/rest/latest/executions?endedBefore=1535524719360&flowUuids=79e6def8-435a-4238-8c92-b168d82f24ed

Please note that the 'endedBefore' request parameter is mandatory and its value must be an epoch(unix) timestamp in milliseconds.
Also if you use get an epoch(unix) timestamp from the 'Library/Utility Operations/Date and Time/Get Epoch Time' operation in a Base CP, the operation returns a timestamp not in milliseconds but in seconds.

See the following manual for more details about the REST API.

https://docs.microfocus.com/itom/Operations_Orchestration:2018.05/Develop/Working_with_API/Purge_Execution_Step_Data

Parents Reply Children
  • Hello,

    The problem with this API is that if we use both purgeItems and flowUuids, the Response entity body is not accurate and we can't use a loop to purge until all is done.

    If the request's parameters involve purging 1 execution, then:

    • if purgeItems is not specified, the second request returns 0 ( the first call has purged all datas)
    • if purgeItems is specified, then the second request (and all subsequent ones) still return 1 (Datas have been purged but execution summary remain).

    So we can't loop until  Response entity body is 0 with those two parameters.