Update a workflow comment

patch

/fscmRestApi/resources/11.13.18.05/publicSectorPcsComments/{publicSectorPcsCommentsUniqID}

Request

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

    For example: publicSectorPcsComments?q=PcsCommentId=<value1>;TaskId=<value2>;LnpRecordKey=<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: Comments
    The comment that has been entered by the user.
  • The unique identifier for a record. The record can be for permits, business licenses, professional licenses, or planning and zoning, which is determined by the classification.
  • Maximum Length: 100
    The unique identifier of the workflow task.
  • Title: Hide from Public
    Maximum Length: 1
    Default Value: Y
    The indicator that determines whether the comment should be hidden from public users or not.
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 : publicSectorPcsComments-item-response
Type: object
Show Source
Back to Top