Update an activity

patch

/fscmRestApi/resources/11.13.18.05/publicSectorActivities/{publicSectorActivitiesUniqID}

Request

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

    For example: publicSectorActivities?q=ActivityId=<value1>;AgencyId=<value2>;Classification=<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
  • Maximum Length: 250
    The activity name.
  • Maximum Length: 1000
    The activity description.
  • Maximum Length: 1
    Indicates whether the activity is enabled for use. Valid values are Y for enabled activity and N for disabled activity.
  • The object version number used to implement optimistic locking. It is incremented every time that the row is updated. The number is compared at the start and end of a transaction to detect whether another session has updated the row since it was queried.
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 : publicSectorActivities-item-response
Type: object
Show Source
Back to Top