Update a related transaction

patch

/fscmRestApi/resources/11.13.18.05/publicSectorRelatedTransactions/{RelatedKey}

Request

Path Parameters
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
    Maximum Length: 1000
    The comments entered by the agency staff in the planning and zoning application.
  • The user who originally created the record in the legacy system. This is used only for data migrations. Updates the Created By attribute.
  • Maximum Length: 1
    Default Value: N
    The identifier of the ralated transaction, which is the primary application.
  • Maximum Length: 480
    The public unique identifier of a migrated related record transaction.
  • Title: Link Existing Application
    Maximum Length: 50
    The unique identifier of the related transaction.
  • The unique identifier of the planning and zoning application that is being linked.
  • Maximum Length: 64
    The public unique identifier of a migrated planning and zoning application that is being linked.
  • Maximum Length: 1
    Default Value: N
    The identifier of the ralated transaction, which is the sub-application.
  • Maximum Length: 64
    The public unique identifier of a migrated planning and zoning application.
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 : publicSectorRelatedTransactions-item-response
Type: object
Show Source
Back to Top