Update a related transaction
patch
/fscmRestApi/resources/11.13.18.05/publicSectorRelatedTransactions/{RelatedKey}
Request
Path Parameters
-
RelatedKey(required): integer(int64)
The unique identifier of the related transaction record.
Header Parameters
-
Metadata-Context:
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".
-
REST-Framework-Version:
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
- application/json
Root Schema : schema
Type:
Show Source
object
-
Comments: string
Title:
Comments
Maximum Length:1000
The comments entered by the agency staff in the planning and zoning application. -
OriginalCreatedBy: string
The user who originally created the record in the legacy system. This is used only for data migrations. Updates the Created By attribute.
-
PriAppFlag: string
Maximum Length:
1
Default Value:N
The identifier of the ralated transaction, which is the primary application. -
RelatedPuid: string
Maximum Length:
480
The public unique identifier of a migrated related record transaction. -
RelTransId: string
Title:
Link Existing Application
Maximum Length:50
The unique identifier of the related transaction. -
RelTransKey: integer
(int64)
The unique identifier of the planning and zoning application that is being linked.
-
RelTransPuid: string
Maximum Length:
64
The public unique identifier of a migrated planning and zoning application that is being linked. -
SubAppFlag: string
Maximum Length:
1
Default Value:N
The identifier of the ralated transaction, which is the sub-application. -
TransactionPuid: string
Maximum Length:
64
The public unique identifier of a migrated planning and zoning application.
Response
Supported Media Types
- application/json
Default Response
The following table describes the default response for this task.
Headers
-
Metadata-Context(required):
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".
-
REST-Framework-Version(required):
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.
Root Schema : publicSectorRelatedTransactions-item-response
Type:
Show Source
object
-
AddedDate: string
(date-time)
Read Only:
true
The date on which the applications were linked. -
Classification: string
Read Only:
true
Maximum Length:3
The classification of the type of application. -
Comments: string
Title:
Comments
Maximum Length:1000
The comments entered by the agency staff in the planning and zoning application. -
Dependency: string
Maximum Length:
10
The identifier of the type of dependency between the linked planning and zoning applications. -
links: array
Links
Title:
Links
The link relations associated with the resource instance. -
OriginalCreatedBy: string
The user who originally created the record in the legacy system. This is used only for data migrations. Updates the Created By attribute.
-
PriAppFlag: string
Maximum Length:
1
Default Value:N
The identifier of the ralated transaction, which is the primary application. -
RelatedKey: integer
(int64)
The unique identifier of the related transaction record.
-
RelatedPuid: string
Maximum Length:
480
The public unique identifier of a migrated related record transaction. -
RelTransactionType: string
Maximum Length:
8
Default Value:ORA_REC
Identifies the related transaction type like permit, planning, business license, or case. -
RelTransId: string
Title:
Link Existing Application
Maximum Length:50
The unique identifier of the related transaction. -
RelTransKey: integer
(int64)
The unique identifier of the planning and zoning application that is being linked.
-
RelTransPuid: string
Maximum Length:
64
The public unique identifier of a migrated planning and zoning application that is being linked. -
RelTransTypeCode: string
Title:
Application Type
Read Only:true
Maximum Length:40
The unique identifier of the related transaction type code. -
RelTransTypeId: string
Maximum Length:
30
The unique identifier of the related transaction type. -
SubAppFlag: string
Maximum Length:
1
Default Value:N
The identifier of the ralated transaction, which is the sub-application. -
TransactionId: string
Maximum Length:
50
The unique identifier of the planning and zoning application. -
TransactionKey: integer
(int64)
The unique identifier of the planning and zoning application.
-
TransactionPuid: string
Maximum Length:
64
The public unique identifier of a migrated planning and zoning application. -
TransactionType: string
Maximum Length:
8
Default Value:ORA_REC
Identifies the source transaction type like permit, planning, business license, or case.
Nested Schema : Links
Type:
array
Title:
Links
The link relations associated with the resource instance.
Show Source
Nested Schema : link
Type:
Show Source
object
-
href: string
Title:
hyperlink reference
The URI to the related resource. -
kind: string
Title:
kind
Allowed Values:[ "collection", "item", "describe", "other" ]
The kind of the related resource. -
name: string
Title:
name
The name of the link to the related resource. -
properties: object
properties
-
rel: string
Title:
relation
Allowed Values:[ "self", "lov", "parent", "canonical", "child", "enclosure", "action", "custom" ]
The name of the relation to the resource instance. Example: self.
Nested Schema : properties
Type:
Show Source
object
-
changeIndicator: string
Change indicator or the ETag value of the resource instance.