Create a scoring range

post

/fscmRestApi/resources/11.13.18.05/publicSectorPassingRuleDetails

Request

Header Parameters
  • If the REST API supports runtime customizations, the shape of the service may change during runtime. The REST client may isolate itself from these changes or choose to interact with the latest version of the API by specifying this header. For example: Metadata-Context:sandbox="TrackEmployeeFeature".
  • The protocol version between a REST client and service. If the client does not specify this header in the request the server will pick a default version for the API.
  • Contains one of the following values: true or false. If true, the server performs an Upsert operation instead of a Create operation. During an Upsert operation, the server attempts to find an existing resource that matches the payload. If a match is found, the server updates the existing resource instead of creating a new one. If not found or false (default), the server performs a Create operation. Note that the Upsert operation isn't supported for date-effective REST resources.
Supported Media Types
Request Body - application/json ()
Root Schema : schema
Type: object
Show Source
  • Title: Agency ID
    Default Value: 1
    The agency identifier of the public sector entity to which these passing rule details apply.
  • Title: Description
    Maximum Length: 100
    The description of the passing rule details.
  • Title: Maximum Score
    The maxiumum inspection score in a range that results in a specified rating.
  • Title: Minimum Score
    The minimum inspection score in a range that results in a specified rating.
  • Title: Number of Major Violations
    The number of major violations identified in a passing rule, used to determine the inspection result.
  • Title: Pass
    Maximum Length: 1
    Indicates whether the combined scoring range and number of violations constitute a passing inspection result. The default value is false.
  • Title: Passing Rule
    Maximum Length: 15
    The unique identifier for a passing rule.
  • Title: Sequence Key
    The secondary key used to make the data for the inspection passing rule details unique.
Back to Top

Response

Supported Media Types

Default Response

The following table describes the default response for this task.
Headers
  • If the REST API supports runtime customizations, the shape of the service may change during runtime. The REST client may isolate itself from these changes or choose to interact with the latest version of the API by specifying this header. For example: Metadata-Context:sandbox="TrackEmployeeFeature".
  • The protocol version between a REST client and service. If the client does not specify this header in the request the server will pick a default version for the API.
Body ()
Root Schema : publicSectorPassingRuleDetails-item-response
Type: object
Show Source
Back to Top