Update a hearing hierarchy body

patch

/fscmRestApi/resources/11.13.18.05/publicSectorHearingHierarchyBodies/{publicSectorHearingHierarchyBodiesUniqID}

Request

Path Parameters
  • This is the hash key of the attributes which make up the composite key--- AgencyId, HearingHierarchyCode and HearingBodyCode ---for the Hearing Hierarchy Bodies resource and used to uniquely identify an instance of Hearing Hierarchy Bodies. The client should not generate the hash key value. Instead, the client should query on the Hearing Hierarchy Bodies collection resource with a filter on the primary key values in order to navigate to a specific instance of Hearing Hierarchy Bodies.

    For example: publicSectorHearingHierarchyBodies?q=AgencyId=<value1>;HearingHierarchyCode=<value2>;HearingBodyCode=<value3>
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.
Supported Media Types
Request Body - application/json ()
Root Schema : schema
Type: object
Show Source
  • Title: Appeal Allowed
    Maximum Length: 1
    Indicates if an appeal is allowed for the hearing body.
  • Title: Enabled
    Maximum Length: 1
    Indicates if the hearing hierarchy body is available to use.
  • Title: Escalate after Expiration Period
    Maximum Length: 1
    Default Value: false
    Indicates if an expiration is applicable for the hearing body.
  • Title: Sequence
    The sequence that the hearing bodies follow in the hearing hierarchy.
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 : publicSectorHearingHierarchyBodies-item-response
Type: object
Show Source
Back to Top