Get a related transaction

get

/fscmRestApi/resources/11.13.18.05/publicSectorRelatedTransactionQueries/{publicSectorRelatedTransactionQueriesUniqID}

Request

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

    For example: publicSectorRelatedTransactionQueries?q=TransactionKey=<value1>;AddedDate=<value2>;RelTransKey=<value3>
Query Parameters
  • This parameter specifies dependencies which are fields that are set before and rolled back after generating the response. Generally they are used to preview the effects of an attribute change. The fields specified in this parameter are always set in the resource instance in question. When a child resource collection is requested and the parameter is set, the fields will be set in the parent resource instance before generating the resource collection payload. The value of this query parameter is a set of dependency fields. Example: dependency=ProductId=2

    Format: <attr1>=<val1>,<attr2>=<value2>
  • When this parameter is provided, the specified children are included in the resource payload (instead of just a link). The value of this query parameter is "all" or "". More than one child can be specified using comma as a separator. Example: ?expand=Employees,Localizations. Nested children can also be provided following the format "Child.NestedChild" (Example: ?expand=Employees.Managers). If a nested child is provided (Example: Employees.Managers), the missing children will be processed implicitly. For example, "?expand=Employees.Managers" is the same as "?expand=Employees,Employees.Managers" (which will expand Employees and Managers).
  • This parameter filters the resource fields. Only the specified fields are returned, which means that if no fields are specified, no fields are returned (useful to get only the links). If an indirect child resource is provided (Example: Employees.Managers), the missing children will be processed implicitly. For example, "?fields=Employees.Managers:Empname" is the same as "?fields=;Employees:;Employees.Managers:Empname" (which will only return the "Empname" field for Managers). the value of this query parameter is a list of resource fields. The attribute can be a direct (Example: Employees) or indirect (Example: Employees.Managers) child. It cannot be combined with expand query parameter. If both are provided, only fields will be considered.

    Format: ?fields=Attribute1,Attribute2

    Format for fields in child resource: ?fields=Accessor1:Attribute1,Attribute2
  • This parameter can be used to show only certain links while accessing a singular resource or a resource collection. The parameter value format is a comma-separated list of : <link_relation>

    Example:
    self,canonical
  • The resource item payload will be filtered in order to contain only data (no links section, for example).
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.

There's no request body for this operation.

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 : publicSectorRelatedTransactionQueries-item-response
Type: object
Show Source
  • Read Only: true
    The unique identifier of the pre-application or business license consultation.
  • Read Only: true
    The user name of the assigned user for the related planning application.
  • Read Only: true
    Maximum Length: 12
    The classification of the related application like permit, planning application, or business license.
  • Read Only: true
    Maximum Length: 255
    A description of the classification code of the current transaction.
  • Read Only: true
    Indicates the total number of conditions of approval applied on the related transaction.
  • Read Only: true
    Indicates whether the user has access to remove the related transaction row.
  • Read Only: true
    Maximum Length: 40
    The dependency between related applications like ORA_PREAPP, ORA_REQ, or ORA_REL.
  • Read Only: true
    Maximum Length: 1000
    The comments added for the related transaction.
  • Read Only: true
    The date and time when the related application was last updated.
  • Read Only: true
    The user who linked the transaction to current application.
  • Links
  • Read Only: true
    Maximum Length: 255
    The related transaction link is for neither the primary nor subapplication of the current application.
  • Read Only: true
    The transaction change date of the parent transaction.
  • Read Only: true
    The parent transaction key for the current transaction.
  • Read Only: true
    Maximum Length: 4
    The current application is the primary application for the related transaction.
  • Read Only: true
    Maximum Length: 4
    The current application is the sub-application for the related transaction.
  • Read Only: true
    Maximum Length: 1
    The related transaction is the primary application of the current application.
  • Read Only: true
    Maximum Length: 255
    The related transaction link is for the primary application of the current application.
  • Read Only: true
    Maximum Length: 100
    The application type of the related application.
  • Read Only: true
    The unique identifier of the related record transaction.
  • Read Only: true
    Maximum Length: 8
    Identifies the related transaction type like permit, planning application, business license, or case.
  • Read Only: true
    Indicates total number conditions of approval applied on the current permit application from it's related planning application.
  • Read Only: true
    Maximum Length: 50
    The application identifier of the related application.
  • Read Only: true
    The application key of the related application.
  • Read Only: true
    Maximum Length: 20
    The application type code for the related application.
  • Read Only: true
    Maximum Length: 30
    The application type identifier for the related application.
  • Read Only: true
    Maximum Length: 15
    The status of the related application.
  • Read Only: true
    Maximum Length: 1
    The related transaction is the sub-application of the current application.
  • Read Only: true
    Maximum Length: 255
    The related transaction link is for the subapplication of the current application.
  • Read Only: true
    Maximum Length: 15
    The system status of the related application.
  • Read Only: true
    Maximum Length: 50
    The permit, planning application, or business license identifier.
  • Read Only: true
    The unique identifier of the Permit, Planning application, or Business License application.
  • Read Only: true
    Maximum Length: 8
    Identifies the source transaction type like permit, planning, business license, or case.
  • Read Only: true
    Indicates the total number of conditions of approval applied on related permit application from current planning application.
  • Read Only: true
    A switch to determine whether the user has access to update the row.
  • Read Only: true
    The type of user who added the related application, such as AGENCY or APPLICANT.
Back to Top