Update a fee item

patch

/fscmRestApi/resources/11.13.18.05/publicSectorFeeItems/{publicSectorFeeItemsUniqID}

Request

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

    For example: publicSectorFeeItems?q=AgencyId=<value1>;FeeItemId=<value2>
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: Department
    Maximum Length: 30
    The department identifier for a fee item.
  • Title: Description
    Maximum Length: 50
    The description of the fee item.
  • Title: Enabled
    Maximum Length: 1
    Indicates whether this fee item is enabled for use or not. The default value is true.
  • Maximum Length: 30
    Indicates the options for the revenue recognition accounting date.The options are fee paid, fee assessed, and fee refunded. The default value is none.
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 : publicSectorFeeItems-item-response
Type: object
Show Source
Back to Top