Clash Detection Suppression Rules
Updates a clash detection suppression rule for the specified criteria and returns the id of the successfully updated rule.
- Discover rule ids by calling GET /clashdetection/suppressionrules
Authorization header with valid Bearer token for scope
For more documentation on authorization and how to get access token visit OAUTH2 Authorization page.
This response indicates that request lacks valid authentication credentials. Access token might not been provided, issued by the wrong issuer, does not have required scopes or request headers were malformed.
This response indicates that the specified rule was not found.
The 422 (Unprocessable Entity) status code indicates that the request cannot be processed by the server due to a client error (e.g. malformed request syntax)
Specify the rule criteria to update a clash detection suppression rule.
Contains error information.
Gives details for an error that occurred while handling the request. Note that clients MUST NOT assume that every failed request will produce an object of this schema, or that all of the properties in the response will be non-null, as the error may have prevented this response from being constructed.