Get a planning plan review communication item

get

/fscmRestApi/resources/11.13.18.05/publicSectorPlanReviewPlanningCommunications/{publicSectorPlanReviewPlanningCommunicationsUniqID}

Request

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

    For example: publicSectorPlanReviewPlanningCommunications?q=LnpRecordKey=<value1>;PlanReviewKey=<value2>
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 : publicSectorPlanReviewPlanningCommunications-item-response
Type: object
Show Source
  • Title: Agency Name
    Read Only: true
    Maximum Length: 100
    The agency name of the public sector entity to which this planning plan review communication applies.
  • Read Only: true
    The unique identifer for an applicant.
  • Title: Applicant User ID
    The user ID for an applicant.
  • Title: Plan Check Coordinator User ID
    Read Only: true
    Maximum Length: 64
    The user who created the planning plan review cycle.
  • Title: Plan Review Cycle
    Read Only: true
    The number specifying each planning plan review cycle.
  • Title: Decision
    Read Only: true
    Maximum Length: 32
    The decision status for the planning plan review cycle.
  • Title: Applicant Email
    Read Only: true
    Maximum Length: 320
    The email address for the applicant.
  • Links
  • Title: Application
    Read Only: true
    Maximum Length: 50
    The planning record identifier.
  • Read Only: true
    The unique identifer for a planning plan review cycle.
  • Title: Subclassification
    Maximum Length: 80
    The public unique identifier of the subclassification code. This is the readable value displayed to the user.
  • Title: Plan Check Coordinator Email
    The email address for the plan coordinator.
  • Title: Plan Check Coordinator Name
    The name of the plan coordinator.
  • Title: Applicant Name
    Read Only: true
    Maximum Length: 450
    The name of the applicant.
  • Read Only: true
    The unique identifer for a planning record.
  • Title: Plan Review Name
    Read Only: true
    Maximum Length: 100
    The name of the planning plan review.
  • Title: Application Type
    Read Only: true
    Maximum Length: 100
    The type of planning application. For example, a residential addition.
  • Title: Decision Date
    Read Only: true
    The date when the planning plan review cycle was closed.
  • Read Only: true
    The user who opened the planning plan review cycle.
  • Title: Plan Review Cycle Status
    Read Only: true
    Maximum Length: 30
    The review status for the planning plan review cycle.
  • Read Only: true
    Maximum Length: 10
    The subclassification code for the transaction type, which indicates that the preapplication process is included in addition to the hearing process.
Back to Top