riskHoldLabelsWithHttpInfo method
Place or release a litigation hold on named records
Places or releases a litigation hold on named records. A hold is a fact about the RECORD, not about the world: it says retention may not dispose of this row, and it asserts nothing about what happened. So it is not a field on an assertion and it is not folded into the content digest — carried there it was silently a no-op on any record that already existed, since re-filing the same assertion with a hold flag produced the same digest, the insert was ignored, and the caller was answered duplicate while the hold it asked for was never placed. This op is the one way a hold moves, in either direction, and the move is written to the audit log. Every named id is this tenant's or is nothing. The statement runs against the tenant's own file, which holds no other tenant's rows and has no column that could name one.
Note: This method returns the HTTP Response.
Parameters:
- RiskHoldIn riskHoldIn (required):
Implementation
Future<Response> riskHoldLabelsWithHttpInfo(RiskHoldIn riskHoldIn,) async {
// ignore: prefer_const_declarations
final path = r'/v1/label/hold';
// ignore: prefer_final_locals
Object? postBody = riskHoldIn;
final queryParams = <QueryParam>[];
final headerParams = <String, String>{};
final formParams = <String, String>{};
const contentTypes = <String>['application/json'];
return apiClient.invokeAPI(
path,
'POST',
queryParams,
postBody,
headerParams,
formParams,
contentTypes.isEmpty ? null : contentTypes.first,
);
}