Create a set of related transactions

post

/fscmRestApi/resources/11.13.18.05/publicSectorRelatedTransactions

Request

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.
  • Contains one of the following values: true or false. If true, the server performs an Upsert operation instead of a Create operation. During an Upsert operation, the server attempts to find an existing resource that matches the payload. If a match is found, the server updates the existing resource instead of creating a new one. If not found or false (default), the server performs a Create operation. Note that the Upsert operation isn't supported for date-effective REST resources.
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.
  • Maximum Length: 10
    The identifier of the type of dependency between the linked planning and zoning applications.
  • 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.
  • The unique identifier of the related transaction record.
  • Maximum Length: 480
    The public unique identifier of a migrated related record transaction.
  • Maximum Length: 8
    Default Value: ORA_REC
    Identifies the related transaction type like permit, planning, business license, or case.
  • 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: 30
    The unique identifier of the related transaction type.
  • Maximum Length: 1
    Default Value: N
    The identifier of the ralated transaction, which is the sub-application.
  • Maximum Length: 50
    The unique identifier of the planning and zoning application.
  • The unique identifier of the planning and zoning application.
  • Maximum Length: 64
    The public unique identifier of a migrated planning and zoning application.
  • Maximum Length: 8
    Default Value: ORA_REC
    Identifies the source transaction type like permit, planning, business license, or case.
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