Is your feature request related to a problem? Please describe.
Right now the custom filter for archival accepts only string type value in actedOn field and there is no field for actionGroup here.
This restricts the user to archive only one entity at a time, increasing the number of '/archive' calls and hence increasing the files => which inturn affects the time taken by '/export' job since it has to get data one by one from each file and thus increasing latency.
Describe the solution you'd like
Here we can use a string array for actedOn and groupBy fields allowing user to archive all at once.
Is your feature request related to a problem? Please describe.
Right now the custom filter for archival accepts only string type value in actedOn field and there is no field for actionGroup here. This restricts the user to archive only one entity at a time, increasing the number of '/archive' calls and hence increasing the files => which inturn affects the time taken by '/export' job since it has to get data one by one from each file and thus increasing latency.
Describe the solution you'd like Here we can use a string array for actedOn and groupBy fields allowing user to archive all at once.